-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Protractor with Appium on iOS not working correctly #1736
Comments
Using ignoreSynchronisation = true, now makes the app display and navigates a bit using my tests, but by.model calls now fail, which makes me think it now hasn't bootstrapped correctly? |
I wonder if the How does the by.model call fail? |
It fails with this stackstrace when using
Just using
will not find any elements
|
OK just to make sure - you're absolutely sure that this item does in fact exist on the page? Have you tried putting in a sleep statement (I'm not sure if implicit wait will wait for custom element selectors, I will look into that and report back) before looking by model? |
Yep, like I say the tests work perfectly on Android, it is only on iOS that this is an issue. I will check when I get back into work tomorrow if the sleep statement makes a difference. Thanks for your help :) |
Any update? |
@juliemr - I have a similar problem, my angular app is launched in browser using safari launcher on an iPad but when i'm trying to use element(by.) i get an error in appium that says something like this 👍 |
I haven't heard any updates on the original issue, so I'm closing this. Please open a fresh issue with a reproducible test case if you believe there is a bug with Protractor. |
Hi @mindmelting could you please share what you've done for Android? In terms of what Thanks!! |
I have the same problem. The app cannot launch. Adding
|
Protractor tests work fine on Android, but with Appium on iOS it uses SafariLauncher and navigates to my angular app, but it never seems to load the app and I just get a gray screen. If I hit refresh the app loads fine though.
The angular app uses requirejs and is manually bootstrapped to a div element, so I configure rootElement in my configuration.
If I use java to write tests, they run fine and the app launches...hence I think it is a Protractor issue...
This is the logs that get output from my selenium grid instance...
The text was updated successfully, but these errors were encountered: