“ITMS-90158”

We have developed the iOS App using .NET MAUI, when we try to upload it to store, the binary is getting rejected with the following error, kindly suggest a solution for this. TMS-90338: Non-public API usage - The app references non-public symbols in : _ubrk_openRules, _ucal_add, _ucal_close, _ucal_get, _ucal_getAttribute, _ucal_getKeywordValuesForLocale, _ucal_getNow, _ucal_getTimeZoneDisplayName, _ucal_getTimeZoneIDForWindowsID, _ucal_getWindowsTimeZoneID, _ucal_open, _ucal_openTimeZoneIDEnumeration, _ucal_set, _ucal_setMillis, _ucol_close, _ucol_closeElements, _ucol_getOffset, _ucol_getRules, _ucol_getSortKey, _ucol_getStrength, _ucol_getVersion, _ucol_next, _ucol_open, _ucol_openElements, _ucol_openRules, _ucol_previous, _ucol_safeClone, _ucol_setAttribute, _ucol_setVariableTop, _ucol_strcoll, _ucurr_forLocale, _ucurr_getName, _udat_close, _udat_countSymbols, _udat_format, _udat_getSymbols, _udat_open, _udat_setCalendar, _udat_toPattern, _udata_setCommonData, _udatpg_close, _udatpg_getBestPattern, _udatpg_

I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!

Have been trying to upload an archive of our app and watch app to iTunes Connect which includes support for iOS9 and watch OS 2 with healthkit.I keep running into this error:ERROR ITMS-90362 :Invalid Info.plist value. The value for the key 'UIRequiredDeviceCapabilities' in bundle {bundle name} is invalid. Expecting array with a single string value of watch-companion'In order to get our app working since it relies on healthkit, we have included healthkit in our UIRequriedDeviceCapabilities and without it the app will never load.<key>UIRequiredDeviceCapabilities</key> <array> <string>healthkit</string> </array>Using this causes the app to not be able to submit. If i change the string to 'watch-companion' as it seems to suggest, then the watch app will never start.Here is an image of the error when uploading through Organizer:https://cloud.githubusercontent.com/assets/1257664/9561131/c6a5b56e-4e30-11e5-9817-3b3d8614e1c5.pngHas anyone been able to submit a watch OS2 ap

I built and submitted a react-native app using expo eas build -p ios --auto-submit and the app was sent to Apple for submission. I received an email back 5 minutes later that reads: Dear Developer, We identified one or more issues with a recent delivery for your app, react-chipsapp 0.1.2 (0.1.2). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?

My app (com.onon.app) consistently fails App Store Connect validation (ITMS-90207: Invalid Bundle) despite passing all local diagnostics (valid arm64 binary, correctly signed, appropriate entitlements). Is there a known issue with Apple's validation server, or are there obscure validation rules I might be missing? Diagnosic info Architecture Check (lipo -info Runner): Non-fat file: Runner is architecture: arm64 Code Signing Verification (codesign -vvv Runner): Runner: valid on disk Runner: satisfies its Designated Requirement Local Environment Details: Operating System: macOS 15.5 24F74 (arm64) Xcode Version: 16.3 (16E140) Transporter Version: 1.3.3-13326 Flutter Version: 3.29.0 CocoaPods Version: 1.16.2 Has anyone encountered a similar issue with a Flutter app that passes local code signing checks but is rejected by App Store Connect? Are there any known edge cases or obscure validation rules that aren't covered by standard code signing diagnostics? I've also opened a Technical Support Incident with