The change can arrive via manifest merge when the app does not fix the target. See how to migrate AR experiences without discovering publishing incompatibilities.
Direct answer
ARCore 1.56 updates its targetSdkVersion to Android API level 37. The documentation warns that if the application does not explicitly declare a target, the value may be inherited by the manifest merge. For augmented reality projects, the migration must check permissions, camera, storage, background execution, native libraries, engine plugins, and store requirements before adopting the new version into production.
Implicit Manifest Creates Avoidable Surprise
Declare the SDK target consciously in the project. Relying on the value of a library makes the change less visible in updates.
Permissions need functional testing
Camera, sensors, media and notifications can change behavior between levels. Test grant, deny, revoke and return to the application.
Plugins can be the weakest link
Analytics, authentication, rendering, or engine SDKs can load their own manifests and native code. Map versions and validate the suite, not just ARCore.
Publication deserves an approval strip
Use internal builds and gradual rollout, track crashes, ANRs, AR session failures, and abandonment before expanding rollout.
Nexus Reading
Treat the new target as a platform change: dependency inventory, permission tests, device matrix, and defined rollback.
FAQ
Does the app change to API 37 even without configuration?
The documentation states that this can happen by merging the manifest when the application does not specify targetSdkVersion.
Does updating the target change the minimum system?
Target SDK and min SDK are different concepts, although dependencies can change additional requirements.
What to validate first?
Build, install, camera, permissions, AR session creation and critical flows on supported devices.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on October 8, 2026. The text is original and interprets practical implications for companies.
- Google for Developers — What's new in ARCore: Official targetSdkVersion change and new features from version 1.56.
- Android Developers — Meet Google Play target API level requirements: Official requirements and effects of target API levels.
Date reported by main source: official documentation consulted on October 8, 2026.