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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.