*** Aborted at 1632322639 (unix time) try "date -d @1632322639" if you are using GNU date *** about azure_spatial_anchors_ros

[roalchaq]

Some more details that will hopefully help diagnose the problem:

• Tested in yet another computer with ROS Noetic and Ubuntu 20.04.
• Made a test without adding the anchor id in the launch file and everything starts just fine. However, when I call the ROS service "/asa_ros/find_anchor" I get the same error as before.

[roalchaq]

So, the issue was not asa_ros. I "fixed" the problem by creating a new resource in Azure and changing the credentials in the ROS side. It would be interesting to know why this happened though. Closing the issue now.

[chriswsuarez]

Hi, any chance you can clarify what the fix was for this? I'm running a setup where I can detect anchors for some period of time and then seemingly at random this issue with occur and asa_ros will crash. I'm doing a unique setup where I detect anchors continuously while the robot is running including resetting sessions and detecting the same anchors again.

[roalchaq]

Hi @chriswsuarez . Sure!. I just created a new anchor(s) and updated the anchor_id field in the launch file. This also happens at random in my case. For some reason, these ids are deleted from time to time from your account.

[chriswsuarez]

Ah gotcha. Thanks!