We are using uikit and on pro max devices we are facing this issue, pushing a viewcontroller from a rootviewcontroller, pretty much freezes in between transitioning of viewcontrollers. 18.4.1, such type of bugs which are not acknowledged are become exceedingly difficulty to convince customers, as apple insulates itself and we are stuck bearing the brunt.

can setUPIVerificationCodeSendCompletion be made available for non upi apps?

Its a private API which is given behind an entitlement, we dont have a lot of documentation or discussion about this API in the public forums, nor does the documentation state in which case it may or may not fail, the only thing we have are back end logs where we see the API being triggered on success of this setUPIVerificationCodeSendCompletion function, which was not supposed to be triggered for that person. We dont know how to simulate it. Which is why i am asking here. Do you want me to raise a bug report? I cant simulate it, but the logs say otherwise. And answering if in the chain has raised it with apple, its above my pay grade, i am not aware of this, i assuming it has been. If you're not in a position to answer this, i understand.

As per our logs the user has not successfully sent the SMS from his device, which is an iphone, the payload has come from another device, which is not an iphone, just like how this MFMessageComposeViewController was working before setUPIVerificationCodeSendCompletion, irrespective of wether an sms was sent or not, callback was given as sent on dismissal of MFMessageComposeViewController(on send button tap), so i can copy the SMS payload and ask someone else to send it to the number, thats the behaviour we are seeing in our back end logs. Fine its a "public" api. Can we discuss about how i can raise a bug simulating this? raising a bug would require me to provide video evidence of this? If i could i would.

no we are not able to reproduce it, which is why i am seeking your expertise on this.

the ones who are doing this are not the legitimate owners of the account, so its not possible at the moment to reproduce it, just wanted to know what possible new features introduced on ios 18.x especially w.r.t messaging, could trigger this bypassing of the API, so we can try to reproduce it, or atleast try to keep some additional checks in place to flag such activity.

Feedback number FB19883396