New 0.60.5 app fails to run in Firebase Test Lab Pixel, API Level 26
See original GitHub issueNew 0.60.5 app created via init fails Robo test when using Android Application Bundle in Firebase Test Lab on Pixel, API Level 26 (and more).
React Native version:
System:
OS: Linux 4.15 Ubuntu 18.04.3 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Memory: 1.50 GB / 15.43 GB
Shell: 4.4.20 - /bin/bash
Binaries:
Node: 10.14.2 - ~/.nodenv/versions/10.14.2/bin/node
Yarn: 1.17.3 - /usr/bin/yarn
npm: 6.4.1 - ~/.nodenv/versions/10.14.2/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 27.0.3, 28.0.3
System Images: android-19 | Intel x86 Atom, android-22 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-27 | Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.5 => 0.60.5
npmGlobalPackages:
react-native-cli: 2.0.1
Steps To Reproduce
- react-native init AwesomeProject2
- cd AwesomeProject2/android && ./gradlew bundleRelease
- Upload app.aab to Firebase Test Lab and run Robo test on Pixel, API Level 26
Describe what you expected to happen:
A successful test.
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
FATAL EXCEPTION: create_react_context
Process: com.awesomeproject2, PID: 13159
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
at java.lang.Thread.run(Thread.java:764)
web-build_2019-08-15T13:49:10.847Z_lej5_sailfish-26-en_US-portrait_logcat.log app.aab.gz
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:5
Top Results From Across the Web
android - Test run failing on Firebase Test Lab - Stack Overflow
That error can occur if you're trying to test a debug APK that you built with Android Studio during development.
Read more >Firebase Test Lab How To Perform Facebook Login In Robo ...
New 0.60.5 app created via init fails Robo test when using Android Application Bundle in Firebase Test Lab on Pixel API Level 26...
Read more >Virtual-device-testing-for-android timeout every 30 min
Hi, I notice that my UI Test for Android recently failed due to TimeOut error: Test results: Model API Level Locale Orientation Outcome ......
Read more >Packages beginning with letter P - RPMFind
Packages beginning with letter P ; pamix-1.6-2.fc34, PulseAudio terminal mixer, linux/x86_64 ; pamtester-0.1.2-18.fc34, Utility to test Pluggable Authentication ...
Read more >Platforms - DirDev.com
js without switching versions manually or pushing to Travis CI. loadtest - Run load tests for your web application, with an API for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Having the same problem here, uploaded my app to the google play store, it works fine on emulator(both downloading it from the play store and directly react-native run-android).Should i be concerned about an unhandled error?
Hi, I am still having the same issue with that Nexus 5X. It just happened today, is the bug fixed or is there any update about this bug? Thanks!