We removed firebase analytics and we appealed, app is in waiting for review state for a very long time. How to release time sensitive releases?

Could this be the issue? https://github.com/firebase/firebase-ios-sdk/issues/15639 could the __SwiftValue reference comes from Firebase Analytics' internal StoreKit 2 integration?

We're not using flutter in this app.

yes we use objective c, and we call a swift sdk which supports objc callbacks, is this because the SDK is passing back swift data types to objective c , also is this something new which has changed, because same implementation was approved before, asking this just for information.

Feedback number FB19883396

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.

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

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.

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.

can setUPIVerificationCodeSendCompletion be made available for non upi apps?

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.

Same above has been raised via Feedback assistance, Recent Similar Reports used to be more than 10, now its None, nobody responds on Feedback assistance, nor are they informing if we need to raise a TSI, what is going on?

got resolved, my mistake, previous version was 1.20 so next version must be 1.21

Asset validation failed Invalid Version. The build with the version “1.9” can’t be imported because a later version has been closed for new build submissions. Choose a different version number. (ID: 0cb9ef1a-e4af-48ed-9279-f31686169f20) Asset validation failed Invalid Pre-Release Train. The train version '1.3' is closed for new build submissions (ID: 67f71f7f-e21c-4495-8a3a-38f7ccf0222f) Asset validation failed This bundle is invalid. The value for key CFBundleShortVersionString [1.3.0] in the Info.plist file must contain a higher version than that of the previously approved version [1.20]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring (ID: 8cb5cafe-f932-4dc5-a9a7-eca59fbe4137) Getting this error now!!!!! the app itself was invisibile, dont know what is 1.9? it is not mentioned anywhere, we have given it as 1.3

hi, did you by any chance get any information on this?