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.
Remote Debugger can't get the right context for iOS 13 web tests
See original GitHub issueThe problem
When running web tests with Xcode 11 beta 5 and iOS 13, web tests fail.
Environment
- Appium version (or git revision) that exhibits the issue: 68981b79b6cf904c0188c72e899c70ea1f9d4d3e
- Last Appium version that did not exhibit the issue (if applicable):
- Desktop OS/version used to run Appium:
- Node.js version (unless using Appium.app|exe): v12.5.0
- Npm or Yarn package manager: npm 6.9.0
- Mobile platform/version under test: iOS 13
- Real device or emulator/simulator: iPhone 8 Simulator
- Appium CLI or Appium.app|exe:
Details
Remote Debugger can’t get the right context for iOS 13 web tests.
Link to Appium logs
https://gist.github.com/sadafyadegari/5faa0c10a48ccc313cc63c2b10c7675e
Code To Reproduce Issue [ Good To Have ]
running iOS web test:
runsauce -c local -t web -v 13.0 -d "iPhone 8" -a 1.13.0
appium 68981b79b6cf904c0188c72e899c70ea1f9d4d3e
WebDriverAgent 2ea6a8839c15e268459b81cd3be1b8fe98b0bf36
appium-xcuitest-driver c0bcf3d6ce88bf3cff6a75a965c4417f136e7f36
Test fails when com.apple.mobilesafari.plist is not copied at /Library/Developer/CoreSimulator/Devices/<device-ID>/data/Library/Preferences/
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
BTW, Apple has changed the path to CoreSimulator folder since Xcode11, check https://github.com/appium/appium-ios-simulator/pull/235
Yep