Dalvik crash on Oneplus on Android 12 - android

I've got an app in the play store, and have just started seeing the following crash on crashlytics as we're releasing a new version:
Fatal Exception: java.lang.VerifyError: Verifier rejected class app.models.basket.BasketPrice: app.models.pricing.Money app.models.basket.BasketPrice.component1() failed to verify: app.models.pricing.Money app.models.basket.BasketPrice.component1(): [0x2] return-wide not expected
app.models.pricing.Money app.models.basket.BasketPrice.component2() failed to verify: app.models.pricing.Money app.models.basket.BasketPrice.component2(): [0x2] return-wide not expected
app.models.pricing.Money app.models.basket.BasketPrice.component3() failed to verify: app.models.pricing.Money app.models.basket.BasketPrice.component3(): [0x2] return-wide not expected (declaration of 'app.models.basket.BasketPrice' appears in /data/app/~~SMvMJ3wjLcBZoO_7ATEdrA==/app-MRhsaTqPRxyDfq-Ma3jNMA==/base.apk)
at app.models.basket.BasketPriceJsonAdapter.fromJson(BasketPriceJsonAdapter.kt:53)
at app.models.basket.BasketPriceJsonAdapter.fromJson(BasketPriceJsonAdapter.kt:21)
at com.squareup.moshi.internal.NullSafeJsonAdapter.fromJson(NullSafeJsonAdapter.java:41)
at app.models.basket.BasketPricedFulfilmentOptionJsonAdapter.fromJson(BasketPricedFulfilmentOptionJsonAdapter.kt:57)
at app.models.basket.BasketPricedFulfilmentOptionJsonAdapter.fromJson(BasketPricedFulfilmentOptionJsonAdapter.kt:22)
at com.squareup.moshi.internal.NullSafeJsonAdapter.fromJson(NullSafeJsonAdapter.java:41)
at app.models.basket.BasketPricedFulfilmentOptionsJsonAdapter.fromJson(BasketPricedFulfilmentOptionsJsonAdapter.kt:37)
at app.models.basket.BasketPricedFulfilmentOptionsJsonAdapter.fromJson(BasketPricedFulfilmentOptionsJsonAdapter.kt:20)
at com.squareup.moshi.internal.NullSafeJsonAdapter.fromJson(NullSafeJsonAdapter.java:41)
at app.models.basket.BasketResponseJsonAdapter.fromJson(BasketResponseJsonAdapter.kt:79)
at app.models.basket.BasketResponseJsonAdapter.fromJson(BasketResponseJsonAdapter.kt:24)
at com.squareup.moshi.internal.NullSafeJsonAdapter.fromJson(NullSafeJsonAdapter.java:41)
at app.models.DataWrapperJsonAdapter.fromJson(DataWrapperJsonAdapter.kt:44)
at app.models.DataWrapperJsonAdapter.toJson(DataWrapperJsonAdapter.kt:22)
at com.squareup.moshi.internal.NullSafeJsonAdapter.fromJson(NullSafeJsonAdapter.java:41)
at retrofit2.converter.moshi.MoshiResponseBodyConverter.convert(MoshiResponseBodyConverter.java:46)
at retrofit2.converter.moshi.MoshiResponseBodyConverter.convert(MoshiResponseBodyConverter.java:27)
at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:243)
at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:153)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
I can't find anyone with this same return-wide not expected issue anywhere on the internet, although the VerifyError thing seems to be when the Dalvik runtime runs into issues.
My theory at the moment is that this is just a device specific issue for Oneplus Android 12 devices, but the stacktrace is in our(/Moshi) code, and it seems to only be on the new version, so I feel like there's some kind of aggravating factor. Can anyone say why this is happening?

Related

App started crashing after upgrading app targetSDK to 32

