Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.10
Issue ID
ADDR-3339
Regression
Yes
“Invalid header data!!!” error is logged when Build Remote Catalog is used
How to reproduce:
1. Open the “InitializeAsync_Bug” project
2. Open the “SampleScene”
3. Enable Hosting Service on any port (Window > Asset Management > Addressables > Hosting)
4. Build Addressables Groups (Addressables > Groups > Build > New Build > Default Build Script)
5. Select “Use Existing Build “ (Addressables Groups > Play Mode Script)
6. Enter Play Mode, wait one second, and exit Play Mode
7. Enter Play Mode again, and observe the Console
Expected result: no errors are logged to the Console
Actual result: “Invalid header data!!!” error is logged to the Console
Reproduced with: 1.21.3-1.21.10 (2020.3.47f1)
Not reproduced with: 1.18.19 (2020.3.47f1), 1.21.2 (2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b12, 2023.2.0a11), 1.21.3 (2021.3.23f1, 2022.2.16f1, 2023.1.0b12, 2023.2.0a11), 1.21.10 (2021.3.23f1, 2022.2.16f1, 2023.1.0b12, 2023.2.0a11)
Reproduced on: Windows 10 (by reporter), Windows 11
Note: *The regressed version is actually 1.21.3*, but it is not listed in external data
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
Resolution Note:
Thank you for reporting a bug to Unity.
We have no plans for porting this fix to 2020.3 as it has reached End-of-Support. If you are still facing this issue, please consider upgrading to a more recent LTS.
Today we will be closing this case. Thank you again for taking the time to report this issue.