“show when run”

Starting somewhere around macOS 26.3, my sandboxed file manager spontaneously loses access to ~/Library/Mobile Documents mid-session. Just to clarify, by file manager do you mean that your app is doing its own navigation of the broader file system or that your app is a file provider extension? If you're a file provider extension, why do you need/want access to so much of the system? What makes this specific to FP-backed paths: regular paths under the same '/' bookmark (~/Library/Application Support, etc.) stay accessible and recover normally with a fresh start AccessingSecurityScopedResource() call. Only ~/Library/Mobile Documents and its subtree fail - the entire tree, including the parent directory itself. What other directories have you tried? Particularly directories user directories like ~/Documents/ or ~/Downloads/? Looking at the bug, the current theory is that this is actually tied to a difference between the sandbox extension originally issued by the open panel and the new extension issued when the b

Seen this one a lot. Subscription is unavailable in the current storefront almost always comes down to one of these, in order of likelihood: Paid Apps Agreement isn't in Active state for the team. Open App Store Connect > Agreements, Tax, and Banking. If the Paid Apps agreement shows anything other than Active (Action Required, missing bank info, missing tax forms, or a contact who's no longer on the team), every subscription rejects with this exact error until it's resolved. The subscription's price schedule doesn't include the user's storefront. Each subscription has pricing set per country. If you only configured prices for some countries, users outside that list get this error. Check the Price tab on the subscription and confirm the user's country is covered. The app and the subscription are in different availability regions. Even with pricing set, the app itself must also be available in that country. Check App Availability on the main app page. The subscription isn't actually in Ready for Sa

Classic StoreKit 1 to 2 migration pitfall. A few things worth checking: The sandbox account matters more than you'd expect. When you reinstall, make sure you're signed into the same sandbox Apple ID that actually made the SK1 purchase. If it's a fresh sandbox user or a different one, there's literally no transaction to restore. Settings > Developer > Sandbox Apple Account shows who's currently active. For a non-consumable originally purchased via SK1, after AppStore.sync() completes, the transaction shows up in Transaction.currentEntitlements with its original productID, but the id or originalID might be a legacy numeric identifier rather than a UUID. If you're filtering entitlements by anything other than productID, that could be why you don't see it. AppStore.sync() triggers an Apple ID password prompt. If the user cancels that prompt, it returns without throwing but also without actually syncing. Wrap it in try/catch and log so you can distinguish canceled vs successful vs failed. I

When start arrives but updates don't on one specific device, it's almost always one of three things. Walking through them: Wrong push token for updates. The start push uses apns-push-type: liveactivity plus your app's device token. But once the activity is running, each activity has its own token delivered via Activity.pushToken (or pushTokenUpdates as an async sequence). Every update has to go to that per-activity token, not the device token, and not a stale token from a previous activity. Worth logging and diffing the token you're actually sending between 16 Pro and 16 Pro Max. stale-date already in the past. iOS silently drops updates whose stale-date is before now on the device. Small clock drift or a timezone mismatch is enough. Try pushing with stale-date explicitly far in the future and see if that changes anything. content-state schema mismatch. If your ContentState decoder throws on the update payload (new field, wrong type, enum case removed), the update is dropped with no user-visible sign

Sounds like a frustrating regression. Before chalking it up to a bug, a few things worth trying: The transaction cache in Xcode's StoreKit environment gets into weird states after major version upgrades. From Xcode, open Debug > StoreKit > Manage Transactions, delete everything in there, then clean build folder (Shift-Cmd-K), nuke DerivedData, and restart Xcode. On the running target, delete the app entirely before re-running. Second, check your scheme's StoreKit configuration setting. The Xcode 16 to 26 migration has been resetting StoreKit Configuration to None on some projects. Edit Scheme > Run > Options, confirm your .storekit file is still selected. Third, when purchases silently fail without even showing the confirmation sheet, it's usually the store failing to resolve the product ID. Open the .storekit file, hit the refresh/sync icon, and confirm every product identifier matches what your code requests exactly (it's case-sensitive). Did macOS also update

@dser Thanks for the post, 26.5 beta 2 should also be fixed as showing the fix in the release notes. Will be great to get to the bottom of this and why does not work for you on 26.5 beta 2. If there is any way you can provide the information and the sysdiagnose, we could go ahead and file a bug? Albert
  Worldwide Developer Relations.

Hello.. if you edit the scheme to run the app as root, then the menu works.. this is a risky workaround that you can use only when testing the menu, after that, better go back to the previous setting.

Hey , Hoping you might be able to share some of your wisdom with me. I’m an iOS dev with around 9 years experience and this past year have finally started shipping my own apps. For me the biggest thing I’m struggling with is distribution. Primarily, I’m posting on TikTok as that’s where a majority of my audience seem to be. Im running search ads for specific keywords but I’m remaining conservative with the bids as it just doesn’t have the ROI. how have you handled marketing or has it been mostly ASO? A self sustaining indie dev life is the goal in the next 3-5 years for me. So would love to hear more from you about your experience!