Appium-desktop: Saved Capability Sets are being lost

[toien44]

The problem

Appium Desktop v1.11.0 when you close the app you lose your saved capability set

[dpgraham]

~~@toien44 that's correct yes. My recommendation is to Save your desired capabilities before starting a session.

It is possible that we can always save the most recently used desired capabilities so that when you return to the session creation screen, it goes back to the caps that you most recently used.

I don't think I'll have time to prioritize this feature but I'd be happy to accept a pull request and help somebody get this feature into Appium Desktop.~~

[toien44]

Before I had a few saved in Saved Capability Set and it didn't delete them. So every time you close Appium Desktop it will delete that section?

[dpgraham]

If you save it, it will be there, you just have to re-select it when you return.

[robegort]

actually the saved capabilities aren't saved anymore. I've had numerous occasions where the saved capabilities are gone when I start appium Version 1.11.0 (1.11.0)

[NastyAlloys]

Same. Every time I restart Appium it asks me to send crash log and no saved capabilities are present.

[dpgraham]

@robegort @NastyAlloys are you saying _all_ saved capabilities are gone? So you're saving caps and then closing and returning to the app and nothing is there?

[dpgraham]

ie: there's nothing under Saved Capabilities Sets

[ranjith-gampa]

Same here. I had 11 saved capabilities yesterday on v1.10.0, today when it was updated to v1.11.0, I see 0 in my saved capabilities list

[dpgraham]

I'm terribly sorry that this happened to all of you. This is obviously a bug on the Appium Desktop side.

One more question: from 1.11.0 onwards, does saving the capabilities no longer work? Or did it lose everything prior to 1.11 but then saves them in the future?

I wish I had a solution for recovering the lost capability sets, but I don't know if that's possible.

[dpgraham]

Is this happening on Windows, Linux or Mac?

This didn't happen for me on Mac.

[toien44]

It started for my on a Mac. It doesn't happen every time. It started for my in 1.11.0

[halderpritam]

Facing the same thing over here. For me it happens on Mac

[robegort]

For me it happened on mac and started on 1.11.0 or 1.11.1

[dpgraham]

This should be resolved with 1.12 now.... let me know if anyone still experiences this.

And again, my apologies for the terrible inconvenience that this would have caused.