Skip to content
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

[Fixed in 0.57] [Regression] Release Android Build Fails on ARM Emulators in 30%-50% times since 0.49 #21037

Closed
isnifer opened this issue Sep 10, 2018 · 3 comments
Labels
Impact: Regression Describes a behavior that used to work on a prior release, but stopped working recently. Issue: Author Provided Repro This issue can be reproduced in Snack or an attached project. Platform: Android Android applications. Resolution: Locked This issue was locked by the bot.

Comments

@isnifer
Copy link
Contributor

isnifer commented Sep 10, 2018

Environment

Run react-native info in your terminal and paste its contents here.

Environment:
  OS: macOS High Sierra 10.13.6
  Node: 9.11.2
  Yarn: 1.3.2
  npm: 6.4.1
  Watchman: 4.9.0
  Xcode: Xcode 9.4.1 Build version 9F2000
  Android Studio: 3.1 AI-173.4907809

Packages: (wanted => installed)
  react: 16.5.0 => 16.5.0
  react-native: 0.56.0 => 0.56.0

Description for this Regression

Hi! I'm working at Tipsi. Some of you have used our tipsi-stripe library.
We are developing not only this library for React-Native and we have rules:

  • All our modules should have example projects
  • Appium E2E-tests ran against these examples.

We are using Travis CI to run E2E-tests. Travis CI allows us to run Android tests only on Emulators with ARM processors architecture.
Currently, we are running tests on emulators on top Android-21 SDK (Android 5.0.1) without gms.
We have noticed that React-Native Apps since 0.49 starting OK only in 50% times, since 0.53.3 only in 30% times on ARM Emulators.

IMPORTANT:

  • If you will rotate a screen of the emulator — you'll see the demo app

QA

Q: What about x86 emulators?
A: On x86 emulators, every demo project works fine

Q: Why do not use x86 emulators on Travis CI?
A: Travis CI does not support them:

emulator: ERROR: x86 emulation currently requires hardware acceleration!

Q: What about iOS?
A: On iOS Simulators, every demo project works fine

Q: Is there a job demonstrates that on 0.48.4 everything is OK?
A: Yes

Reproducible Demo

https://github.com/isnifer/tipsi-travis-scripts/tree/feature/scripts

# inside the root of the folder
npm run ci

Update from September 13, 2018

Q: Is there a job demonstrates that on 0.57.0 everything is OK?
A: Yes

@react-native-bot react-native-bot added Platform: Android Android applications. Impact: Regression Describes a behavior that used to work on a prior release, but stopped working recently. ⏪Old Version labels Sep 10, 2018
@react-native-bot
Copy link
Collaborator

It looks like you are using an older version of React Native. Please update to the latest release, v0.56 and verify if the issue still exists.

The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

@isnifer
Copy link
Contributor Author

isnifer commented Sep 10, 2018

@react-native-bot yes, the issue exists since 0.49

@hramos hramos added the Issue: Author Provided Repro This issue can be reproduced in Snack or an attached project. label Sep 11, 2018
@isnifer
Copy link
Contributor Author

isnifer commented Sep 13, 2018

@hramos I'm closing this issue. I have tested it on 0.57.0 and it works — https://travis-ci.org/tipsi/tipsi-travis-scripts/builds/427959587

@isnifer isnifer closed this as completed Sep 13, 2018
@isnifer isnifer changed the title [Regression] Release Android Build Fails on ARM Emulators in 30%-50% times since 0.49 [Fixed in 0.57] [Regression] Release Android Build Fails on ARM Emulators in 30%-50% times since 0.49 Sep 13, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Sep 13, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Impact: Regression Describes a behavior that used to work on a prior release, but stopped working recently. Issue: Author Provided Repro This issue can be reproduced in Snack or an attached project. Platform: Android Android applications. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants