Azure-docs: could not intialize cloudSpatialAnchorSession

[SurferLab]

Hello, When executing the line cloudSpatialAnchorSession = new CloudSpatialAnchorSession(); unity generates the following error :
EntryPointNotFoundException: ssc_cloud_spatial_anchor_session_create
Microsoft.Azure.SpatialAnchors.CloudSpatialAnchorSession..ctor () (at <b36503265f8640b0b25527e88c19df3b>:0)
AzureSpatialAnchorsScript.InitializeSession () (at Assets/Scripts/AzureSpatialAnchorsScript.cs:49) --> the line
AzureSpatialAnchorsScript.Start () (at Assets/Scripts/AzureSpatialAnchorsScript.cs:95) --> the call of the method containing the line

---

Document details

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

• ID: e3aab4c6-3e00-857c-e9a1-0a4023897b2f
• Version Independent ID: b92bc135-0ced-3eea-00ae-1a941c6f4c65
• Content: Tutorial: Create a new HoloLens Unity app - Azure Spatial Anchors
• Content Source: articles/spatial-anchors/tutorials/tutorial-new-unity-hololens-app.md
• Service: azure-spatial-anchors
• GitHub Login: @julianparismorgan
• Microsoft Alias: pmorgan

[KrishnaG-MSFT]

@SurferLab Thanks for your comment. We will review and get back to you shortly with an update.

[asergaz]

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

[SurferLab]

Hi again, i found a workarround in this link (https://github.com/Azure/azure-spatial-anchors-samples/issues/23#issuecomment-487812797).
The problem persist but it seems that unity doesn't allow running the project directly from the editor : you should deploy your project on hololens to be able to see what you're coding. Still hard work :(
Thank you guy, hope that you'll found a bug fix soon.
Regards,

[jparismorgan]

Hi @SurferLab, yes, you're right there. You can't use ASA in the Editor, you have to deploy to a device to use it.

[asergaz]

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.