-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test runs fine on iOS, but tails on Android #716
Comments
Doesn't look like an expected behavior to me. Please provide the all the logs and information as requested in the issue template. Also, since we don't use JS navigation solutions, could you please recreate this in a minimal demo project and upload it for us? Thanks |
What version of react native do you use? |
thanks for the replies guys! So I tried to recreate the issue in a simple example, but it turns out that it's not react-native-router-flux... I took their example and added detox to it, but there I can run the tests on iOS and android. It must be something else in my code. I have redux and firebase - so it might be related to the network requests. Will try to add them to the sample project and see if I'll manage to recreate the issue. Please leave the issue open a little longer. |
Sure. The bot might close it, but we can always reopen. |
It is important to note which version of react-native your project uses, as there have been known-incompatibilities with wix-detox from time to time. Last time I was able to use them together was RN 49. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
I have a simple login test:
This works fine on iOS. The user is logged in and sees the companiesScreen. The test fails on Android at the last line:
await expect(element(by.id('companiesScreen'))).toBeVisible()
If I change this to:
await waitFor(element(by.id('companiesScreen'))).toBeVisible().withTimeout(4000)
Then it works on android as well. The navigation in our app is done by react-native-router-flux, which users react-navigation.
WaitFor works, but it defeats the purpose of all this. I have another tests that also fail with the same conditions... Is this expected behavior or a bug?
The text was updated successfully, but these errors were encountered: