Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.1.0f2
Issue ID
1037999
Regression
No
Camera permission does not appear with ARCore when application starts on a device
To reproduce:
1. Open attached project
2. Make sure that Scripting Runtime Version:.Net 4.x Equivalent and API Compatibility Level:.Net 4.x
3. Build and run on Android device
4. Notice that app doesn't ask for camera permission and camera doesn't start
Actual result: the app doesn't ask for camera permission and the camera doesn't start.
Expected result: When app opens it asks for camera permission
Reproduced in: 2017.2.3f1; 2017.3.2f1; 2017.4.3f1; 2018.1.1f1; 2018.2.0b4; 2018.3.0a1
Reproduced with:
Google Pixel, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/sailfish/sailfish:8.1.0/OPM4.171019.016.B1/4720843:user/release-keys
Samsung SM G965U1, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 630, Build:samsung/star2qlteue/star2qlteue:8.0.0/R16NW/G965U1UEU1ARBG:user/release-keys
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment