Noted, thanks. Will do that later.
edysudarto
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
Post
Replies
Boosts
Views
Activity
If i understand it correctly, you mean if it still occurs in iOS 16, I should submit a new bug report and mentioned about the existing one there (which is FB9839142) and also let you know again both of the bug report numbers here, right ?
hi, is there any updates that can be shared from the Apple side regarding this ?
like maybe it will be fixed in the upcoming iOS 16 ?
I see, so it's confirmed that there's nothing we can do to resolve this issue in my side for now beside waiting for the fix to be published on the next iOS update by Apple (even though we are not sure when and on which version).
Thanks for clarifying that for me, Quinn. Really appreciate your help !
Please do send my thanks to your colleague for pointing out one of crucial part in this investigation.
XD
Have a nice day, both of you !
Unfortunately no.
Sorry, i misclicked the button mark as accepted answer there.