Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.22.2
2.2.2
Issue ID
ADDR-3735
Regression
No
[Android] "Unable to find registered file for bundle" errors are thrown when building Addressables Bundle which includes Localization Tables using the Play Asset Delivery
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the Addressables Group Window (Window > Asset Management > Addressables > Groups)
3. Build the Addressables Bundle (Build > New Build > Play Asset Delivery)
4. Observe the Console Window
Expected result: No errors are thrown
Actual result: The “Unable to find registered file for bundle Library/com.unity.addressables/aa/Android/Android\localization-string-tables-” errors are thrown for each locale in the Addressables Bundle
Reproducible with: 1.22.2 (2023.2.21f1), 2.2.2 (6000.0.15f1)
Could not test with: 2021.3.42f1, 2022.3.42f1 (the required com.unity.addressables.android package is not available for these Editor versions)
Reproducible on: MacOS Sonoma 14.5 (Intel), Windows 11
Not reproducible on: No other environment tested
Workaround: Build the Addressable Bundle using the “Default Build Script”
Notes:
- The Addressables Content build succeeds
- The same errors are thrown when building aab type builds but are not visible when building apk
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Property field override bar does not update transparency correctly when switching between valid and invalid GameObjects
- Project window selection is not updated when search term is changed
- Error when adding valid MonoBehaviour script to Prefab in Project window
- Editor Launch Screen will close when Enter is pressed on it
- ObjectPool's pool is destroyed when entering Play Mode without reloading Domain
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.