Search Issue Tracker
Fixed in 2019.1.X
Votes
1
Found in
2018.3.0a8
2018.3.0a9
Issue ID
1071819
Regression
Yes
[XR] Failed to initialize Vuforia SDK on android device
Failed to initialize Vuforia SDK on android device.
Steps to repro:
1. Create a new project.
2. File > Player Settings > XR Settings > Enable "Vuforia Augmented Reality Supported".
3. Create AR Camera from GameObject menu.
4. Create build for Android device.
Actual Result:
Failed to initialize Vuforia on the device.
Expected Result:
Vuforia SDK should initialize gracefully on the device.
Reproducible on:
2018.3.0a10, 2018.3.0a9
Working fine on:
2018.3.0a8, 2018.3.0a1, 2018.2.4f1.
Note:
1) Camera permission has to be given manually for this app from app settings menu. The application works fine after that.
2) In earlier versions the Camera used to open without giving any permission manually.
Environment:
Windows and MAC.
NOTE: Occurring only on Android devices.
Reproduced on devices:
1. Samsung Galaxy S8
OS: Android 8.0 (Oreo)
GPU: Mali-G71 MP20
CPU: Octa-core (4x2.3 GHz Mongoose M2 & 4x1.7 GHz Cortex-A53)
2. Samsung Galaxy S8+
OS: Android 8.0 (Oreo)
GPU: Mali-G71 MP20
CPU: Octa-core (4x2.3 GHz Mongoose M2 & 4x1.7 GHz Cortex-A53)
3. Google Pixel 2
OS: Android 8.0
GPU: Adreno 540
CPU: Octa-core (4x2.35 GHz Kryo & 4x1.9 GHz Kryo)
Comments (2)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
deanryanEC2018
Mar 07, 2019 10:16
Any work around for this to work in Unity 2018.3.0f2 , this is being used for a major release so can not upgrade to Unity 2019.1 yet