-
Notifications
You must be signed in to change notification settings - Fork 175
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
Failing to load libhermes.so on Chromebooks #53
Comments
Interestingly enough when side-loading the application directly onto the Chromebook via
The application runs as expected, it only seems to be a problem when directly downloading from the Play Store. |
@asleepace any updates on if you were able to resolve this? Currently also seeing this issue in production. |
@asleepace were you able to fix the issue, I am also experiencing the same issue in my app... any suggestions? |
@noumantahir I'm not sure my solution is still relevant, but maybe try the following in the project's allprojects {
repositories {
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../../node_modules/jsc-android/dist")
}
google()
maven {
url 'https://maven.google.com/'
name 'Google'
}
maven {
// All of Detox' artifacts are provided via the npm module
url "$rootDir/../../node_modules/detox/Detox-android"
}
maven { url 'https://www.jitpack.io' }
configurations.all {
resolutionStrategy {
force "com.facebook.soloader:soloader:0.9.0+"
}
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
// We used to use this section to override support libraries in different
// modules, however this is not an ideal strategy and we should opt to exclude
// certain libraries in the App gradle dependencies (see nearby for example)
// or here https://docs.gradle.org/current/userguide/dependency_downgrade_and_exclude.html
// see version prior to 120.0 for actual implementation here.
}
}
}
} Specifically this line resolutionStrategy {
force "com.facebook.soloader:soloader:0.9.0+"
} We also now use Hope this helps, it's been quite a while so I can't really remember 😅 |
Version 0.10.3 has been released which includes this fix. |
Description
Recently we started using SoLoader version 0.8.0 to fix an issue with the hermes engine not loading on some phones like the Oppo. However after this fix we are seeing a new error that seems to only be affecting Chromebooks running our react native application.
Platforms
Although we are unable to reproduce the error it appears to happen on android versions 5-9 and only on Chromebooks with the majority being the Google Chromebook 11 Model 3180.
Gradle
Library Versions
Note we have already looked into other similar PRs such as this, however we are building our app as an apk and not bundling.
0.8.0
0.60.5
^0.1.1
The text was updated successfully, but these errors were encountered: