“sandbox”

I ship a macOS audio player on the Mac App Store. I want to re-enable a remote-control feature, but I got rejected for it once already and I want to avoid burning another review cycle. I'd appreciate guidance from anyone who has shipped this pattern. What the feature does The Mac app runs a small local HTTP server (BSD sockets + GCD) on port 7777 and advertises itself over Bonjour as _tmstudioplayer._tcp. A companion iOS app discovers it with NWBrowser and controls playback: transport, volume, EQ, and so on. Everything stays on the local network. There is no cloud service, no account, no login, and no user data leaves the device. The server only accepts connections while the Mac app is running and in the foreground. This requires com.apple.security.network.server, plus NSLocalNetworkUsageDescription in Info.plist. The rejection An earlier build was rejected because com.apple.security.network.server was declared but App Review could not observe any functionality that justified it. That was fair. At the time th

Summary: After converting our Apple Developer account from Individual → Organization, our app stopped receiving APNs device tokens. application(:didRegisterForRemoteNotificationsWithDeviceToken:) is never called, and application(:didFailToRegisterForRemoteNotificationsWithError:) is also never called — no token, no error. This affects all new device‑token registrations app‑wide; device tokens issued before the conversion still work and continue to deliver pushes. Environment Membership status: Active Device: iPhone 15 Pro, iOS [26.6] Reproduced on both development (sandbox) builds installed via Xcode/CLI and TestFlight builds. What works Existing device tokens (created before ~Aug 1) still deliver pushes normally (server reports delivered 1/1 via our .p8 token‑based auth). So the send path and APNs auth key are fine. UNUserNotificationCenter authorization succeeds — authorizationStatus == .authorized. UIApplication.shared.isRegisteredForRemoteNotifications == true. What doesn't work We call UIApplica

Hello everyone, I'm facing a frustrating issue with the new App Store Connect UI when trying to submit In-App Purchases alongside my app version. My Situation: App: Nagpur Prime Property (iOS) Rejected under Guideline 2.1(b) — App Completeness Reason: IAPs not submitted with the binary What I've Done: Uploaded new Build 7 (v1.0.1) ✅ Created 2 auto-renewable subscriptions: • Basic Plan (npp_basic_plan) — Ready for Review ✅ • Premium Plan (npp_premium_plan) — Ready for Review ✅ Added both to a Draft Submission (3 items total) ✅ Sandbox tester account added ✅ The Problem: The Draft Submission panel shows: ⚠️ Unable to Submit for Review — To submit your items for review, add an app version for the selected platform. The Submit for Review button is permanently GRAYED OUT. The Draft Submission shows: Versions column: - (no app version linked) Items: 3 (Subscription Group + 2 subscriptions) The App Version (Build 7) is in a SEPARATE submission showing Ready for Review — but there is NO UI option to link the

Hoping someone from Apple or anyone who has hit this can help. While setting up my first app I made a mistake: the App Store Connect app record was created with the wrong identifier a Services ID I use for Sign in with Apple (com.mycompany.myapp.signin) instead of my real app bundle ID (com.mycompany.myapp). A second app record was bound to the correct bundle ID. It had no builds, no in-app purchases, and was never published, so I deleted it, expecting the bundle ID to be released. Current state: The correct bundle ID does not appear in the Bundle ID dropdown, either in my existing app's App Information page or when creating a new app. Deleting the App ID in the developer portal fails with: The App ID appears to be in use by the App Store, so it can not be removed at this time. It has been like this for several days; all my builds are signed with the correct bundle ID, and my subscriptions live on the surviving app record, so I cannot upload builds or run sandbox purchases until the record is on the

FileFerry is a native macOS file transfer client. It speaks FTP, FTPS (explicit AUTH TLS), SFTP, WebDAV and SMB, and opens a full SSH terminal on the same connection. Written in SwiftUI and AppKit, sandboxed, no third-party services. Requires macOS 14.6 or later. Free during the beta. https://testflight.apple.com/join/yY7JpHBP What I would most like tested The protocol side, against servers I have no access to: FTP directory listings from servers other than vsftpd and ProFTPD. MLSD is preferred where available; the LIST parser is the part most likely to break on an unusual date or month format, and a line it cannot parse means the file is missing from the table. FTPS against servers that require TLS session reuse on the data connection. vsftpd defaults to requiring it; the app uses separate connections and reports 522 with an explanation rather than failing silently. Self-signed certificates and host key changes. Fingerprints are confirmed once and then checked every session; a changed one refuses th

Hi all, I’m building a sandboxed macOS app that, among other things, lets the user create and associate an Apple Note with a calendar meeting. The user explicitly initiates the action. The app uses AppleScript to create the note, obtain its identifier, and open it in Notes. Notes only declares the com.apple.Notes.openlocation scripting access group. Note creation is not covered, so com.apple.security.scripting-targets does not appear sufficient. The working implementation requires: com.apple.security.automation.apple-events com.apple.security.temporary-exception.apple-events for com.apple.Notes NSAppleEventsUsageDescription Has anyone successfully shipped a Mac App Store app using this temporary exception to control the built-in Notes app? Is this potentially acceptable with a clear entitlement explanation and Feedback Assistant report, or should I assume that note creation through AppleScript cannot be included in a Mac App Store build? Is there another supported API that can create an Apple Note an

Hi! I'm experimenting with a macOS app using Finder Sync, and I'd like to make sure I'm heading in the right direction before I build too much. The workflow I'm aiming for is: • Right-click a folder in Finder • Choose Create Sticky Note • Get the selected folder URL • Launch (or activate) the main app • Open a small floating NSPanel that's associated with that folder The panel itself would live in the main app, not inside the Finder extension. The goal is simply to store notes associated with a specific folder. A few questions: Is Finder Sync the right technology for this kind of workflow, or is there a better API I should be looking at? Is opening a floating NSPanel from a Finder context menu (via the main app) a reasonable architecture on current versions of macOS? What's the preferred way for a Finder Sync extension to communicate with the main app these days? XPC? App Groups? Distributed Notifications? Something else? Are there any sandbox or App Store review limitations I should be aware of with

Game Center matchmaking fails for all non-default users on Apple TV — no IDS registration for secondary users (FB24156316) On a multi-user Apple TV (tvOS 26.5, Apple TV 4K 3rd gen), Game Center real-time matchmaking fails for every user except the default user, in every app I've tested — including Apple Arcade titles. Filed as FB24156316 with full logs and sysdiagnose; posting here for visibility and in case anyone has shipped multi-user GC multiplayer on tvOS successfully. My game adopts com.apple.developer.user-management (runs-as-current-user-with-user-independent-keychain). The entitlement itself works: on a secondary user's profile the app runs under that user's persona and GKLocalPlayer authenticates as them — the welcome banner shows the right account. But any GKMatchmakerViewController quickmatch hard-fails within ~9 seconds (Failed to find players), and accepting an invite fails with GKError 35 (not signed in to iCloud) even though Settings shows that user's iCloud as signed in. Unified logs show the