Hello, My team is currently having an issue uploading our app to the AppStore because of the following issues: ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary because it includes assembly source code or inline assembly. To resolve this issue, rewrite the corresponding code in a higher-level language such as Objective-C or Swift and redeliver your app.  ITMS-90562: Invalid Bundle - There's an issue with the app's bitcode compilation. Rebuild the app using the current public (GM) version of Xcode and upload it again. Firstly, we do not have a watchOS app at all. Our last release was successful when built on Xcode 11.6 and we're currently using Xcode 11.7. According to Apple, Xcode 12 isn't required until April of 2021, so I'm not sure what it's complaining about. Here's what we've tried. We created an AppStore build and ran it through the validator and that succeeded. It even uploads fine, but doesn't successfully process once uploaded. We created an Enterprise version of our app and exported it, making sure to enable the "Rebuild from Bitcode" option to hopefully mimic what the AppStore is doing and failing at and it still succeeds. We downloaded and used the Transporter app from Apple to try uploading our AppStore ipa, but the logs didn't indicate anything suspicious (perhaps because the bitcode compilation for AppStore variants happen on Apple's servers?) We searched for anything that could have indicated "watch" or "watchOS" in our codebase and build settings and dependencies (built from Carthage), but we didn't find anything there either. We went through the Export phase again for the AppStore build and disabled Bitcode. The only one to succeed was #5, but we don't want to do this as a long term solution, but don't understand how to get more information as to what the problem is exactly. Does anyone have any information on this?

Hi, We are using Firebase Crashlytics to collect crashes from our app. Firebase Crashlytics says that the dSYM is missing to process crashes for the recent two versions of our app. We have recently not changed anything in our app distribution process (it is based on CI/CD). For the non-product change, we moved one of our internal frameworks to be managed by SPM (previously Carthage). In build settings, we have set : Debug information format: DWARF with dSYM Files Enable bitcode: Yes Because of the latter, we manually download all dSYMs from the AppStoreConnect page and upload them to the Firebase Crashlytics for each new version. I've double-checked the UUID's and the one mentioned by Firebase is missing in the downloaded (from the AppStoreConnect) zip file. The zip file contains dSYM for our app but with a different UUID. Is there anything I can do to verify that generated dSYMs have the correct UUID? Not sure if this is related, but when I try to download crashes via Xcode Organiser, I got an error: Unable to download crash information. An error occurred preventing Xcode from downloading updated crash information. The value “2021-07-27T00:00:00Z” is invalid. Please try again later.

When Submitting new App version for Review, the status changed to Invalid Binary and I got an email saying the following: We identified one or more issues with a recent submission for App Store review for your app, ****************. Please correct the following issues, then upload again. ITMS-90118: Invalid routing app setting: To upload a routing app coverage file on App Store Connect, you must define the app binary as a routing app.

We met some feedback of upgrade installation failed, I also met the same issue. And I can make sure I didn't cancel the upgrade install, but the apple system log shows install failed reason due to the user canceled. canceled by client 1 for reason Error Domain=IXUserPresentableErrorDomain Code=3 "This installation was canceled by the user." UserInfo={NSLocalizedFailureReason=User canceled., NSLocalizedDescription=This installation was canceled by the user.}). By analyzing the system log, I guess when upgrading the in-house app, the iOS system may need to uninstall the old version app, but the uninstall operation may fail due to some unknown reason. And will lead the upgrade install failed(the real install failed reason). I don't know well about the installation of the in-house app. I think the in-house app upgrade install has some bugs. Does anyone meet the same issue when upgrading the in-house app? Please download detail install log uploaded in the attachment! detail upgrade install log 2022-01-27 22:34:19.225873 +0800 nehelper Handling an apps installed notification with bundle IDs ( "com.***.yyy" ) 2022-01-27 22:34:19.291323 +0800 runningboardd Acquiring assertion targeting system from originator [daemon<com.apple.mobile.installd>:203] with description <RBSAssertionDescriptor| "FBSApplicationTerminationAssertion" ID:32-203-1450 target:system attributes:[ <RBSPreventLaunchLimitation| <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "com.***.yyy">>> ]> 2022-01-27 22:34:19.293129 +0800 runningboardd Executing termination request for: <RBSProcessPredicate <RBSProcessBundleIdentifierPredicate "com.***.yyy">> 2022-01-27 22:34:19.531831 +0800 installd 0x16cf8b000 -[MIUninstaller performUninstallationWithError:]: Uninstalling parallel placeholder for com.***.yyy 2022-01-27 22:34:19.533612 +0800 installd com.***.yyy:7:9:2:1:Success (End) : Uninstall (Parallel Placeholder) 2022-01-27 22:34:19.537589 +0800 SpringBoard termination assertion released for com.***.yyy 2022-01-27 22:34:19.537889 +0800 lsd com.***.yyy:5:6:1:1:Unregister bundles - Start 2022-01-27 22:34:19.674045 +0800 lsd com.***.yyy:5:6:1:1:Beginning _LSUnregisterAppWithBundleID (placeholder only) 2022-01-27 22:34:19.756216 +0800 installcoordinationd -[IXSDataPromise cancelForReason:client:]: <IXSPlaceholder(0x15ff07b80) Name:App Placeholder: inhouse (com.***.yyy) Creator:App Store UUID:972307B4-DC5D-4A50-8421-4AE931560BA9> : canceled by client 1 for reason Error Domain=IXUserPresentableErrorDomain Code=3 "This installation was canceled by the user." UserInfo={NSLocalizedFailureReason=User canceled., NSLocalizedDescription=This installation was canceled by the user.} 2022-01-27 22:34:19.756742 +0800 installcoordinationd -[IXSDataPromise decommission]: Decommissioning <IXSPlaceholder(0x15ff07b80) Name:App Placeholder: inhouse (com.***.yyy) Creator:App Store UUID:972307B4-DC5D-4A50-8421-4AE931560BA9> 2022-01-27 22:34:19.757803 +0800 installcoordinationd -[IXSDataPromise cancelForReason:client:]: <IXSPromisedStreamingZipTransfer(0x15fe0e460) Name:UPP599852B1/com.***.yyy Creator:App Store UUID:36AE0914-4D2F-4C30-BE98-ED352ED22145 PercentComplete:0.108321 IsComplete:N DiskUsageBytes:0> : canceled by client 1 for reason Error Domain=IXUserPresentableErrorDomain Code=3 "This installation was canceled by the user." UserInfo={NSLocalizedFailureReason=User canceled., NSLocalizedDescription=This installation was canceled by the user.} 2022-01-27 22:34:19.759059 +0800 installcoordinationd -[IXSDataPromise decommission]: Decommissioning <IXSPromisedStreamingZipTransfer(0x15fe0e460) Name:UPP599852B1/com.***.yyy Creator:App Store UUID:36AE0914-4D2F-4C30-BE98-ED352ED22145 PercentComplete:0.000000 IsComplete:N DiskUsageBytes:0> 2022-01-27 22:34:19.784715 +0800 appstored Placeholder for application {bundleID = com.***.yyy; version = 2201122041; shortVersion = 1.8.1; variantID = (null)} removed, re-verifying installed application 2022-01-27 22:34:19.786051 +0800 appstored Handling application installation: {bundleID = com.***.yyy; version = 2201122041; shortVersion = 1.8.1; variantID = (null)} 2022-01-27 22:34:19.786089 +0800 appstored Ignoring installation for {bundleID = com.***.yyy; version = 2201122041; shortVersion = 1.8.1; variantID = (null)} as it does not appear to support ODR 2022-01-27 22:34:19.787542 +0800 appstored Canceling progress for bundleID: com.***.yyy 2022-01-27 22:34:19.807920 +0800 navd com.***.yyy:5:8:3:1:applicationsDidInstall <LSApplicationProxy: 0x103859f80> com.***.yyy file:///private/var/containers/Bundle/Application/70D1ADCE-B225-4F55-84A1-CA834A516F45/inhouse.app/ <com.***.yyy <installed >:0> 2022-01-27 22:34:21.645313 +0800 tccd Handling Application Uninstalled event for { bundleIDs = ( "com.***.yyy" ); isPlaceholder = 1; }. 2022-01-27 22:34:22.107373 +0800 tccd LS says com.***.yyy was uninstalled but now we have found it is still installed. 2022-01-27 22:34:28.331871 +0800 nehelper Handling an apps uninstalled notification with bundle IDs ( "com.***.yyy" ) 2022-01-27 22:34:28.754040 +0800 nehelper Handling an apps installed notification with bundle IDs ( "com.***.yyy" )

The review of your app is taking longer than expected. once we have completed our review, we will notify you via resolution center. Why they saying that the review will take longer but when I look my binary it says rejected?

Hello All, I am trying to generate mdx using distribution profile. When I build the app, I get the mdx. But when I try to archive I am getting the below error, checkOrderDynamicLibrariesInSDKImage: check dylib failed: /Users/charita/Library/Developer/Xcode/DerivedData/AppMAMSDKIntegrationTwo-antnnuimpdsltjeudfyzjsuizlyz/Build/Intermediates.noindex/ArchiveIntermediates/AppMAMSDKIntegrationTwo/InstallationBuildProductsLocation/Applications/AppMAMSDKIntegrationTwo.app/AppMAMSDKIntegrationTwo 1115 2021-11-04 11:42:19.359 CGAppCLPrepTool[90875:286613] [ToolkitLib] ERROR: Unknown loader command found in the application binary image. Please note that I am using the latest MAM SDK library - 21.9.0

Can Xcode build a macOS native application that uses compiled Python code? I know Python scripts can be compiled into OS-level executables (I haven't tried PyInstaller, etc. on macOS yet) ... and I'm assuming the bundled Python executable can be included inside the Application Package ... but I was hoping there's a way to include Python code as a subroutine/object and call it natively within a "native" macOS application.

I have previously been able to upload multiple versions of our app (built in flutter) to TestFlight and the App Store. However now, seemingly randomly, I cannot even validate or distribute any archive generated in order to upload it to App Store Connect. The error being displayed is as follows App Store Connect Operation Error: No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. From extensive googling, I have tried the following solutions to no avail: Updating to the latest XCode (Version 12.5.1) Removing pod folder and re running pod install Enabling bitcode - can't even build the archive as this causes other errors Restarting XCode Setting all frameworks as "Do not embed" Help! I'm at a loss, and really need to get this uploaded today!

Hello folks, I am practically at my wits end here and I think I have searched high and low and can't find any definitive steps or answers that can point me in the right direction. My team is working on a command line executable tool that is written in C. We have built the code on Mac OS 11.5 using our internal tools (no Xcode unfortunately) and are able to test and verify everything works. Now comes the hard part of signing and notarizing the tool so it can be distributed to our end users. I have figure out how to sign the executable and add some entitlements, the problem I have now is the notarization. Currently the tool is bundled in a dmg with the structure shown below. I ran the xcrun altool to notarize the dmg and after a couple hours it was successful. I was able to staple the ticket to the dmg but I don't see a way to staple the ticket to the tool itself (Stapling is not supported for mach-O binaries). I was able to mount the dmg but when I click on the installer script or the executable, I get the dreaded gatekeeper warning that the developer cannot be confirmed. Anyone know any guides I can follow to get this application bundled and notarized and signed properly so my end users don't get hassled by gatekeeper? Any help is greatly appreciated. Dmg structure: DMG |----- Folder | |----- dylib files | |----- command line tool | |----- installer script (copies dylibs to /usr/local/lib and copies command line tool to /usr/local/ path and adds to PATH % xcrun stapler staple clitool.dmg Processing: Downloads/Payload/clitool.dmg Processing: Downloads/Payload/clitool.dmg The staple and validate action worked!