How to resolve issue for appium inspector when entering PlatformName as iOS, getting error that platformName should be MAC,WINDoWS etc. Not able to start session because of this.

[chetan160689]

Appium or Appium Desktop?

You are reporting an issue at the Appium Desktop repository. Appium Desktop is a wrapper around Appium. If you are having trouble running tests, it is much more likely that the problem you are encountering is not a problem with Appium Desktop but with Appium. For that reason we require you to have tried your testcase with Appium CLI before reporting issues. Check the checkbox below to confirm that you have proven your issue does not reproduce on Appium itself:

• [x] I have verified that my issue does not occur with Appium and should be investigated as an Appium Desktop issue

The problem

Replace this section with a description of your issue

Environment

• I am running Appium Desktop version .
• I am on (pick one):
  • [x] Mac
  • [ ] Windows
  • [ ] Linux

[chetan160689]

Using mac m1 and latest appium desktop and appium inspector

[chetan160689]

Actual Error Message after clicking on Start Session :

Error Failed to create session. Error : Platform can be one of MAC, WIN8, XP, and ANY

[chetan160689]

Any update on this?

[chetan160689]

[email protected] @mykola-mokhnach - Do you have any solution on this? I can see all others can use PlatformName as iOS but for me i am getting above error which are not mobile platforms.

[chetan160689]

@jlipps - Can you also look from your end?

[jlipps]

Please provide a full report of what's going on. I don't see any actual issue here. Only an error message that you're not using a platform name appropriate for your driver. Share more about what you are doing, your full set of capabilities, the full server logs, etc...

[kkauffman-incomm]

I'm seeing the same issue on both macOS Big Sur and Windows 10. I have to install Appium Desktop 1.19.1, back when Appium Inspector was bundled with that, in order to get a working version (@chetan160689, here is a work-around, if you need it).

I am attempting to connect to a device via BrowserStack. Here is my capability set:

{
  "appium:deviceName": "iPhone SE 2020",
  "platformName": "iOS",
  "appium:app_url": "bs://[REDACTED]",
  "appium:platformVersion": "13"
}

The above capability set was created with the instructions provided by BrowserStack. The checkbox to "Automatically add necessary Appium vendor prefixes on start" does not prepend appium: to the front of platformName, and I'm not sure why. Is platformName now defunct in place of something else?

[KazuCocoa]

It seems like browserstack specific behavior as https://github.com/appium/appium-inspector/issues/437 .

platformName is W3C standard, so it should not have a vendor prefix like appium: as https://www.w3.org/TR/webdriver/

Duplicate of https://github.com/appium/appium-inspector/issues/437

[kkauffman-incomm]

For those in the future: this was indeed a BrowserStack issue, but only in the documentation. The webpage with instructions for how to connect to BrowserStack is using BrowserStack's custom app_url capability instead of the W3C app capability. It's a small detail that is easy to overlook.

This morning, I received this response from BrowserStack support:

I request you to please follow the W3C protocol for the capability generator: https://www.browserstack.com/app-automate/capabilities?tag=w3c

We will be checking internally to update this page regarding W3C protocol capabilities and will be publishing those changes accordingly.