Can not save desired capabilities-Appium inspector

[DeliaLing]

Can not save desired capabilities-Appium inspector

I wrote desired capabilities as below, click on save as with a name. Then close inspector and reopen it again. Click on the name what I just saved. the content is empty. There is a size limit for the video, so not able to attach it here.

{ "deviceName": "iPhone XR", "platformVersion": "16.0",

"platformName": "iOS",

"xcodeSigningId": "iPhone Developer",

"automationName": "XCUITest" }

Environment

• I am running Appium Desktop version <1.22.3-4>.
• Appium inspector version: 2022.9.1
• Mac: 12.6
• I am on (pick one):
  • [x ] Mac
  • [ ] Windows
  • [ ] Linux

[sudharsan-selvaraj]

@DeliaLing Have you clicked on the save icon in the JSON editor before hitting Save as button?

[DeliaLing]

Hi @sudharsan-selvaraj , I clicked the save button, please check the video from this link: https://drive.google.com/file/d/1ADKkO1mbgyaih5b3ws4qO6BUq6Oxfobn/view?usp=sharing

The desired cap can be saved only when the session can be started without any error. If I make a change for any existing desired cap and save it. The change is not saved successfully. Moreover, if I create a new desired cap and save it without starting a session, it can not be saved it neither.

[eglitise]

@DeliaLing I can see a few issues in your video:

1. At 0:07, you should first press the save icon in the JSON editor, and only then press 'Save As...'. This is a minor bug because the 'Save As...' button should not be enabled.
2. At 0:32, after pressing the save icon in the JSON editor, you should press the 'Save' button at the bottom. In the video it is not enabled, which was fixed in Appium Inspector v2022.11.1.

The expected behavior is that, after pressing the save icon in the JSON editor, you need to press either the 'Save' or 'Save As...' button at the bottom to save your changes.

Please update to a newer Appium Inspector version, and check if your issue persists with the flow I described.

[eglitise]

A fix for the first issue in my previous comment is included in v2023.5.1. Closing this issue. @DeliaLing - feel free to reopen this if you are still experiencing the problem with the latest app version.