Java lang error fatal exception xiaomi

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

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

Error MainActivity #30

Error MainActivity #30

Comments

Hello I have an error while running the application under android when I call the function to launch unity, I have the following error:

06-29 16:04:47.106 18699-18699/fr.xx.xx E/ActivityThread: Activity fr.xx.xx.MainActivity has leaked IntentReceiver org.apache.cordova.plugin.CordovaUnityLauncher$UnityToIonicBroadcastReceiver@ec2200e that was originally registered here. Are you missing a call to unregisterReceiver()?

Compilation is not a problem.

The text was updated successfully, but these errors were encountered:

Inside Android Studio, can you verify that CordovaUnityLauncher.java is the same as above? How about making broadcastReceiverRegistered a static variable? Does it fix the issue?

Yes inside the Android Studio is same file.

here is the device report:

java.lang.Error: FATAL EXCEPTION [main] Unity version : 2018.1.6f1 Device model : Xiaomi Redmi 5 Plus Device fingerprint: xiaomi/vince/vince:7.1.2/N2G47H/V9.5.12.0.NEGMIFA:user/release-keys Caused by: java.lang.UnsatisfiedLinkError: No implementation found for void com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator() (tried Java_com_unity3d_player_UnityPlayer_nativeRestartActivityIndicator and Java_com_unity3d_player_UnityPlayer_nativeRestartActivityIndicator__) at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator(Native Method) at com.unity3d.player.UnityPlayer.resume(Unknown Source) at com.unity3d.player.UnityPlayerActivity.onResume(Unknown Source) at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1270) at android.app.Activity.performResume(Activity.java:6988) at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3497) at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3560) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2808) at android.app.ActivityThread.-wrap12(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1549) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:163) at android.app.ActivityThread.main(ActivityThread.java:6379) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794) 

however, at the function level: onActivityResult

the return code is:
requestCode = 0
resultCode = 0
Activity.RESULT_OK = -1

Can I see the contents of your jniLibs, with subdirectories expanded? Also, what is your Unity version?

My Unity Version is 2018.1.6f1

I can see libmain.so and libunity.so in your jniLibs; which is a good sign. But it is also bad news because now I can’t think of any reasons for the java.lang.UnsatisfiedLinkError to occur.

Can you build your Unity project to another empty folder, open it in Android Studio and run the project on your Xiaomi device to see if it works from Android Studio without Ionic integration?

Then, can you try running the Unity integrated Ionic project on an emulator to see if the issue is related to Xiaomi device? I’d suggest you to test the project on both an ARM emulator and an x86 Intel emulator.

Ok, so the project generate from Unity without ionic integration and launch from Android Studio works perfectly. On the Android emulator the ionic / Unity project is running without problems.

What are the specs of your emulator?

android 8 api 26 X86 base of Pixel 2 XL

06-30 14:40:42.960 20133-20227/fr.neomabs.lx I/Timeline: Timeline: Activity_launch_request time:2694546 intent:Intent < cmp=fr.neomabs.lx/com.unitycaller.ionic.UnityPlayerExtendedActivity (has extras) >06-30 14:40:42.971 20133-20133/fr.neomabs.lx D/CordovaActivity: Paused the activity. 06-30 14:40:43.001 20133-20227/fr.neomabs.lx W/PluginManager: THREAD WARNING: exec() call to LaunchAR.launchAR blocked the main thread for 45ms. Plugin should use CordovaInterface.getThreadPool(). 06-30 14:40:43.016 20133-20227/fr.neomabs.lx D/YoikScreenOrientation: execute action: screenOrientation Requested ScreenOrientation: any 06-30 14:40:43.360 20133-20133/fr.neomabs.lx D/CordovaActivity: Stopped the activity. CordovaActivity.onDestroy() 06-30 14:40:43.369 20133-20133/fr.neomabs.lx D/CordovaWebViewImpl: >>> loadUrl(about:blank) 06-30 14:40:43.372 20133-20133/fr.neomabs.lx W/cr_AwContents: WebView.destroy() called while WebView is still attached to window. 06-30 14:40:43.387 20133-20133/fr.neomabs.lx W/ContentCatcher: Failed to notify a WebView 06-30 14:40:43.392 20133-20133/fr.neomabs.lx W/cr_AwContents: Application attempted to call on a destroyed WebView java.lang.Throwable at org.chromium.android_webview.AwContents.f(SourceFile:310) at org.chromium.android_webview.AwContents.a(SourceFile:282) at org.chromium.android_webview.AwContents.q(SourceFile:529) at ass.loadingStateChanged(SourceFile:159) at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method) at org.chromium.base.SystemMessageHandler.handleMessage(SourceFile:9) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:163) at android.app.ActivityThread.main(ActivityThread.java:6396) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:794) 

Pixel 2 XL: 64-bit ARM
Xiaomi Redmi 5 Plus: 32-bit ARM

If Pixel 2 XL emulator had an Intel (x86) processor, then it’d suggest that there might be something wrong with the ARM libraries of Unity. However, now that is not an option. To be honest, I don’t have any clues about this problem at this point. What I’d suggest you to do is first try Ionic integration with an empty Unity project and see if it works on Xiaomi. If not, you can try using a different Unity version.

Regarding the latest logcat error, if it doesn’t crash the app or doesn’t seem to affect anything, then I think it is harmless.

