Azure-docs: Clarification needed on saving anchors to the cloud

[maulik1shah]

I have followed this entire document for creating local and shared anchors, and as I understood, the createAnchorAsync method of CloudSpatialAnchorSession class is responsible for saving the anchors to the Azure cloud.

In the sample Android application, when I tried to save anchors in either 'Basic' or 'Nearby' mode (Button names), my anchors were not being stored on the cloud, while in case of 'Shared' they all got stored on the cloud as well as on the .Net sharing service database.

While searching for the reason for above mentioned incident, the only difference I found between the codes of AzureSpatialAnchorsActivity and SharedActivity classes is that in the AzureSpatialAnchorsActivity class, each anchors is assigned an expiry date, while in the SharedActivity class, it's not. Is that the reason why the anchors are not being stored on Azure cloud in the former case? Please clarify.

[Enter feedback here]

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e263a867-f6c6-0ac2-baad-57059396e839
• Version Independent ID: 1fa20d5b-660c-026c-7edc-4e6322d19812
• Content: Quickstart - Create Android app with Azure Spatial Anchors
• Content Source: articles/spatial-anchors/quickstarts/get-started-android.md
• Service: azure-spatial-anchors
• GitHub Login: @craigktreasure
• Microsoft Alias: crtreasu

[maulik1shah]

I believe I had delays in the azure cloud appearance, otherwise I don't see that problem. Sorry for inconvenience.

[YutongTie-MSFT]

@maulik1shah So it's all good now ^^? Are we safe to close?

[maulik1shah]

Yes, please.