AGP 8.3.0-alpha11 produces release APK that crashes on startup with android.content.res.Resources$NotFoundException [307987906]

Fixed

Bug

Status Update

No update yet.

Description

pu...@gmail.com

created issue #1

Oct 27, 2023 10:59AM

Studio Build: Iguana Canary 11 Version of Gradle Plugin: 8.3.0-alpha11

Version of Gradle: 8.4

Version of Java: 17.0.9

OS: Linux

If I generate a (clean) release APK of my app with minification/obfuscation enabled, it will crash on app startup when it loads an XML layout with android.content.res.Resources$NotFoundException:

Caused by: android.view.InflateException: Binary XML file line #36 in <package name>:layout/abc_search_view: Binary XML file line #36 in <package name>:layout/abc_search_view: Error inflating class TextView
Caused by: android.view.InflateException: Binary XML file line #36 in <package name>:layout/abc_search_view: Error inflating class TextView
Caused by: android.content.res.Resources$NotFoundException: Unable to find resource ID #0x7f0902cd

There is no such issue with 8.3.0-alpha11

Comments

pu...@gmail.com <pu...@gmail.com> #2Oct 27, 2023 11:01AM

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?

so...@google.com <so...@google.com> Oct 27, 2023 01:26PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Oct 30, 2023 04:29PM

Reassigned to lu...@google.com.

cm...@google.com <cm...@google.com> #3Oct 30, 2023 06:38PM

Reassigned to ri...@google.com.

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

Message last modified on Oct 30, 2023 06:40PM

pu...@gmail.com <pu...@gmail.com> #4Oct 30, 2023 07:49PM

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.

Message last modified on Oct 30, 2023 07:53PM

pu...@gmail.com <pu...@gmail.com> #5Oct 30, 2023 08:11PM

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

ri...@google.com <ri...@google.com> #6Oct 31, 2023 09:11AM

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

pu...@gmail.com <pu...@gmail.com> #7Oct 31, 2023 09:50AM

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

ri...@google.com <ri...@google.com> #8Oct 31, 2023 11:25AM

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.

ri...@google.com <ri...@google.com> #9Oct 31, 2023 12:23PM

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.

ri...@google.com <ri...@google.com> #10Oct 31, 2023 12:27PM

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

pu...@gmail.com <pu...@gmail.com> #11Oct 31, 2023 12:38PM

Confirming that using res/raw/shrinker.xml works fine, retaining most of the benefits of the precise shrinker (only +20kb added to the APK with keep rule vs the crashing precise APK without it).

So it might be a good idea to integrate that keep rule by default for now.

Message last modified on Oct 31, 2023 12:38PM

ri...@google.com <ri...@google.com> #12Nov 1, 2023 12:41PM

Marked as fixed.

Landed a fix in AGP to default to keeping ids for now, this should hit canary in the next few weeks and you can then delete your shrinker.xml file again

Thanks for the provided apks and info!

an...@google.com <an...@google.com> #13Nov 2, 2023 09:04PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Iguana | 2023.2.1 Canary 12
Android Gradle Plugin 8.3.0-alpha12

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

pu...@gmail.com <pu...@gmail.com> #14Nov 3, 2023 11:11AM

Thanks for the fix, confirming that shrinker.xml is not needed anymore.

pu...@gmail.com <pu...@gmail.com> #15Jan 28, 2024 01:36PM

With AS 2023.3.1 Canary 7 / AGP 8.4.0-alpha07, this problem is back again and I had to explicitly add the shrinker.xml file with content above for app to not crash on startup.

ri...@google.com <ri...@google.com> #16Jan 29, 2024 07:07AM

Can you share the generated apk for that with me? That seems very strange

pu...@gmail.com <pu...@gmail.com> #17Jan 30, 2024 11:05AM

APK sent.

ri...@google.com <ri...@google.com> #18Jan 30, 2024 11:29AM

I landed a fix in AGP yesterday and a fix with tests in R8 here: https://r8.googlesource.com/r8/+/26aaf90cc10cc79b86fb568f959470853c4042be

Thanks for the apk

an...@google.com <an...@google.com> #19Feb 5, 2024 10:32PM

The fixes for this issue are now also available in:

Android Studio Jellyfish | 2023.3.1 Canary 8
Android Gradle Plugin 8.4.0-alpha08