question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Appium 1.15.x No Longer matching Connected UDID of Real Device

See original GitHub issue

The problem

UDID of real device using Appium 1.15.0 no longer contains a “-”. This is causing the following error:

2019-10-24 18:04:58:609 - [debug] [MJSONWP] Encountered internal error running command: Error: Unknown device or simulator UDID: ‘00008020-001C650A2288002E’ 2019-10-24 18:04:58:609 - [debug] [MJSONWP] at XCUITestDriver.determineDevice (/usr/local/avm/versions/1.15.0/node_modules/appium/node_modules/appium-xcuitest-driver/lib/driver.js:806:17)

Environment

  • Appium version (or git revision) that exhibits the issue: 1.15
  • Last Appium version that did not exhibit the issue (if applicable): 1.14
  • Node.js version (unless using Appium.app|exe): 10.16.0
  • Npm or Yarn package manager: yarn
  • Mobile platform/version under test: iOS
  • Real device or emulator/simulator: Real

Details

Appium retrieves the connected device with a UDID of: 00008020001C650A2288002E Actual UDID of connected device: 00008020-001C650A2288002E

Devices used: iPhone XS Max (12.1), iPhone XR (12.4.1)

I am using AWS Device Farm to access their pool of real devices, so I don’t have control over their device UDID’s. I’ve also tried Appium 1.15.1 to no avail.

Link to Appium logs

https://gist.github.com/hcastro/0ec6d2f7c86466971efbaecacd049217

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
imurchiecommented, Oct 24, 2019

But you could do something like udid = process.env.AWS_UDID.replace('-', '') or whatever is the case in the language you’re using.

We can make this work on the server side, but it will take a while to get into place, so temporarily doing it on the test side would be useful for now.

0reactions
Bruno-ornelascommented, Feb 14, 2020

Como você conseguiur iniciar o appium 1.15 no aws device farm?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Appium Is not working after xcode11 update - Issues/Bugs
If I connect appuim server from appium desktop app(which has 1.15 latest version), the web driver agent installed and run correctly. But when ......
Read more >
Setting up the Environment for iOS Testing on Real Device
Appium's iOS real device support depends on a third-party software suite called libimobiledevice. Run. brew install libimobiledevice --HEAD.
Read more >
How To Automate iOS App Using Appium | LambdaTest
To know the device name, in the iPhone, we can navigate to“Settings> General > About > Name.” udid: is the unique ID of...
Read more >
appium-xcuitest-driver - npm
After many failures on real devices it could transition to a state where connections are no longer being accepted. To possibly remedy this...
Read more >
connect econnrefused 127.0.0.1:8100 - You.com - You.com
I want to automate native app in appium but I'm not able to connect to appium server ... [XCUITest] Available devices: [XCUITest] No...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found