I’ve solved this issue by deleting the x86 jniLibs and replacing the arm .so files with an older export from unity. It seems that the .so didn’t export corectly. DId you by any change upgrade to another version of unity before getting this error?

Could you share the file with us?

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

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

Crash on Xiaomi Caused by java.lang.NullPointerException #2823

Crash on Xiaomi Caused by java.lang.NullPointerException #2823

Comments

• Unity version: Not Related
• Google Mobile Ads Unity plugin version: 8.2.0
• Platform: Android
• Any specific devices issue occurs on: Xiaomi

Step 2: Describe the problem
on firebase crashlytics dashboard i am seeing this crash. not sure its related to admob or not. But it is few lines related to com.google.android.gms.ads. Please discard if not related to admob.

Crashlytics — Stack trace

Fatal Exception: java.lang.Error: FATAL EXCEPTION [AdWorker(Default) # 16]
Unity version : 2021.3.23f1
Device model : Xiaomi M2103K19I
Device fingerprint: Redmi/camellia_in/camellia:12/SP1A.210812.016/V13.0.7.0.SKSINXM:user/release-keys
Build Type : Release
Scripting Backend : IL2CPP
ABI : arm64-v8a
Strip Engine Code : true

Caused by java.lang.NullPointerException: Attempt to invoke virtual method ‘int android.os.Bundle.size()’ on a null object reference
at android.os.Parcel.createExceptionOrNull(Parcel.java:2432)
at android.os.Parcel.createException(Parcel.java:2410)
at android.os.Parcel.readException(Parcel.java:2393)
at android.os.Parcel.readException(Parcel.java:2335)
at android.view.IWindowManager$Stub$Proxy.getSupportedDisplayHashAlgorithms(IWindowManager.java:6126)
at android.view.displayhash.DisplayHashManager.getSupportedHashAlgorithms(DisplayHashManager.java:71)
at com.google.android.gms.ads.eventattestation.internal.l.(:com.google.android.gms.policy_ads_fdr_dynamite@231710101@231710100057.526733554.526733554:2)
at com.google.android.gms.ads.nonagon.ad.j.e(:com.google.android.gms.policy_ads_fdr_dynamite@231710101@231710100057.526733554.526733554:11)
at com.google.android.gms.ads.nonagon.ad.g.run(:com.google.android.gms.policy_ads_fdr_dynamite@231710101@231710100057.526733554.526733554)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)

Complete Stack Trace is attached.
crash.txt

The text was updated successfully, but these errors were encountered:

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

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

com.google.android.gms.common.api.internal.GoogleApiManager$zac.zag #2805

com.google.android.gms.common.api.internal.GoogleApiManager$zac.zag #2805

Comments

Samsung Galaxy J4 Core(j4corelte), Android 8.1

java.lang.Error: FATAL EXCEPTION [GoogleApiHandler]
Unity version : 2019.2.14f1
Device model : samsung SM-J410G
Device fingerprint: samsung/j4corelteub/j4corelte:8.1.0/M1AJB/J410GUBS1ASK4:user/release-keys
Caused by
at com.google.android.gms.common.api.internal.GoogleApiManager$zac.zag (Unknown Source:10)
at com.google.android.gms.common.api.internal.zace.zac (Unknown Source:45)
at com.google.android.gms.common.api.internal.zace.zaa (Unknown Source:49)
at com.google.android.gms.common.api.internal.zacg.run (Unknown Source:2)
at android.os.Handler.handleCallback (Handler.java:790)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:164)
at android.os.HandlerThread.run (HandlerThread.java:65)

Samsung Galaxy A3(2016)(a3xeltekx), Android 7.0

java.lang.Error: FATAL EXCEPTION [GoogleApiHandler]
Unity version : 2019.2.14f1
Device model : samsung SM-A310N0
Device fingerprint: samsung/a3xeltekx/a3xeltekx:7.0/NRD90M/A310N0KOU1CQL2:user/release-keys
Caused by
at com.google.android.gms.common.api.internal.GoogleApiManager$zac.zag (Unknown Source)
at com.google.android.gms.common.api.internal.zace.zac (Unknown Source)
at com.google.android.gms.common.api.internal.zace.zaa (Unknown Source)
at com.google.android.gms.common.api.internal.zacg.run (Unknown Source)
at android.os.Handler.handleCallback (Handler.java:751)
at android.os.Handler.dispatchMessage (Handler.java:95)
at android.os.Looper.loop (Looper.java:154)
at android.os.HandlerThread.run (HandlerThread.java:61)

Xiaomi Redmi 7(onc), Android 9

java.lang.Error: FATAL EXCEPTION [GoogleApiHandler]
Unity version : 2019.2.14f1
Device model : Xiaomi Redmi 7
Device fingerprint: xiaomi/onc_eea/onc:9/PKQ1.181021.001/V11.0.3.0.PFLEUXM:user/release-keys
Caused by
at com.google.android.gms.common.api.internal.GoogleApiManager$zac.zag (Unknown Source:10)
at com.google.android.gms.common.api.internal.zace.zac (Unknown Source:45)
at com.google.android.gms.common.api.internal.zace.zaa (Unknown Source:49)
at com.google.android.gms.common.api.internal.zacg.run (Unknown Source:2)
at android.os.Handler.handleCallback (Handler.java:873)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:201)
at android.os.HandlerThread.run (HandlerThread.java:65)

The text was updated successfully, but these errors were encountered:

Источник