missing package product

I’m stuck with repeated production crashes in my SwiftUI app and I can’t make sense of the traces on my own. The symbolicated reports show the same pattern: Crash on com.apple.CFNetwork.LoaderQ with EXC_BAD_ACCESS / PAC failure Always deep in CFNetwork, most often in URLConnectionLoader::loadWithWhatToDo(NSURLRequest*, _CFCachedURLResponse const*, long, URLConnectionLoader::WhatToDo) No frames from my code, no sign of AuthManager or tokens. What I’ve tried: Enabled Address Sanitizer, Malloc Scribble, Guard Malloc, Zombies. Set CFNETWORK_DIAGNOSTICS=3 and collected Console logs. Stress-tested the app (rapid typing, filter switching, background/foreground, poor network with Network Link Conditioner). Could not reproduce the crash locally. So far: Logs show unrelated performance faults (I/O on main thread, CLLocationManager delegate), but no obvious CFNetwork misuse. My suspicion is a URLSession lifetime or delegate/auth-challenge race, but I can’t confirm because I can’t trigger it. Since starting this

My workout watch app supports audio playback during exercise sessions. When users carry both Apple Watch, iPhone, and AirPods, with AirPods connected to the iPhone, I want to route audio from Apple Watch to AirPods for playback. I've implemented this functionality using the following code. try? session.setCategory(.playback, mode: .default, policy: .longFormAudio, options: []) try await session.activate() When users are playing music on iPhone and trigger my code in the watch app, Apple Watch correctly guides users to select AirPods, pauses the iPhone's music, and plays my audio. However, when playback finishes and I end the session using the code below: try session.setActive(false, options:[.notifyOthersOnDeactivation]) the iPhone doesn't automatically resume the previously interrupted music playback—it requires manual intervention. Is this expected behavior, or am I missing other important steps in my code?

Hello everyone, I recently submitted my new app “Bitcoin Miner – Mining Pool” for App Review. The app was submitted under my Apple Developer account (Account Holder: Harshil Patel). However, the status has been “Waiting for Review” for over 2 days without any movement. 📍 Details: Submission platform: App Store Connect Metadata & screenshots uploaded correctly No compliance warnings or “Missing Information” alerts No previous rejections for this version I understand the review process time may vary, but I’m unsure whether this delay is normal or if there’s something more I should check on my side. 👉 Questions for the community / Apple Team Is there a typical timeline for apps currently showing “Waiting for Review”? My only goal is to ensure the submission process is moving correctly. Any guidance or suggestions will be highly appreciated. Thank you! — Harshil Patel

We are developing a messaging app which sends End-to-End encrypted data. The application supports multiple types of E2EE data, including text messages and voice over IP calls. Apple's article titled “Sending End-to-End Encrypted VoIP calls” (https://developer.apple.com/documentation/callkit/sending-end-to-end-encrypted-voip-calls) states that the following steps are required to support E2EE VoIP calls: Request permission to receive remote notifications through the User Notifications framework Register for VoIP calls using PuskKit Add a Notification Service Extension target to your app. Add the com.apple.developer.usernotifications.filtering entitlement to the NSE target’s entitlements file. We have completed steps one through three. We are still missing the filtering entitlement. As of right now the system does not allow us to use reportNewIncomingVoIPPushPayload(_:completion:) method because of the missing entitlement.
 Below is a short description of how our messaging app works: User sends

Hello Apple Developer Community, I am implementing the Return to Service feature with app preservation in our MDM solution (iOS 26+). My goal is to use the EraseDeviceCommand to securely erase user data while preserving managed apps, and then have the device automatically re-enroll without user interaction. What I am doing: The device is supervised and successfully enrolled in Automated Device Enrollment (ADE). The device has generated and escrowed a bootstrap token to our MDM server (SetBootstrapToken received). I am sending the EraseDeviceCommand to the device via MDM with the necessary parameters for Return to Service with app preservation. The command payload includes: Enabled: true The previously escrowed BootstrapToken (as Base64 data). WiFiProfileData (as Base64 data) to ensure connectivity post-erase. Example Payload Structure (Simplified): ReturnToService Enabled BootstrapToken YOUR_BASE64_TOKEN WiFiProfileData YOUR_BASE64_WIFI_PROFILE The observed behavior: The erase command is successful. The de

The review team rejected our application wrinting this : We have started our review, but we need additional information to continue. Specifically, it appears your app may access or include paid digital content or services, and we want to understand your business model before completing our review. Our app is free and doesn't include any payement package or page But we are coupled to another application for the login. And this other application has a trial period and effectively needs payment after. Do i need to explain in my app all the payment process of the other app ?

Hi everyone, I’m currently facing a blocking issue during App Review, and I’d really appreciate some help from anyone who has experienced something similar. My app was rejected under Guideline 2.1 – App Completeness with the following message: “An error message appeared after trying to Sign in with Apple. Device: iPad Air (5th generation), iPadOS 26.1.” The problem is: I cannot reproduce this bug at all, even when testing under the same conditions. ✔ What I tested: Physical iPad Air M2 on iPadOS 26.1 Physical iPhone devices iOS/iPadOS simulators (latest Xcode) TestFlight build (clean install) Debug build installed via Xcode (device connected) In every case, Sign in with Apple works correctly: Authentication sheet displays properly Callback returns the credential User is created/logged in without error No crash, no rejected promise, no empty credential ✔ Environment Using ASAuthorizationAppleIDProvider + ASAuthorizationController Default Apple Sign In button No custom nonce/redirect modifications No backend pr

Hello, I’m contacting you for assistance regarding an App Review issue that our company is currently facing. Background Several months ago, a former employee submitted an early prototype of our app using his personal Apple Developer account. That submission was never approved, and after the employee left the company, he removed the app from his account. It is no longer available on the App Store and no longer listed under that account. Recently, we rebuilt the product completely — new UI, new codebase, and a fully updated design — and submitted it under our company’s official Apple Developer account. Issue Our recent submission was rejected with 4.3 – Spam, indicating that our app is considered a duplicate of another existing app. However, the only similar app is the old prototype submitted several months ago by the former employee, which was removed and never published. It seems likely that our submission is being linked to that previous prototype, even though it no longer exists and was submitted u