Fixed
Status Update
Comments
jh...@gmail.com <jh...@gmail.com>
jh...@gmail.com <jh...@gmail.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ch...@google.com <ch...@google.com>
na...@vitruvian.me <na...@vitruvian.me> #3
Almost 2 months later and this is still broken
ri...@google.com <ri...@google.com> #4
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
ri...@google.com <ri...@google.com> #5
jb...@google.com What is the update on this?
jh...@gmail.com <jh...@gmail.com> #6
What is the status of this item?
jh...@gmail.com <jh...@gmail.com> #7
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
ri...@google.com <ri...@google.com> #8
Any ETA on next release?
ri...@google.com <ri...@google.com> #9
Still broken and not updated? --package_file argument is not usable in it's current form on 26.1.1 straight from the developer site.
ri...@google.com <ri...@google.com> #10
Comfirmed that this seems to still be broken. Can we have an update please?
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
ga...@google.com <ga...@google.com>
ga...@google.com <ga...@google.com> #11
Hi, is there any update to this issue? Thanks.
cm...@google.com <cm...@google.com>
cm...@google.com <cm...@google.com> #12
Hi Google. You claim it's been fixed on master, but we haven't had a new release since the broken version 26.1.1. Can you please release the fix?
Description
When certain build features are used together, the resource shrinker mangles resource IDs. Resource ID integers in the resulting binary are wrong, which at runtime leads either to
The behavior is not totally deterministic - some builds are fine, but sometimes, renaming the XML resource is enough (!) to get the crash. Sometimes, a clean build, AS restart, or invalidate caches & restart command fixes things, but only temporarily, until the next rename.
To reproduce, please run the attached project, distilled from a real-world project:
R.string.sample_string_resource
resource to anything else, and try again.android.content.res.Resources$NotFoundException: String resource ID #0x7f0d0027
(full stack trace below).The issue can be mitigated by not using certain build features. Each one of the following fixes the problem independently:
isShrinkResources = false
.resourceConfigurations += "en"
.settings.gradle.kts
andbuild.gradle.kts
).Notes:
Thanks, and let me know if I can help further. 🙏
Full stack trace:
System info: