-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
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
Duplicate assets in asset modules no longer permitted. #181
Comments
Thank you for reporting this, will fix in the next release. Could you please share your usecase, why do you need the same file between different asset modules? |
We have a large database of image assets for use in a battery of cognitive tests. Assets packs are downloaded for specific instances of a given task. Some images are reused between different types of tasks and consequently exist in different asset packs. Alternative strategies exist, but would be quite an upheaval for our asset generation mechanism (which is shared with a parallel implementation on iOS, where overlapping asset tags are permitted). |
Fixed in 1.3.0. |
Describe the bug
As of v1.2.0, duplicate assets are no longer permitted.
I can see that this behaviour has been changed because resources in asset modules are uncompressed, whereas in features modules these are compressed. Can this check in bundletool only reject a collision where a clash occurs between an asset module and a feature module? It seems to me that if this resource only exists in asset modules, then there is no ambiguity between compressed or uncompressed. Please correct me if I've misunderstood. I've got an app out in the wild which was processed by the Play Store by an earlier version of bundletool that I now can't easily update.
Bundletool version(s) affected
Version: 1.2.0
Stacktrace
To Reproduce
Create two bundles with a duplicate asset. Run build-apks
Expected behavior
Duplicate asset names are permitted if file contents are identical and asset only exists in asset modules.
The text was updated successfully, but these errors were encountered: