“missing package product”

Thanks so much for this post and thanks for your patience on my replay. When Unicode characters and emojis render perfectly on a physical device but appear as blank spaces or empty boxes in the Simulator and SwiftUI Canvas, in my opinion it means the Color Emoji font is missing and this is corrupted, or failing to load inside the Simulator Runtime. Because the SwiftUI Canvas uses the exact same underlying simulator infrastructure as the standalone Simulator app, both break at the same time. We identified this a bug and I would encourage you to use the physical device or to download the latest beta simulators iOS 24.4 RC https://developer.apple.com/download/os/ and let me know it the issue has been fixed. Here are the most effective ways to resolve this issue: Open Xcode and go to Xcode > Settings (or Preferences) > Platforms. Find the iOS Simulator runtime you are currently using (e.g., iOS 26.3). Right-click (or Control-click) it and select Delete. Once deleted, click the + button at the botto

The one time we got Apple on the phone, we spoke to someone who said she was in charge of the testing team reviewing our app. The call was frustrating—she didn’t seem familiar with basic app testing for a location-based product (for example, how to emulate a different location) I don't know what 'emulating a different location' means, either. If it's not her own app that you are talking about, why does her unfamiliarity to your app make her incompetent? It is your responsibility, not hers, to explain how the app works. Right now we are averaging about a week at best to two weeks. What does that mean?

@App Review Following up on your response from 2 days ago. Our app (Apple ID: 1505684382) has now been in Waiting for Review for 16 days — submitted March 4th. Despite your message that you would contact us via App Store Connect, we have received no communication there. To summarize what we have tried: 2x Expedited Review requests — no response 2x Support cases via Contact Us — no response This forum post — your team replied but no follow-through yet We have exhausted every available channel. Our app includes a time-sensitive subscription pricing test, and every day of delay is causing measurable revenue loss. We respectfully ask for a concrete answer: What is preventing our app from entering review, and when will it be reviewed? Thank you.

The only way out of it was to create a build post-action script to generate the missing dsym file. Here is the gist of the script: set -euo pipefail if [ -z ${ARCHIVE_PATH:-} ]; then exit 0 fi APP_PATH=$ARCHIVE_PATH/Products/Applications/App_Product_Name.app if [ ! -d $APP_PATH/Contents ]; then exit 0 fi BIN=$APP_PATH/Contents/Frameworks/Framework_Name.framework/Framework_Name OUT=$ARCHIVE_PATH/dSYMs/Framework_Name.framework.dSYM OUT_DWARF=$OUT/Contents/Resources/DWARF/Framework_Name if [ ! -f $BIN ]; then exit 0 fi if [ ! -f $OUT_DWARF ]; then mkdir -p $ARCHIVE_PATH/dSYMs rm -rf $OUT xcrun dsymutil $BIN -o $OUT fi if [ ! -f $OUT_DWARF ]; then exit 1 fi BIN_UUIDS=$(xcrun dwarfdump --uuid $BIN | awk '{print $2}' | sort) DSYM_UUIDS=$(xcrun dwarfdump --uuid $OUT_DWARF | awk '{print $2}' | sort) if [ $BIN_UUIDS != $DSYM_UUIDS ]; then exit 1 fi

Update: Two separate teams affected, detailed timeline below Team 1 (DocuAgile): 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions) 03-17 09:06 UTC: Suddenly all Rejected (statusCode 7000, Team is not yet configured for notarization) 03-17 12:32 UTC: Brief recovery, 2 Accepted 03-17 13:08 UTC: Back to Rejected 03-18 13:51 UTC: Recovery again, 2 Accepted 03-19 02:30 UTC onwards: All stuck In Progress, logs return not yet available Tested with a 7KB minimal test.zip — also stuck: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd Team 2 (separate account): 03-11 to 03-17 03:30 UTC: All Accepted (100+ successful submissions) 03-17 09:06 UTC: All stuck In Progress, never recovered Agreement was not signed — signed it today, still no recovery All submission logs return not yet available Earliest stuck submission: 789d40c4-ff83-469f-9b9b-2ac93183125e (2026-03-17 09:06 UTC) Latest stuck submission: ef7f8dbb-a7db-44c8-910c-532761b2a528 (2026-03-19 11:53 UTC) Both teams have valid Developer ID Application certific

Update: I tested with a minimal 7KB test.zip (simple signed app) using the same keychain profile. It also stuck in In Progress immediately, confirming the issue is account/team level, not related to the package content. Submission ID for test: 015ade60-c2f8-4af7-b535-3ae7fd5c9ffd

[quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] I am trying to verify a helper binary/dylib inside my product that can be updated separately from the main binary. [/quote] Is this an executable or a dynamic library? Or do you need this test to support both? And by “inside my product” do you mean that it’s located within an app’s bundle? Or that it’s logically part of your product, but is stored in some other location on disk? And while I’ll have a lot more to say about your overall issue once I better understand it, I want to nip this one in the bud: [quote='880483022, chapo213, /thread/818938?answerId=880483022#880483022, /profile/chapo213'] Does extracting a team-id … automatically verifies that the anchor is apple? [/quote] No. You can’t trust the information you get back from SecCodeCopySigningInformation unless you’ve validated the code signature. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmai

Ugh. The only remaining thing I can think of is to have, say, a completely separate license manager application responsible for all subscriptions to the set of plugins I'm selling, and using something like mach ports to communicate with it. And I suspect that would (aside from being a pretty alien way of doing things for Mac users, at least unless you use Adobe products) probably run afoul of one or another App Store policy (would it? Adobe is certainly a precedent, though I lack their clout).

Definitely a hell of an experience in the worse way. Apple Watch Series 4 iPhone 11 Mac Neo I had 0 issues developing/deploying to Pixel WearOS, but obstacles after obstacles, developing for and deploying to Apple WatchOS. After several days of working around each obstacle with the help of Gemini, I'm adding the summary of what I had to do so far to get to initial deployment in case this helps Apple/others with fix/workarounds: Here is the complete technical post-mortem for the development environment setup. This summarizes the specific hurdles cleared to get a Watch Series 4 (watchOS 10.6.2) communicating with your Mac via a No-SIM iPhone bridge. 🛠️ Environment Recovery Summary The Networking Layer The primary blocker was extreme network instability on the default 10.0.0.x gateway. The Symptom: ping tests showed 62% packet loss and 1,000ms+ latency. The Fix: Migrated all devices to a clean 192.168.86.x subnet. The Result: Achieved 0% packet loss and ~13ms latency, providing the stable pipe

I am seeing a similar issue, but only for my Mac Catalyst archive on XCode 26. My app is a SwiftUI application that embeds an Objective-C framework built from a separate Xcode project. The framework binary itself does have UUIDs, but when I inspect the .xcarchive, the corresponding framework dSYM is missing from the archive’s dSYMs folder. What is confusing is that this does not happen for the iOS build. I use the same framework target, and when I archive the iOS app and upload to TestFlight, I do not get the warning. The problem only appears when I archive the Mac Catalyst version. So in summary: • The embedded framework binary is present in the archive • The framework executable has valid UUIDs • The app archive’s dSYMs folder does not contain the matching dSYM for that embedded framework • This only happens for Mac Catalyst • The same setup works correctly for iOS Has anyone seen Catalyst archives skip generating or packaging dSYMs for embedded frameworks, even though the binary itself co