Search Issue Tracker
Fixed in 1.6.1
Votes
0
Found in [Package]
0.6.8
Issue ID
1188009
Regression
No
[Addressables] Hosting Service port changes when Assets are reimported
How to reproduce:
1. Open the attached project "1188009.zip"
2. Open the Hosting window (Window - Asset Management -> Hosting Services)
3. Notice the Port field value in the Hosting window
4. Reimport all Assets (Assets -> Reimport All)
5. Observe the Port value in the Hosting window
Expected result: Port value stays the same
Actual result: Port value changes
Reproducible with Unity versions: 2018.4.11f1, 2019.1.14f1, 2019.2.9f1, 2019.3.0b7, 2020.1.0a8
Reproducible with package versions: 0.6.8, 0.7.5, 0.8.6, 1.1.10, 1.2.4
Notes:
Could not test on earlier package versions due to Console errors.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.6.1):
This should be fixed in the coming 1.6.1 release. The port should no longer re-randomize on a domain reload.