Hi folks - Jumping in here to provide an update and to give you confidence that our team is aware of and working to resolve the issue. Apologies for any frustration this has caused.
The issue is complex and our product & engineering teams are still working to diagnose the issue such that we can provide a fix as quickly as possible. That effort includes working with our partners (carriers and hardware suppliers) as well as digging into recent Device OS releases.
I imagine many of you are working directly with support engineers, please continue to do so. We will also be updating this thread as we make progress on diagnosing and plans to address it.
Thanks for your patience and we will keep you posted.
Dan