build disappears

I built Dext with a development ID and successfully re-signed and notarized it. This time, I only notarized the Driverkit, and plan to do the installer app later. Here are the steps I tried: Signed the build using Apple Development in Xcode Re-signed the build product Zipped the build product Notarized using xcrun notarytool submit, which returned Accept. Below is a sample re-signing command. codesign --sign $CODE_SIGN_IDENTITY --entitlements --options runtime --verbose --force build/Release/.app I'll probably need to eventually create an installer app and notarize it, but I think I've temporarily resolved the recent issue of not being able to sign with a Developer ID in Xcode. If you have any issues from an engineering perspective, please let me know.

Whether this entitlement is assigned on a single app or your team account would depend on the entitlement team's evaluation of your use case at the time you have made the request. This would be determined on a case by case basis, and the information you received at the time you made the request and received the entitlement would have explained your usage limitations. Best would be to contact the entitlement team and inquire about the state of your entitlement assignments. White-labelled apps could be different, depending on what you exactly mean by white-labeled. If the apps are being published by your clients directly, they will need tp apply and acquire the entitlement separately. In any case, this sounds like you would be better off contacting the entitlements team and inquire. On the technical side, you could be encountering some other issue, like a build problem not configuring the extension correctly, the extension not being launched, or crashing, etc. Using the Console app and filtering on you

The way I approach issues like this is to work backwards from the contents of the built app to understand why you received an error message, and then keep going backwards from there to see why the app was built that way. For this error, you need to inspect your built app bundle. You can do this by going to the Xcode Organizer, selecting the version of your app receiving this message, right-clicking, and selecting Show in Finder. You'll see a .xcarchive package in Finder, and you select this, right-click, and select Show Package Contents. Inside of this Xcode archive package, you'll see the folders Products/Applications/YourCoolApp.app. Right click on your .app and select Show Package Contents. We're now looking at the inner contents of your app bundle. Take a look at the contents of your Info.plist file inside this bundle, and look at the value of the CFBundleExecutable key — the value of that key is the file name of your main app binary. Does that file exist? A Missing Bundle Executable If that executable fi

Signing a distribution USB or PCI DEXT The issues described above mean that the standard Xcode GUI flow cannot be used to directly export a distribution release of a USB or PCI DEXT. Here is that flow I've found that will work: Note: The instructions below reference macOS-specific documentation, but the flow I'm describing was actually tested using an iOS project. Start by building the final version of your DEXT. On the portal, generate and download a provisioning profile for whatever environment you're going to try to build. Generate a profile for both the DEXT and the app it will be embedded in. Rename the DEXT profile you downloaded in #2 to embedded.provisionprofile”. Show the packaged contents of your DEXT and replace the existing embedded.provisionprofile (development profile) profile with the file from #3 (the release profile). Use this command to resign the DEXT with the final entitlement configuration you'll be shipping. See the Sign each code item section of Creating distribution-s

Looks like Expo opened an incident on their end due to high fail % of app build submissions Incident: https://status.expo.dev/incidents/6b3hzs8tflb9