Stay organized with collectionsSave and categorize content based on your preferences.
As of the August 2022 1.33.0 release, theARCore Cloud Anchor APIendpoint is deprecated. All apps built with ARCore SDK 1.33.0 and higher now target the
newARCore API,
general-purpose API intended for use with all ARCore cloud services. All apps
built with ARCore SDK 1.32.0 and lower will continue to target the older API.
This change will not affect existing data. Once an app is updated to use ARCore
SDK 1.33.0 or later, and the newARCore APIhas been enabled in the Google
Cloud project used by your app, functionality should remain the same as it did
when using the previous end point. To support older app versions, you may enable
both APIs while making the transition.
If your app uses the Cloud Anchors API, you must update it to use ARCore SDK
1.33.0 or laterbefore August 31, 2023. After this date, apps compiled with
ARCore SDK 1.32.0 or earlier will no longer be able to host and resolve Cloud
Anchors.
Update your app to use the latest ARCore SDK. ARCore SDK 1.33 and later use
the new ARCore API.
Test these changes by using Cloud Anchor API functionality in your app.
Verify that the Cloud Anchor API usage for the updated app appears under theARCore APIin the Google Cloud project, andnotunder theARCore
Cloud Anchor API.
Update app settings
If your iOS app is using signed JWTs for authorization, change theaudienceclaim tohttps://arcore.googleapis.com/for apps built with
ARCore SDK 1.33.0 and higher.
If your API key isrestricted,
you must allow the ARCore API.
If you send requests to the ARCore Cloud Anchor Management API from your
backend, you must enable the ARCore API and change the domain name toarcore.googleapis.com.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["\u003cp\u003eThe ARCore Cloud Anchor API is being replaced by a new, general-purpose ARCore API starting with ARCore SDK 1.33.0.\u003c/p\u003e\n"],["\u003cp\u003eApps using ARCore SDK 1.32.0 or lower must be updated to ARCore SDK 1.33.0 or later by August 31, 2023, to continue using Cloud Anchors.\u003c/p\u003e\n"],["\u003cp\u003eExisting Cloud Anchor data will not be affected by this change.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers need to enable the new ARCore API in their Google Cloud project and update their apps to use the latest ARCore SDK.\u003c/p\u003e\n"],["\u003cp\u003eApp settings may need to be updated, including JWT audience claims, API key restrictions, and backend request configurations, to reflect the new API endpoint.\u003c/p\u003e\n"]]],[],null,["# ARCore 1.33 Cloud Anchor endpoint changes\n\nAs of the August 2022 1.33.0 release, the\n**[ARCore Cloud Anchor API](https://console.cloud.google.com/apis/library/arcorecloudanchor.googleapis.com)**\nendpoint is deprecated. All apps built with ARCore SDK 1.33.0 and higher now target the\nnew\n**[ARCore API](https://console.cloud.google.com/apis/library/arcore)**,\ngeneral-purpose API intended for use with all ARCore cloud services. All apps\nbuilt with ARCore SDK 1.32.0 and lower will continue to target the older API.\n\nThis change will not affect existing data. Once an app is updated to use ARCore\nSDK 1.33.0 or later, and the new **ARCore API** has been enabled in the Google\nCloud project used by your app, functionality should remain the same as it did\nwhen using the previous end point. To support older app versions, you may enable\nboth APIs while making the transition.\n\nIf your app uses the Cloud Anchors API, you must update it to use ARCore SDK\n1.33.0 or later **before August 31, 2023**. After this date, apps compiled with\nARCore SDK 1.32.0 or earlier will no longer be able to host and resolve Cloud\nAnchors.\n\nNaming changes\n--------------\n\n\u003cbr /\u003e\n\n| | Previous | New |\n| API name | ARCore Cloud Anchor API | ARCore API |\n| Domain name | `arcorecloudanchor.googleapis.com` | `arcore.googleapis.com` |\n|-------------|------------------------------------|-------------------------|\n\n\u003cbr /\u003e\n\nUpdate your app to use the new endpoint\n---------------------------------------\n\nTo update your app:\n\n1. Visit the [Google Cloud Platform console](https://console.cloud.google.com/).\n2. Determine which cloud project your app uses.\n3. Ensure that the **ARCore API** is enabled.\n4. Update your app to use the latest ARCore SDK. ARCore SDK 1.33 and later use the new ARCore API.\n5. Test these changes by using Cloud Anchor API functionality in your app.\n6. Verify that the Cloud Anchor API usage for the updated app appears under the **ARCore API** in the Google Cloud project, and *not* under the **ARCore\n Cloud Anchor API**.\n\nUpdate app settings\n-------------------\n\n- If your iOS app is using signed JWTs for authorization, change the `audience` claim to `https://arcore.googleapis.com/` for apps built with ARCore SDK 1.33.0 and higher.\n- If your API key is [restricted](https://cloud.google.com/api-keys/docs/add-restrictions-api-keys), you must allow the ARCore API.\n- If you send requests to the ARCore Cloud Anchor Management API from your backend, you must enable the ARCore API and change the domain name to `arcore.googleapis.com`."]]
