I think it will stay as a known issue in the current RTM release, until we switch phones OTA with vivid in the next few months. The issue is annoying, but users can easily get back to a known working state, by restarting a signup session.
I think it will stay as a known issue in the current RTM release, until we switch phones OTA with vivid in the next few months.
The issue is annoying, but users can easily get back to a known working state, by restarting a signup session.