Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.1.0-preview.4
Issue ID
1219775
Regression
No
[iOS] ARKit reorders the XR Reference Image Library when built on iOS
How to reproduce:
1. Open the user-supplied project
2. Build the "SampleScene" Scene for iOS and deploy it
3. Enter Play Mode in the Editor and compare the Game view with the Player's output
Expected result: the Player's output is the same as the Game view in the Editor (Reference Images are outputted in order)
Actual result: the Reference Image order is reversed in iOS
Reproducible with: ARKit 3.1.0-preview.4, 3.0.1 (2019.3.0f6, 2020.1.0a25)
Could not test with: ARKit 2.0.1, 2.1.1, 2.1.2, 3.0.0-preview.1, 3.0.0-preview.4 due to package errors
Reproduces on:
VLNQA00160 iPhone 6s iOS 13.3.1
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:
Unfortunately, the reference image library is internally stored in an unsorted set on the Xcode side so we can't guarantee the edit-time ordering will match the runtime ordering. Please use the GUID and string identifiers rather than depending on the index of the list in the editor.