This article provides information intended for developers with app(s) that use a defective version of the SoLoader SDK directly or indirectly.
What’s happening
One or more of your apps contain a defective version of the SoLoader SDK, which causes your app to crash, thus harming its usability. Even if your app doesn’t depend on the SoLoader directly, we suspect that one of the third-party libraries/SDKs in your app’s dependencies may do so.
Additional details
Your app incorporates a version of the SoLoader SDK that causes crashes on 64bit-only devices. Versions before 0.9.0 incorrectly assume that all system libraries are present in /system/lib:/vendor/lib (see fix).
We recommend updating to the latest stable version of SoLoader, 0.10.4 or greater, which, in addition to the 64bit-only issue above, also fixes:
- A backup-and-restore issue (see fix); and
- an issue concerning loading native libraries from vendor partition (see fix).
Next Steps
You can fix apps with bad SoLoader versions by following each of the steps below.
Step 1: Update your app and fix the issue.
If your app depends on the SoLoader SDK directly, migrate your app to SoLoader 0.10.4 or newer.
For example, if you specified 'com.facebook.soloader:soloader:0.9.0' in your Gradle settings, update it to “0.10.4+” or newer.
If your app depends on the SoLoader SDK indirectly through another SDK, please check the latest version of that SDK or contact your SDK provider to download a fixed version and apply to your project.
For other ways to make your app support 64-bit devices, please refer to this guide.
Step 2: Submit your updated app bundle or APK.
Follow the steps in this article to create a new release with your updated app bundle or APK.