I've upgraded my app target SDK 30 to 32, after updating created the release build & installed the builds over the older build(In short, I update the app on the device).
Now,app started crashing after this update & getting the following crash logs.
FATAL EXCEPTION: OkHttp Dispatcher
Process: com.zerion.apps.iform.main, PID: 7750
java.lang.VerifyError: Superclass c.a of c.g is declared final (declaration of 'c.g' appears in /data/app/~~B1TWx2zBH9lfzsGOMr146Q==/com.zerion.apps.iform.main-MzBcSg49f0sTgamcKa69Ag==/base.apk!classes2.dex)
at j$.time.format.DateTimeFormatter.<clinit>(Unknown Source:35)
at com.zerionsoftware.iformdomainsdk.domain.logging.LogMessageGenerator.createMessage(SourceFile:1)
at com.zerionsoftware.iformdomainsdk.data.retrofit.LoggingInterceptor.intercept(SourceFile:5)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:10)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:1)
at com.zerionsoftware.iformdomainsdk.data.retrofit.NetworkConnectionInterceptor.intercept(SourceFile:3)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:10)
at okhttp3.internal.http.RealInterceptorChain.proceed(SourceFile:1)
at okhttp3.RealCall.getResponseWithInterceptorChain(SourceFile:13)
at okhttp3.RealCall$AsyncCall.execute(SourceFile:2)
at okhttp3.internal.NamedRunnable.run(SourceFile:3)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:920)
I'm working on this issue so long, but unable to find the exact problem.

Does the Google Play Console log all crashes?

