+1, same issue here. Reported in Feedback Assistant with ID 13691566
To not let users be impacted by this, you can call startMonitoring again 1 second after you receive the error; this worked consistently for our users, but obviously is a bit of a clunky workaround
Topic:
App & System Services
SubTopic:
General
Tags: