This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
I am running the Azure Spatial Anchors Basic Demo on Unity (2020.3.23f1) and iOS (latest iOS) with ASA 2.11.0 and for some reason I cannot place the Anchors when running it on my iPhone (iPhone 12 Pro).
When reaching the phase "Tap a surface to add the local Anchor" nothing happens when I tap the screen, nor do I see any log printed in my Xcode.
The last log I see in Xcode is the following:
"State from DemoStepBusy to DemoStepStartSession
Microsoft.Azure.SpatialAnchors.Unity.Examples.AzureSpatialAnchorsBasicDemoScript:set_currentAppState(AppState)
Microsoft.Azure.SpatialAnchors.Unity.Examples.<AdvanceDemoAsync>d__14:MoveNext()
System.Runtime.CompilerServices.AsyncTaskMethodBuilder:Start(TStateMachine&)
Microsoft.Azure.SpatialAnchors.Unity.Examples.AzureSpatialAnchorsBasicDemoScript:AdvanceDemoAsync()
Microsoft.Azure.SpatialAnchors.Unity.Examples.<AdvanceDemo>d__16:MoveNext()
System.Runtime.CompilerServices.AsyncVoidMethodBuilder:Start(TStateMachine&)
Microsoft.Azure.SpatialAnchors.Unity.Examples.DemoScriptBase:AdvanceDemo()
UnityEngine.Events.UnityAction:Invoke()
UnityEngine.Events.UnityEvent:Invoke()
UnityEngine.EventSystems.EventFunction1:Invoke(T1, BaseEventData) UnityEngine.EventSystems.ExecuteEvents:Execute(GameObject, BaseEventData, EventFunction1)
UnityEngine.InputSystem.UI.InputSystemUIInputModule:ProcessPointerButton(ButtonState&, PointerEventData)
UnityEngine.InputSystem.UI.InputSystemUIInputModule:ProcessPointer(PointerModel&)
UnityEngine.InputSystem.UI.InputSystemUIInputModule:Process()"
I wonder if it is somehow related to the fact I had to replace the Input Module / System with the new one ("Replace with InputSystemUIInputModule")
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Shachar Grembek
Are you referring to this step in the tutorial? While making source code changes?
The export works fine. That is the message regarding the input module 
Thanks for the response, we are checking with the team internally.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 97%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOA%3C/text%3E%3C/svg%3E)
@Shachar Grembek that sounds like it is possibly the issue. Are you able to run it with the StandaloneInputModule?
Hello @Shachar Grembek ,
As suggested by @Oladapo Afolabi "Are you able to run it with the StandaloneInputModule?"
Thanks!