Search Issue Tracker
Won't Fix
Won't Fix in 4.2.X
Votes
0
Found in [Package]
4.2.7
Issue ID
ARKB-38
Regression
No
[iOS] ARFoundation ARKit does not full detect plane on iPhone 12 Pro
How to reproduce:
1. Create a new project with the AR Core template
2. Go to Edit > Project Settings > XR Plug-In management > iOS
3. Enable ARKit
4. Build and deploy the project to iOS
5. Scan your surroundings
Expected outcome: The edges of the room are detected
Actual outcome: The edges of the room do not get detected
Reproducible with: 2020.3.45f1, 2021.3.17f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Reproduced on: iPhone 12 Pro (iOS 14.2.1)
Could not reproduce on: iPhone 13 Pro (iOS 15.6.1), 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:
This reflects the underlying plane data we get from ARKit, and can be seen when using the ARKit sample from Apple (https://developer.apple.com/documentation/arkit/content_anchors/tracking_and_visualizing_planes)
Resolution Note (4.2.X):
This reflects the underlying plane data we get from ARKit, and can be seen when using the ARKit sample from Apple (https://developer.apple.com/documentation/arkit/content_anchors/tracking_and_visualizing_planes)