Issue with iOS ipa File Submission

[ctokunaga-reichert-vitalant]

Wondering if anyone has had any issues with submitting an Uno app on the iOS side of things. Originally had a Xamarin app, and decided to convert it to Uno. After development, when attempting to submit the ipa file to App Store Connect, the delivery has failed with the error "ITMS-90018: This bundle is invalid - The file extension must be .zip." The strange thing is, the ipa file passes verification from Apple without issue. I have tried the Transporter app, using Xcode command line, and the Azure DevOps Pipeline Task to deliver the ipa file and all have resulted in the same issue. Verification passes, and then upon delivery, I receive an email with the error code and no additional information. I've also tried changing the file extension of the ipa file to zip to take a look at the contents, and everything seems to look fine. I have the one payload folder, and the one .app folder. Everything within the .app folder looks fine as far as I can tell. I have seen somewhere that if there are additional files within the .app folder that contain the word "app" that it can cause submission issues with Apple, but none of my filenames contain "app". I have even tried updating the .NET version and Uno SDK version I was using. When I originally started the conversion from Xamarin to Uno, I was targeting .NET 8 and Uno 5.4.10. During development, I routinely updated the Uno SDK as updates became available, and am now targeting .NET 9 and Uno 6.0.96, but I'm still seeing the same issue. Android, on the other hand, has not been an issue. I was able to submit to the Google Play Store just fine. I have also been able to distribute ipa files for Dev and QA versions of the iOS app directly to my physical devices, and they run without any problems. Just wanted to see if anyone else has had issues specifically with submitting Uno Apps to Apple and if anyone might have some suggestions as to what might be going on.

[jeromelaban]

Thanks for the report.

Can you validate if you CFBundlename size is not over 16 characters?

You can view the contents of the info.plist with the following:

unzip -p MyApp.ipa "Payload/*.app/Info.plist" | plutil -p -

If it is, you may need to change your AssemblyName property in your app so the name gets smaller.

[ctokunaga-reichert-vitalant]

I will give that a shot and see what happens.

[ctokunaga-reichert-vitalant]

Publishing an empty Uno app with the same BundleID to TestFlight worked without issue. I'm going to try adding in dependencies and packages that my app uses to see if I eventually get the same error.

[jeromelaban]

Thanks for the update! This is good news indeed.

You may also be able to compare the structure of the IPAs more directly. Is there anything significant that shows up when comparing the info.plist files? (using #20744 (comment))

[ctokunaga-reichert-vitalant]

It seems this was caused by a third party dependency. I've reached out to get the package fixed, and hopefully that will take care of this issue going forward. Does not seem to be an issue on the Uno side. Thanks for the help digging into this!

[jeromelaban]

Thanks for the update, for future reference, this is the change in question: radarlabs/radar-sdk-xamarin#24.