Google Play still detects AR after removing AR Foundation and XR packages

Target Platforms XR
, ,
1

Hello everyone,

I’m having an issue publishing an update of an existing Android app to Google Play and I’m running out of ideas.

Background

The app was originally developed using Unity and, in older releases (published in 2024), it included Augmented Reality features implemented with AR Foundation.

I have now completely redesigned the app and removed all AR functionality. The new version uses GPS/location-based features instead, and there are no AR experiences available to users anymore.

However, Google Play keeps rejecting the update with the following policy violation:

"Families Policy Requirements: Special restrictions: Augmented Reality

Your app uses Augmented Reality (AR), and doesn’t include a safety warning as soon as the AR section starts. The warning should remind users of the following:

  • The importance of parental supervision
  • To be aware of your surroundings"

The problem is that the app no longer contains any AR section.

What I have already done

  • Removed or commented all scripts with code that used AR functionalities.

  • Removed all AR Foundation functionality from the project.

  • Removed AR/XR-related packages from Package Manager.

  • Verified that XR Plugin Management is disabled.

  • Deleted the Library and obj folders and rebuilt the project from scratch.

  • Updated the Google Play Store listing and removed all references to AR from:

    • app description
    • screenshots
    • promotional graphics

  • Checked the generated AndroidManifest.xml and found no ARCore-related permissions or features.

  • The manifest does not contain camera permissions or AR-specific declarations.

  • Rebuilt and uploaded a completely new Android App Bundle.

Additional findings

After building the Android App Bundle, I analyzed it using Android Studio.

While inspecting the generated files, I found references to ARCore inside files such as:

  • GoogleARCoreApi.smali
  • UnityPlayer.smali

These files contain references to ARCore-related classes and methods. However, I am not familiar enough with Smali code to determine whether these references are actually used by the application or if they are simply generic Unity runtime code included in every Android build.

Because of this, I cannot tell whether these findings could be the reason Google Play still classifies the app as using Augmented Reality.

Summary

smalifiles
smalifiles1005×822 121 KB

Google Play appeal / review request

At this point, I am also wondering whether it would make sense to submit an appeal or request a manual review from Google Play.

Given that:

  • all AR functionality has been removed from the app,
  • all references to AR have been removed from the store listing,
  • the Android manifest does not appear to contain AR-specific declarations,

I am starting to question whether this could be a false positive from the automated review process.

Has anyone experienced a similar situation where Google Play continued to classify an app as AR even after the functionality had been removed?

Would it be appropriate to submit an appeal or contact Google Play support requesting a manual review, and if so, what information would you recommend providing to help demonstrate that the app no longer contains any AR features?

Any advice on the best approach would be greatly appreciated.

Any suggestions or similar experiences would be greatly appreciated.

Thank you!

2
  1. Unity 2022.3 is not supported unless you are an Enterprise or Industry user.
  2. What are AR Foundation/ARCore versions?
  3. Android-XR tag is related to Unity OpenXR: Android XR | Unity OpenXR Android XR | 1.3.1 — that’s not your case. Use XR and AR-Foundation instead.
  4. @andyb-unity any ideas?
3

Thanks for your reply.

Unity 2022.3 is not supported unless you are an Enterprise or Industry user.

Could you clarify what you mean by “not supported” in this context?

The project is currently using Unity 2022.3.62f2, but I don’t see how the Unity version itself would be related to Google Play detecting AR functionality in the generated build.

What are AR Foundation/ARCore versions?

There are currently no AR Foundation or ARCore packages installed in the project.

Older versions of the app did use AR functionality and therefore included different versions of AR Foundation/ARCore over time, but I don’t have a record of those versions anymore. Would that still be relevant for a new release where all AR functionality has been removed?

Android-XR tag is related to Unity OpenXR

Thanks for pointing that out. I selected the wrong tag. Unfortunately I don’t see any option to edit the topic tags after posting. Is there a way to change them?

At the moment I’m mainly trying to understand two things:

  1. What exactly could still be causing Google Play to classify the app as an AR application.
  2. Whether there is a reliable way to verify that no AR-related dependencies remain in the Unity project or in the generated Android build.

Are there any additional project files, generated Gradle dependencies, Unity settings, or Android build artifacts that I should inspect to verify that ARCore is no longer being included in the final build?

4

You report a bug here or want help. It probably will not be considered for regular users by the Team. Unity releases have a period of support.

You need whether be an Indusrty/Enterpise user (the latest version is 2022.3.76f1) or check your issue in the supported Unity versions to exclude this scenario first (Unity 6.0 or 6.3), and then submit a bug report which can be approved or you will get an explanation on it.

You can edit Tags when editing the Title.

To get a guaranteed answer with a supported Unity version, please submit a bug report via Unity Bug Reporter. Also, attach the internal number that you will receive via Email after submitting. Only a post with such a number makes sense here on Discussions.