Few of my iOS app’s universal binary exceeds 200MB, while individual device-specific binaries remain under 200MB. I understand Apple recommends keeping app binaries below 200MB to allow downloads over mobile networks. I want to confirm whether the size of the universal binary impacts the ability of users to download or update the app (App Store build) over cellular networks, or if only the device-specific slice size is considered?

My app / subscription gets rejected with the following: Guideline 2.1 - Performance - App Completeness We have returned your in-app purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the in-app purchase products with the binary. and Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first subscription has been submitted for review, additional subscriptions can be submitted from the Subscriptions section. Learn More ...ive tried all kinds. I archive a new build, upload it, update the app information top show new build so it ties in...and still nothing works. it is incredible frustrating. Can anyone help please. Ive wasted days on this

My iOS app (logbook) is failing App Store Connect validation with: "The app contains one or more corrupted binaries. Rebuild the app and resubmit. (ID: 96ef48c6-afb4-4e23-9205-8f625577feab)" From the distribution logs, I found the issue: 2025-07-16 07:11:35 +0000 Item /Users/guillaumehuchet/Library/Developer/Xcode/Archives/2025-07-16/Skyden 16-7-25, 09.01.xcarchive/Products/Applications/Skyden.app doesn't have the entitlement com.apple.developer.web-browser-engine.host enabled, returning ["arm64e"] 2025-07-16 07:11:35 +0000 Archs to thin for item /Users/guillaumehuchet/Library/Developer/Xcode/Archives/2025-07-16/Skyden 16-7-25, 09.01.xcarchive/Products/Applications/Skyden.app are ["arm64e"] The validation system is checking for web browser engine entitlements (which my app doesn't need), and when not found, it incorrectly requires arm64e architecture - which is private and unavailable to third-party developers. Details: Xcode: 16.4.0 Uses WKWebView solely to render HTML templates into PDF documents for logbook exports No web browsing functionality - WebView is only used as a rendering engine for PDF generation This appears to be a validation bug. The app builds and runs fine locally. How can I get past this incorrect architecture requirement? I tried everything in the last 2 days to debug it, saying I'm desperate would be a small word... this is blocking our app launch...

Hi, Recently our App is facing a generic error with no error details. This error is happening once Build has been successfully uploaded to AppStore Connect through Xcode Organiser. Steps followed while uploading the build: Archive the Build through Xcode Once Archive is successful, Distributing the App through Xcode Organiser using AppStore Connect distribution method. Build Uploaded successfully to AppStore Connect After 5 min we are receiving a email with below message Hello, We noticed one or more issues with a recent delivery for the following app: AppName App Apple ID 2121111 Version 3.6.9 Build 75 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/AppName. Remove the instructions from the binaries, rebuild and resubmit. Apple Developer Relations Solutions tried till now Updating Xcode to latest version of 16.4 Recreating new Distribution certificates and Provisioning Profiles Clearing DerivedData and cleaning Build Folder This issue seems to be occurring recently only since launch of Xcode 16.4 Other Device info Macbook Pro macOS: Sequoia 15.5 Xcode: 16.4

A little bit of background: If you make an app with no compiled Arm64 binaries in the Content/MacOS folder, MacOS erroneously identifies it as an Intel based app. After launching the app, MacOS will prompt the user to install rosetta, despite the app running fine natively. I found a simple solution to this issue, either include a do-nothing compiled binary to Contents/MacOS, or add <key>LSArchitecturePriority</key> <array> <string>arm64</string> </array> to the plist. The problem is this change only fixes the issue if you also change the BundleID. If you run the app even once with the bad configuration, MacOS seems to cache the intel flag somewhere based on the BundleID. It does not seem to be cached in the usual places. How to reproduce: (On apple silicon) You probably already have rosetta, and it is a pain to remove, so a VM is likely needed. Make an empty app with Script Editor, export with file format: Application. Replace Example.app/Content/MacOS/applet with a script of the same name. Make sure the old applet is gone, don't rename it and leave it in the directory. I used: #!/usr/bin/osascript display dialog "Hello, world" Make it executable sudo chmod +x ./Example.app/Content/MacOS/applet Run the app and observe that it asks you to install rosetta Add the previously mentioned fix to you plist, including the BundleID change Run it again and observe that it now works Change your BundleID back. Running this now raises the rosetta prompt despite the fact that it runs fine on a clean install of MacOS. Things I have tried: Rebooting, no effect Reforming the app, no effect Reboot in recovery mode, no effect lsregister -delete, no effect ~/Library/Preferences, ~/Library/Caches, /Library/Preferences, and /Library/Caches, none contain an entry for the BundleId defaults delete, domain not found

