Is it possible to set an expiration time (anchor property expireTime) later than the maximum expiration time (anchor property maximumExpireTime) indicated when fetching the anchor info using the Cloud Anchors Management API?
This may at first sound like a stupid question, but please continue reading.
I have Persistent Cloud Anchors setup and working in an Android app, ie. I can create anchors with a Time To Live (TTL) over one day. The documentation of Cloud Anchors says that you can set a TTL of 1-365 days, and that the expiration time can be changed afterwards using the Cloud Anchors Management API.
The thing is, the Cloud Anchors Management API happily receives an updated expireTime later than maximumExpireTime without complaining and when fetching the anchor info again, it clearly indicates that the anchor has an expireTime later than maximumExpireTime.
Note: maximumExpireTime seems to be fixed 365 days after createTime
Anyone with experience of persistent cloud anchors and their TTL or with insight of the inner workings of the service? I think that a maximumExpireTime of 365 days after createTime is a bit short to qualify as persistent. It should be more like 365 days after lastLocalizeTime, which effectively would expire any anchor that hasn't been used for up until a year.