Search Issue Tracker
Active
Under Consideration for 5.1.X, 6.0.X
Votes
12
Found in [Package]
5.1.2
6.0.0-pre.7
Issue ID
ARCB-29
Regression
No
[XR][Android] Crash on Android 14 due to ARCore package not specifying one of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED
Reproduction steps:
1. Open the attached project “ARProject”
2. Ensure that Target API Level is set to API Level 34 at (menu: Edit > Project Settings > Player > Other Settings > Identification > Target API Level)
3. Ensure that “Google Play Services for AR” app isn’t installed on the device
4. Build And Run on Android
5. Observe the app behaviour
Expected result: The app runs successfully
Actual result: The app crashes with the error “Error AndroidRuntime java.lang.RuntimeException: Unable to resume activity
{com.DefaultCompany.Android14ARInstallCrashTest/com.google.ar.core.InstallActivity}
: java.lang.SecurityException: com.DefaultCompany.Android14ARInstallCrashTest: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts”
Reproducible with: 5.0.5, 51.0, 5.1.2 (2021.3.36f1, 2022.3.22f1)
Not reproducible with: 6.0.0-pre.3, 6.0.0-pre.6 (2023.2.15f1, 6000.0.0b12)
Couldn’t test with: 6.0.0-pre.3, 6.0.0-pre.6 (2021.3.36f1, 2022.3.22f1) (packages not supported causes errors)
Reproducible with this device:
VLNQA00591 - Samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
Pixel 6, Octa-core, 2800 MHz, Cortex X1, 64-bit, Mali-G78 MP20 (user's)
Not reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
Testing environment: Windows 11 23H2 (22631.3007), macOS 13.6 22G120 Darwin 22.6.0 (user’s)
Note: Reproducible with AR Foundation Samples
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
TsvetelinaStoyanova
Apr 26, 2024 14:43
Hi, I experienced the same issue (+1 votes). As a temporary workaround, I included the arcore dependency in a custom build.gradle, as shown in the google documentation:
dependencies {
…
implementation 'com.google.ar:core:1.42.0'
}
This solution might require further steps to ignore the arcore library in the build process from the Android side.