Question

最近一次更新后，看到我们统一制作的游戏在Google Play控制台上崩溃，这种情况在Android 5.0上发生的机率超过了99％。我猜想这与WebView有关，并且看到了这篇相关文章： https://bugs.chromium.org/p/chromium/issues/detail?id=559720 但是，这似乎与我们的情况不符，因为我们在最近的更新后才看到此崩溃，并且几乎所有事件都发生在Android 5.0上。我们仍在使用Facebook SDK 4.9.0，想知道它是否太旧了。 Stacktrace如下：

java.lang.Error: FATAL EXCEPTION [main]
Unity version     : 5.6.3f1
Device model      : positivo S455
Device fingerprint: Positivo/S455/S455:5.0.2/LRX22G/URBR2017051601:user/release-keys
Caused by
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3136)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3167)
  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2522)
  at android.app.ActivityThread.access$800 (ActivityThread.java:162)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1412)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:189)
  at android.app.ActivityThread.main (ActivityThread.java:5529)
  at java.lang.reflect.Method.invoke (Native Method)
  at java.lang.reflect.Method.invoke (Method.java:372)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:951)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:746)
Caused by: java.lang.IllegalArgumentException: 
  at dalvik.system.VMRuntime.getInstructionSet (VMRuntime.java:324)
  at dalvik.system.VMRuntime.is64BitAbi (VMRuntime.java:337)
  at android.webkit.WebViewFactory.getWebViewNativeLibraryPaths (WebViewFactory.java:273)
  at android.webkit.WebViewFactory.loadNativeLibrary (WebViewFactory.java:384)
  at android.webkit.WebViewFactory.getProvider (WebViewFactory.java:95)
  at android.webkit.CookieManager.getInstance (CookieManager.java:46)
  at android.webkit.CookieSyncManager.sync (CookieSyncManager.java:108)
  at com.facebook.internal.Utility.clearCookiesForDomain (Utility.java:694)
  at com.facebook.internal.Utility.clearFacebookCookies (Utility.java:719)
  at com.facebook.login.WebViewLoginMethodHandler.tryAuthorize (WebViewLoginMethodHandler.java:104)
  at com.facebook.login.LoginClient.tryCurrentHandler (LoginClient.java:249)
  at com.facebook.login.LoginClient.tryNextHandler (LoginClient.java:211)
  at com.facebook.login.LoginClient.authorize (LoginClient.java:127)
  at com.facebook.login.LoginClient.startOrContinueAuth (LoginClient.java:108)
  at com.facebook.login.LoginFragment.onResume (LoginFragment.java:152)
  at android.support.v4.app.Fragment.performResume (Fragment.java:2401)
  at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1465)
  at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState (FragmentManager.java:1740)
  at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1809)
  at android.support.v4.app.FragmentManagerImpl.dispatchStateChange (FragmentManager.java:3217)
  at android.support.v4.app.FragmentManagerImpl.dispatchResume (FragmentManager.java:3181)
  at android.support.v4.app.FragmentController.dispatchResume (FragmentController.java:214)
  at android.support.v4.app.FragmentActivity.onResumeFragments (FragmentActivity.java:470)
  at android.support.v4.app.FragmentActivity.onPostResume (FragmentActivity.java:459)
  at android.app.Activity.performResume (Activity.java:6065)
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3121)

Answer 1

此问题与32/64位设备之间的不匹配有关。此处的chrome.org中存在一个错误：https://bugs.chromium.org/p/chromium/issues/detail?id=559720#c2

“不支持的ABI：空”可能表示32/64位不匹配。当供应商发布OTA将64位设备从32位升级到64位Android时，我们一直看到一个问题。 PlayStore中存在一个错误，此类设备将继续获得32位WebView。那可能就是这里发生的事情。我们为此打开了一个内部错误，但我无法确定何时修复。 :(用户可以通过在“设置”中卸载WebView更新，然后在Play商店中重新更新WebView来获得正确的版本。

引用上述来源的另一条评论：

该问题应在用户下次出于任何原因运行Play商店应用后自行解决（该问题仅在自动更新期间发生，运行Play商店可修复导致其安装错误软件包的错误状态）。 / p>

IllegalArgumentException：不支持的ABI：Android 5.0上的VMRuntime.getInstructionSet（）中为null

1 个答案: