Search Issue Tracker

Fixed

Fixed in 5.1.4, 6.0.0-pre.8

Votes

21

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

Package: ARCore

-

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: (only reproduces on Android 14+ devices)
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

  1. Resolution Note (fix version 6.0.0-pre.8):

    Updated ARCore SDK to 1.42

  2. Resolution Note (fix version 5.1.4):

    Updated ARCore SDK to 1.42

Log in to vote on this issue

Comments (6)

  1. modernator24

    Aug 22, 2024 04:55

    @TsvetelinaStoyanova

    that's not working for me

    Could not determine the dependencies of task ':launcher:collectReleaseDependencies'.
    > Could not resolve all task dependencies for configuration ':launcher:releaseRuntimeClasspath'.
    > Could not resolve com.google.android.play:core:1.42.0.
    Required by:
    project :launcher > project :unityLibrary
    > Could not resolve com.google.android.play:core:1.42.0.
    > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

  2. weareroyale

    Jul 21, 2024 00:58

    In our case we found that this issue actually came down to a bug in Play Asset Delivery. We resolved it by updating the Google Play Core libraries, by adding this to Assets/Plugins/Android/mainTemplate.gradle:

    dependencies {
    implementation 'com.google.android.play:core:1.10.3'
    }

  3. weareroyale

    Jul 19, 2024 19:09

    We are also experiencing this bug with an AR app built in Unity 2019.4. We can build directly to a local device and it runs. When we build an .aab and publish it through the Play Store, then downloaded it to an Android 14 device it crashes immediately on start apparently with this error:

    2024/07/19 11:43:12.341 16972 16972 Fatal DEBUG Abort message: 'No pending exception expected: java.lang.SecurityException: com.our.app: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts

  4. ParkW

    Jul 17, 2024 09:28

    I was trying to update the AR app version on the Play Store and found this.
    I wonder if it will be fixed before 8/31...

  5. tomcarnevale

    Jul 16, 2024 16:29

    Still seeing this issue. The deadline for new apps on the play store to target Android 34 is August 31st...

  6. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues