你要瀏覽的網頁目前並未提供你慣用的語言版本。你可以在頁面底部選取其他語言版本,或使用 Google Chrome 內建的翻譯功能,將網頁內容即時翻譯成所選的語言。

How to fix apps with bad SoLoader versions

This information is 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 artifact directly, we suspect that one of the 3rd-party libraries/SDKs in your app’s dependencies may do so.

Additional details

Your app incorporates a version of the SoLoader SDK that causes hangs or 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 (i) a backup-and-restore issue (see fix), and (ii) an issue concerning loading native libraries from vendor partition (see fix).  

Next Steps 

1. Update your app and fix the issue using the steps highlighted below.

  • If your app depends on the SoLoader SDK directly, 
    • Migrate your app to SoLoader 0.10.4 or newer.
    • For example, if you implemented '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.

2. Submit your updated app bundle or APK

To submit an updated app bundle or APK:

  1. Go to your Play Console.
  2. Select the app.
  3. Go to the App bundle explorer.
  4. Select the non-compliant APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under.
  5. Go to the track with the policy issue. It will be one of these 4 pages: Internal / Closed / Open testing or Production.
  6. Near the top right of the page, click Create new release. (You may need to click Manage track first.)
  7. If the release with the non-compliant APK/app bundle is in a draft state, discard the release.
  8. Add the policy-compliant version of the APK/app bundle.
  9. Make sure the non-compliant version of the APK/app bundle is under the Not included section of this release. For further guidance, please see the "Not included (app bundles and APKs)" section in this Play Console Help article.
  10. To save any changes you make to your release, select Save.
  11. When you've finished preparing your release, select Review release.
  12. If the non-compliant APK/app bundle is released to multiple tracks, repeat steps 5-9 in each track.

During this time your new app or app update displays an "in review" status until your request is completed. If the app has not been updated correctly, app stability notifications will continue to be sent to your Play Console. 

We’re here to help

If you have technical questions about the issue, you can post to Stack Overflow and use the tag “android-stability.” For clarification on steps you need to take to resolve this issue, you can contact our support team.

這對您有幫助嗎?

我們應如何改進呢?
false
Google apps
Main menu
13147898582091329336
true
搜尋說明中心
true
true
true
true
true
5016068
false
false