I have a crash that has slowly crept up in crash rate over my last few releases. All attempts to fix the crash have proved futile. I suspect that the crash happens in the background and users are not actually seeing the issue, else I would have many more reviews about the app crashing.
Do users still need to tap the the crash module that pops up in order for Google to log the crash or does the crash report get sent automatically at this point?
I can not find a definitive answer to this.
Here is the crash if anyone has ideas. There is a lot of info available on that I have tried as well as anything else I could think of. Dug through every SDK, reverted back to previous target API, turned off features etc etc :(
java.lang.RuntimeException: An error occurred while executing doInBackground()
at
android.os.AsyncTask$3.done(AsyncTask.java:354)
at
java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at
java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at
java.util.concurrent.FutureTask.run(FutureTask.java:271)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at
java.lang.Thread.run(Thread.java:798)
Caused by: java.lang.SecurityException: Caller no longer running, last stopped +2s531ms because: timed out while starting
at
android.os.Parcel.createException(Parcel.java:1950)
at
android.os.Parcel.readException(Parcel.java:1918)
at
android.os.Parcel.readException(Parcel.java:1868)
at
android.app.job.IJobCallback$Stub$Proxy.dequeueWork(IJobCallback.java:195)
at
android.app.job.JobParameters.dequeueWork(JobParameters.java:243)
at
androidx.core.app.JobIntentService$JobServiceEngineImpl.dequeueWork(:4)
at
androidx.core.app.JobIntentService.dequeueWork(:2)
at
androidx.core.app.JobIntentService$CommandProcessor.doInBackground(:2)
at
androidx.core.app.JobIntentService$CommandProcessor.doInBackground(:1)
at
android.os.AsyncTask$2.call(AsyncTask.java:333)
at
java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at
java.lang.Thread.run(Thread.java:798)
Caused by: android.os.RemoteException: Remote stack trace:
at
com.android.server.job.JobServiceContext.assertCallerLocked(JobServiceContext.java:481)
at
com.android.server.job.JobServiceContext.doDequeueWork(JobServiceContext.java:359)
at
com.android.server.job.JobServiceContext$JobCallback.dequeueWork(JobServiceContext.java:160)
at
android.app.job.IJobCallback$Stub.onTransact(IJobCallback.java:83)
at
android.os.Binder.execTransact(Binder.java:746)

Google ML Kit Text Recognition(v16.1.3) crashes after upgrading the dependency

After upgrading the Text Recognition dependency from 16.1.1 to 16.1.3:
com.google.android.gms:play-services-mlkit-text-recognition:16.1.3
on some devices(Realme 3 Pro Android 10), the app starts crashing when calling
TextRecognition.getClient().process(InputImage.fromFilePath(context, data)).await()
here is the stack trace from firebase:
Non-fatal Exception: f.b.e.a.a: Failed to init thin text recognizer.
at com.google.mlkit.vision.text.internal.zzb.zza(zzb.java:47)
at com.google.mlkit.vision.text.internal.zzn.load(zzn.java:3)
at com.google.mlkit.common.sdkinternal.ModelResource.zza(ModelResource.java:18)
at com.google.mlkit.common.sdkinternal.zzn.run(zzn.java:10)
at com.google.mlkit.common.sdkinternal.zzp.run(zzp.java:10)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zze(MlKitThreadPool.java:13)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzc(MlKitThreadPool.java:8)
at com.google.mlkit.common.sdkinternal.zzj.run(zzj.java:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzd(MlKitThreadPool.java:10)
at com.google.mlkit.common.sdkinternal.zzk.run(zzk.java:2)
at java.lang.Thread.run(Thread.java:919)
Caused by android.os.RemoteException: Not allowed since feature flag for ML Kit is not enabled.
at ii.a(ii.java)
at com.google.android.gms.vision.text.mlkit.TextRecognizerCreator.newTextRecognizer(TextRecognizerCreator.java:11)
at com.google.android.gms.vision.text.mlkit.TextRecognizerCreator.newTextRecognizer(TextRecognizerCreator.java)
at mu.u(mu.java:4)
at al.onTransact(al.java:4)
at android.os.Binder.transact(Binder.java:914)
at com.google.android.gms.internal.mlkit_vision_text.zza.zzb(zza.java:7)
at com.google.android.gms.internal.mlkit_vision_text.zzlh.zzd(zzlh.java:8)
at com.google.mlkit.vision.text.internal.zzb.zza(zzb.java:30)
at com.google.mlkit.vision.text.internal.zzn.load(zzn.java:3)
at com.google.mlkit.common.sdkinternal.ModelResource.zza(ModelResource.java:18)
at com.google.mlkit.common.sdkinternal.zzn.run(zzn.java:10)
at com.google.mlkit.common.sdkinternal.zzp.run(zzp.java:10)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zze(MlKitThreadPool.java:13)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzc(MlKitThreadPool.java:8)
at com.google.mlkit.common.sdkinternal.zzj.run(zzj.java:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at com.google.mlkit.common.sdkinternal.MlKitThreadPool.zzd(MlKitThreadPool.java:10)
at com.google.mlkit.common.sdkinternal.zzk.run(zzk.java:2)
at java.lang.Thread.run(Thread.java:919)
The feature flag should already be enabled everywhere, it may due to your play services have not received the update. You can reboot your device to see if the issue gets resolved.
See github.com/googlesamples/mlkit/issues/236 for a similar report.

Installation apk in android 8.0 error

I have benn trying for many days to install an app on any device using android oreo either in debug mode with android studio either by creating apk, but I still fail. At the beggining I had issue described here install_failed_no_matching_abis failed to extract native libraries res=-113 after updating to android 8.0 oreo
and while I am trying to solve this I get different errors all the time.
When I set android.enableAapt2=true I get this error
when I set android.enableAapt2=false I get warning
The option 'android.enableAapt2' is deprecated and should not be used anymore.
Use 'android.enableAapt2=true' to remove this warning.
I`t will be removed at the end of 2018..`
and finally this error comes up
and this in log Mesagges
04-17 01:37:27.331 9763-11258/? E/xiy: Job(ItemMessageAttachmentsCacheEvictorJob#0.126) Enqueued job 'ItemMessageAttachmentsCacheEvictorJob' failed
java.lang.IllegalArgumentException: Attachment cache cannot be null.
at piu.a(Unknown Source:4)
at pki.a(Unknown Source:17)
at yik.a(SourceFile:1)
at xik.b(SourceFile:2)
at xil.a(Unknown Source:4)
at yik.a(SourceFile:1)
at yhr.run(SourceFile:1)
at wzc.run(Unknown Source:3)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:782)
Either way I cannot install my app on any device running oreo although it works fine up to nougat.Even if I buld apk ig get error parsing apk file.

Crosswalk not working with Android 4.1 "Project Runtime Not Found" Error

I cannot get a Cordova app using Crosswalk to run on Android 4.1. I have built my app with Crosswalk and had it working on 4.1 2 months ago, but it's not.
I put my app aside and did all the debugging with a blank Cordova project, with only 3 plugins. Using instructions from here.
cordova-plugin-whitelist
cordova-plugin-network-information
cordova-plugin-crosswalk-webview
I have no build problems, but when I try and run the app on the phone it crashes right away. I am testing on the Android 4.1.2 emulator image. The following are the logcat ERROR's
11-17 03:25:26.645 1256-1256/com.cordova.blank E/Trace: error opening trace file: No such file or directory (2)
11-17 03:25:28.315 1256-1256/com.cordova.blank E/libEGL: validate_display:209 error 3008 (EGL_BAD_DISPLAY)
11-17 03:25:28.315 1256-1256/com.cordova.blank E/libEGL: validate_display:209 error 3008 (EGL_BAD_DISPLAY)
11-17 03:25:28.325 1256-1256/com.cordova.blank E/chromium: [ERROR:gl_surface_egl.cc(327)] No suitable EGL configs found.
11-17 03:25:28.325 1256-1256/com.cordova.blank E/chromium: [ERROR:gl_surface_android.cc(23)] GLSurfaceEGL::InitializeOneOff failed.
11-17 03:25:28.325 1256-1256/com.cordova.blank E/chromium: [ERROR:browser_main_loop.cc(698)] GLSurface::InitializeOneOff failed
11-17 03:25:28.404 1256-1288/com.cordova.blank E/dalvikvm: Could not find class 'android.bluetooth.BluetoothManager', referenced from method org.chromium.media.AudioManagerAndroid.hasBluetoothHeadset
11-17 03:25:28.455 1256-1256/com.cordova.blank E/chromium: [ERROR:xwalk_platform_notification_service.cc(103)] Not implemented reached in virtual bool xwalk::XWalkPlatformNotificationService::GetDisplayedPersistentNotifications(content::BrowserContext*, std::set<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >*)
11-17 03:25:28.515 1256-1256/com.cordova.blank E/chromium: [ERROR:xwalk_browser_context.cc(79)] Failed to read preference, error num: 0
11-17 03:25:28.585 1256-1293/com.cordova.blank E/chromium: [ERROR:unix_domain_server_socket_posix.cc(106)] Not implemented reached in virtual int net::UnixDomainServerSocket::GetLocalAddress(net::IPEndPoint*) const
11-17 03:25:28.616 1256-1256/com.cordova.blank E/dalvikvm: Could not find class 'org.xwalk.core.internal.extension.api.DisplayManagerJBMR1', referenced from method org.xwalk.core.internal.extension.api.XWalkDisplayManager.getInstance
11-17 03:25:28.725 1256-1256/com.cordova.blank E/dalvikvm: Could not find class 'org.chromium.content.browser.ScreenOrientationListener$ScreenOrientationDisplayListener', referenced from method org.chromium.content.browser.ScreenOrientationListener.<init>
11-17 03:25:29.125 1256-1298/com.cordova.blank A/libc: Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1298 (Chrome_InProcGp)
I have tried with Crosswalk 14 & 15 latest stable releases. I have tried with both Cordova 5.3.3 and Cordova 5.0.0
I also have a Blackberry 10 emulator, the app on it doesn't crash right away, instead an error dialog is presented.
The minSdkVersion is set to 16.
The test app loads fine with no Crosswalk added.
I have also tried all of the above with Ionic.
The app works fine on Android 4.3 emulator and on my physical Android 5.1.1 device.
I can also reproduce this issue, a JIRA ticket has been created for Crosswalk team, please track here https://crosswalk-project.org/jira/browse/XWALK-5791.
I am so sorry for my mistake, I didn’t realize that is an arm architecture device, I installed an x86 apk.
I tried again with an arm apk on ZTE U5(android 4.1) device, this issue disappeared.
Did you meet the same situation with me?

Categories

Resources