Hello, Can anyone help me with the below? I've been sent the below bolded, italicized message three time in a row now with no further explanation. _**Please note that links are required to be included in both of the metadata and the binary. We noticed that your app binary is still missing: A functional link to your privacy policy A functional link to your Terms of Use This information is required for apps which include auto-renewable subscriptions.**_ My reviewer initially instructed me to include my terms of use link in my app description (as my privacy policy was already displayed). I followed that instruction and that subsequently started the persistence of the bolded, italicized message. For full context, the links are in my app description and on my paywall inside of the app itself. I need help and clarity on what I'm missing so I can get the app approved. Also, if anyone knows any alternative ways of allowing users to purchase a subscription within the app that Apple allows - I would appreciate that information, as it seems this process is too complicated for me.

Hello everyone, I'm currently experiencing repeated "Invalid Binary" rejections when submitting my Flutter-based iOS app ("Master Tere") through App Store Connect. I've followed all the expected steps and guidelines, but the rejection contains no additional explanation beyond the "Invalid Binary" status. Here’s my current setup: Built using Flutter and Xcode 15.3 WebView-based app loading a professional portfolio site Runner target is signed automatically using Xcode Managed Profiles Certificates: Apple Development and Apple Distribution (auto-managed) Bundle ID: com.actuain.mastertere1 Version: 1.0.0, Build: 6 Deployment target: iOS 18.0 Device family: iPhone only All signing identities and provisioning profiles match for Debug and Release In my Info.plist, I’ve cleaned up legacy keys that might cause conflicts: ✅ Removed <key>UIMainStoryboardFile</key> (no storyboard is used) ✅ Removed <key>CFBundleSignature</key> as it was set to ???? ✅ Display name and Bundle ID align with Xcode project settings Despite all this, every time I upload through Xcode Organizer, I get an "Invalid Binary" error after processing. No issues are shown during archive validation. I suspect the issue may be related to: Flutter WebView integration with latest iOS SDKs Residual metadata in the archive from unused iOS storyboard references Possibly missing entitlements or capabilities not flagged by Xcode Questions: Are there any known issues affecting Flutter WebView apps recently (especially around Xcode 15.3 or iOS 18 SDK)? Is it mandatory to remove Main.storyboard from the project bundle even if it's not used? Could this issue be related to background modes, UIRequiredDeviceCapabilities, or entitlements even if not directly flagged? I’d appreciate any insights or experiences from others who’ve faced this issue recently. Thanks in advance! Luis Antonio Pinto Acosta

Hi! I'm uploading a Flutter app using Xcode 15.3 and everything builds and runs fine on my iPhone. I use automatic signing with valid development and distribution certificates. The upload to App Store Connect completes successfully and shows as “Waiting for Review”, but after a few minutes it changes to: iOS 1.0 — Invalid Binary There are no other error details. I've checked Info.plist, signing settings, build/version numbers, and everything seems okay. Does anyone know what “Invalid Binary” means or what might be causing it? Thanks in advance!

Im getting Invalid Binary error the last 48 hours, I cant find a solution for this problem, also the apple dont give more information about the error. Please can you provide more information about the Invalid Binary rejection.

i got this email how solve this issue

i got this email please provide me solution on this binary error

