I'm still having this issue on iOS 16.3.1. This is a real pain. Users know in the meantime they have to kill the app and start again, but this can't be the final solution! Apple? Do I really
PeteDeGreet
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution