java.lang.VerifyError: Verifier rejected class [293501981]

Verified

Bug

Status Update

No update yet.

Description

an...@airbnb.com

created issue #1

Jul 28, 2023 04:57PM

DESCRIBE THE ISSUE IN DETAIL:

Our app started crashing today out of the blue without any code change (or tooling version upgrades) to the code in question:

java.lang.VerifyError: Verifier rejected class s90.b: void s90.b.ǃ(o52.c, u52.a) failed to verify: void s90.b.ǃ(o52.c, u52.a): [0x244] copy1 v26<-v11 type=Undefined cat=3 (declaration of 's90.b' appears in /data/app/~~5Xr2Mb1qMgb3r7pQ7m9qrA==/com.airbnb.android-X4F2fwfbB2MHV1HUOdtkEw==/base.apk!classes16.dex)
at z90.b$a.invokeSuspend(CalendarEditViewModel.kt:118)
at z90.b$a.invoke(CalendarEditViewModel.kt:13)
at kotlinx.coroutines.flow.FlowKt__MergeKt$mapLatest$1.invokeSuspend(Merge.kt:49)
at kotlinx.coroutines.flow.FlowKt__MergeKt$mapLatest$1.invoke(Merge.kt:2)
at kotlinx.coroutines.flow.FlowKt__MergeKt$mapLatest$1.invoke(Merge.kt:1)
at kotlinx.coroutines.flow.internal.ChannelFlowTransformLatest$flowCollect$3$1$2.invokeSuspend(Merge.kt:37)
at kotlinx.coroutines.flow.internal.ChannelFlowTransformLatest$flowCollect$3$1$2.invoke(Merge.kt:2)
at kotlinx.coroutines.flow.internal.ChannelFlowTransformLatest$flowCollect$3$1$2.invoke(Merge.kt:1)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startCoroutineUndispatched(Undispatched.kt:14)
at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:28)
at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:1)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:23)
at kotlinx.coroutines.BuildersKt.launch(Unknown Source:1)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:13)
at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source:1)
at kotlinx.coroutines.flow.internal.ChannelFlowTransformLatest$flowCollect$3$1.emit(Merge.kt:111)
at kotlinx.coroutines.flow.SharedFlowImpl.collect$suspendImpl(SharedFlow.kt:202)
at kotlinx.coroutines.flow.SharedFlowImpl$collect$1.invokeSuspend(SharedFlow.kt:13)
at kotlin.coroutines.jvm.internal.a.resumeWith(ContinuationImpl.kt:6)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:105)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:1)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:15)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:29)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:1)

I saw several of those fixed in the past months so we updated to latest version of R8 (4.0.64) but we are still seeing it.

We are working around this right now by just keeping the class in question but I think this is a bug in R8.

I included the broken .aab and .apk files and also an input dump and shared it with "the usual" people. Happy to share it with others if required, or provide more information.

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: Not relevant Version of Gradle Plugin: 7.4.2 Version of Kotlin: 1.8.21 Version of Gradle: 7.6 Version of Java: openjdk 17.0.8 2023-07-18 LTS OS: Linux

https://drive.google.com/file/d/1ggIkdj93p1XEon-u-gJHEW127kmQk_lq/view?usp=drive_web (release_global_airbnb.gz)

https://drive.google.com/file/d/1VO_s1gOXew1G_WtFKC-J9kQm5dN5SuW5/view?usp=drive_web (r8_dump_release_global_airbnb.zip)

Comments

ar...@google.com <ar...@google.com> Jul 28, 2023 06:45PM

Assigned to an...@google.com.

an...@airbnb.com <an...@airbnb.com> #2Jul 28, 2023 11:49PM

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

ri...@google.com <ri...@google.com> Jul 31, 2023 07:59AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #3Jul 31, 2023 09:08AM

the fractional part of the location data is exactly the same.

an...@airbnb.com <an...@airbnb.com> #4Jul 31, 2023 05:21PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. AP4A.241205.013.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

ch...@google.com <ch...@google.com> #5Aug 2, 2023 11:49AM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

ch...@google.com <ch...@google.com> #6Aug 4, 2023 10:59AM

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。

as for Android build,all versions have it.
I dont reprodouce this issue.

what may be the cause of this issue?please

an...@airbnb.com <an...@airbnb.com> #7Aug 4, 2023 06:06PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ch...@google.com <ch...@google.com> #8Aug 7, 2023 01:08PM

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

ch...@google.com <ch...@google.com> #9Aug 9, 2023 06:07AM

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

ap...@google.com <ap...@google.com> #10Aug 11, 2023 05:55AM

Thank you very much! it is very useful to me . It solved my confusion.

ap...@google.com <ap...@google.com> #11Aug 11, 2023 07:47AM

Project: r8
Branch: main

commit 18021f50bf2661a1c1aa6312004b3da2ef107ca7
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Fri Aug 11 08:22:16 2023

Only allow instances of final classes in filled-new-array

Bug:

Issue 293501981

Description

Issue summary

Comments

ar...@google.com <ar...@google.com> Jul 28, 2023 06:45PM

an...@airbnb.com <an...@airbnb.com> #2Jul 28, 2023 11:49PM

ri...@google.com <ri...@google.com> Jul 31, 2023 07:59AM

ch...@google.com <ch...@google.com> #3Jul 31, 2023 09:08AM

an...@airbnb.com <an...@airbnb.com> #4Jul 31, 2023 05:21PM

ch...@google.com <ch...@google.com> #5Aug 2, 2023 11:49AM

ch...@google.com <ch...@google.com> #6Aug 4, 2023 10:59AM

an...@airbnb.com <an...@airbnb.com> #7Aug 4, 2023 06:06PM

ch...@google.com <ch...@google.com> #8Aug 7, 2023 01:08PM

ch...@google.com <ch...@google.com> #9Aug 9, 2023 06:07AM

ap...@google.com <ap...@google.com> #10Aug 11, 2023 05:55AM

ap...@google.com <ap...@google.com> #11Aug 11, 2023 07:47AM

ap...@google.com <ap...@google.com> #12Aug 11, 2023 07:47AM

ap...@google.com <ap...@google.com> #13Aug 11, 2023 08:28AM

ap...@google.com <ap...@google.com> #14Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #15Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #16Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #17Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #18Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #19Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #20Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #21Aug 11, 2023 11:00AM

ap...@google.com <ap...@google.com> #22Aug 11, 2023 11:02AM

ap...@google.com <ap...@google.com> #23Aug 11, 2023 11:02AM

ap...@google.com <ap...@google.com> #24Aug 11, 2023 11:02AM

ap...@google.com <ap...@google.com> #25Aug 11, 2023 11:16AM

ap...@google.com <ap...@google.com> #26Aug 11, 2023 11:16AM

ap...@google.com <ap...@google.com> #27Aug 11, 2023 11:16AM

ap...@google.com <ap...@google.com> #28Aug 11, 2023 11:16AM

ap...@google.com <ap...@google.com> #29Aug 11, 2023 11:18AM

ap...@google.com <ap...@google.com> #30Aug 13, 2023 11:52AM

ap...@google.com <ap...@google.com> #31Aug 13, 2023 03:04PM

ap...@google.com <ap...@google.com> #32Aug 13, 2023 03:04PM

ap...@google.com <ap...@google.com> #33Aug 13, 2023 03:05PM

ap...@google.com <ap...@google.com> #34Aug 13, 2023 03:06PM

ch...@google.com <ch...@google.com> #35Aug 14, 2023 08:32AM

an...@airbnb.com <an...@airbnb.com> #36Sep 5, 2023 06:16PM

Add comment

Issue metadata