Hello everyone, I’m currently developing an Electron application, and I’m trying to properly sign and notarize it for macOS. The notarization process itself seems to complete successfully—the file is accepted without issues. However, when I attempt to staple the notarization ticket to the executable, I consistently get Error 65 with TheStableAndValidateActionFailed. The issue is puzzling because the executable does not change at any point during the process. After facing this issue multiple times in my own project, I decided to test it on a more controlled setup. I followed the steps from this https://www.youtube.com/watch?v=hYBLfjT57hU and the instructions from this macos-code-signing-example which have previously worked for others. Yet, even with this setup, I still get the same Error 65. Below, I have attached the verbose logs for reference. I’m trying to understand what could be causing this issue—whether it’s related to certificates, the signing process, or something else entirely. Has anyone encountered a similar problem, and if so, how did you resolve it? Any insights would be greatly appreciated!

Hello Apple Developer Community, I recently created a fresh project with: No dependencies No additional written code After generating the iOS build, I navigated to the build folder:"build/ios/iphoneos/Runner.app" Then, I ran the following otool commands to inspect the binary: otool -Iv Runner | grep -w _strlen otool -Iv Runner | grep -w _malloc Surprisingly, I received positive results, meaning these functions are present in the binary. My Questions: Why is a fresh project (with no extra dependencies & No additional written code) including these APIs in the binary?

Hello Apple Developer Community, I recently created a fresh project with: No dependencies No additional written code After generating the iOS build, I navigated to the build folder: cd build/ios/iphoneos/Runner.app Then, I ran the following commands to inspect the binary: otool -Iv Runner | grep -w _strlen otool -Iv Runner | grep -w _malloc Surprisingly, I received positive results, meaning these functions are present in the binary. My Questions: Why is a fresh Flutter project (with no extra dependencies) including these APIs in the binary?

I'm trying a release a new version to one of my Apps. Last success was January 25, but now I'm keep getting "Invalid binary" error no matter what I'm doing, with no further info about the source of the problem. I clarified all settings are correct and tried different ways (direct upload from xCode, using Transporter). I even rollback my project to the same version I used when I was able to release a new version (Jan 25), and with the same project content - same code, same settings, only changed version - I also got the same error response. Any idea?

I have these two pods: Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher Frameworks/GoogleToolboxForMac.framework/GoogleToolboxForMac they are showing this error: ITMS-91061: Missing privacy manifest I've tried manually making privacy files, I've tried updating the SDK's too. I cant update them because firebase depends on GTM Session at a lower version and if I update, MLKit depends on toolbox (even though its deprecating) If I upgrade then the whole project explodes. What do I do. I need help. this is all I get and it doesn't help: https://developer.apple.com/support/third-party-SDK-requirements

Could not launch “App Name” Domain: IDELaunchErrorDomain Code: 20 Recovery Suggestion: LaunchServices has returned error -54. Please check the system logs for the underlying cause of the error. User Info: { DVTErrorCreationDateKey = "2024-12-27 12:16:34 +0000"; DVTRadarComponentKey = 113722; IDERunOperationFailingWorker = IDELaunchServicesLauncher; } The operation couldn’t be completed. (OSStatus error -54.) Domain: NSOSStatusErrorDomain Code: -54 User Info: { "_LSFunction" = "_LSOpenStuffCallLocal"; "_LSLine" = 4224; }

Hi I uploaded an app in apple account but app getting rejected with The status of your app has changed to Invalid Binary. I am using Xcode 15.3. I am not getting specific problem. I am getting same message as invalid binary.

I'm having some trouble with in-app purchases on Apple Store Connect, and I'm hoping someone here has dealt with a similar issue. Initially, I was able to add the purchases using the "Select In-App Purchases" button. However, after my app was refused, the in-app purchases were also rejected, and now I'm stuck in a frustrating loop: Developer Action Needed -> Waiting for Review -> Rejected. I’ve tried submitting the in-app purchases for review at the same time as the app, but that also ended in rejection. The reviewers can’t locate the in-app purchases, even though I list them in the comment box. I suspect this is because I can’t re-add them using the "Select In-App Purchases" button anymore. The instructions on "add the in-app purchases in the binary" are vague and non-specific. To make matters worse, the reviewers are commenting on issues from an older build, like a placeholder I left in the settings window. That placeholder has been removed in the latest build, but their feedback doesn’t reflect that. Has anyone encountered this loop or know how to get out of it? Any advice would be much appreciated!