missing package product

Issue: SKOverlay configured with a Custom Product Page identifier opens the default product page instead of the custom one on iOS 26. This works correctly on iOS 18 and earlier. Details: Custom Product Page is published and valid in App Store Connect customProductPageIdentifier is correctly set on SKOverlayAppConfiguration Same code works fine on iOS 18 and lower Code: - (void)presentSKOverlayInWindowScene:(UIWindowScene *)scene { SKOverlayAppConfiguration *config = [[SKOverlayAppConfiguration alloc] initWithAppIdentifier:@my_app_id position:SKOverlayPositionBottom]; config.userDismissible = YES; if (@available(iOS 15.0, *)) { [config setCustomProductPageIdentifier:@my_apps_custom_product_page_id]; } SKOverlay *overlay = [[SKOverlay alloc] initWithConfiguration:config]; overlay.delegate = self; [overlay presentInScene:scene]; } Are there any known iOS 26 changes affecting Custom Product Pages with SKOverlay, or is additional configuration now required. Thank you

Hello! Ive been working on a package tracking app for iOS and was looking forward to pushing it to TestFlight for some testers to use. When I go to archive the package, I get a warning about the ...TrackerIntents.appex is an ExtensionKit extension and must be embedded in the parent app bundle's Extensions directory, but is embedded in the parent app bundle's Tracker.app/Extensions directory. The extension is for siri integration with shortcuts. I have done quite a lot of things to try and diagnose this but cant seem to get passed this warning. I know it's a warning but would rather it not exist. Ideally I would think its a matter of moving the items but in the navigation area, I dont see an extensions area. The main app target has it in the dependencies along with the EmbedExtensionKit Extensions in the Build Phases. Any ideas or configs I can try? I can provide more information if needed. This is on the latest Xcode version 26.0.1 for iOS 26. Thank you.

I’m honestly about to lose my mind at this point. My apps have been stuck in “Waiting for Review” for almost a month, and I still have zero progress, zero response, and zero clarity on what’s going on. Here are the facts: Both of my apps were submitted for review nearly 30 days ago Status: Still “Waiting for Review” with no movement at all I contacted Apple Support multiple times — no useful feedback was provided One of my expedited review requests was approved 4+ days ago, yet the status of the app hasn’t changed whatsoever This situation is extremely frustrating. I’m a developer trying to run a business, and these unexplained delays are causing serious damage to my release timeline, marketing schedule, and user acquisition plans. I genuinely don’t understand why things are stuck for this long. All I’m asking for is basic transparency: Why is the review not starting? Why is the expedite request approved but not reflected in the review queue? Is there a hidden issue blocking my apps that I am not bei

I’m genuinely on the edge of losing my sanity right now. My apps have been stuck in “Waiting for Review” for almost a MONTH, yes, 30 days and absolutely nothing is happening. At this point, I’m not even sure if my apps are in a review queue or a black hole. Here’s my situation: 2 apps submitted, both still “Waiting for Review” 30 days of zero movement Contacted support multiple times, replies that lead nowhere Expedited Review request APPROVED 4+ days ago… and guess what? Still no movement. Not even a “Hi, we’re looking at it.” I feel like I’m talking to a wall. This is starting to feel like a glitch in the Matrix. This is seriously impacting my launch, marketing, business timeline and user acquisition strategy. I love Apple, I love the platform, but this silence and lack of transparency is painful for developers. What we need is very simple: A realistic timeline 1 week? 2 weeks? A month? If expedited review is approved, why is nothing happening? If there’s an issue, just tell me so I can fix it inst

We are currently experiencing a very interesting issue when accessing the location in the background with CLLocationManager. The user has given our app the whenInUse permission for locations and in most cases the app provides location updates even when it's in the background. However, when we started to use other navigation apps in the foreground we saw that the func locationManager(_ manager: CLLocationManager, didFailWithError error: Error) method was called with (kCLErrorDomain error 1.). The user hasn't changed the location permission and we saw that locations were delivered once the user opened the app again. I don't see anything in the documentation explaining this issue, but I chatted with other developers that confirm that specific behavior. Am I missing something here?

I’m testing auto-renewable subscription purchases in the sandbox environment. When I buy a subscription package using a sandbox test user, I don’t receive any App Store Server Notifications from the sandbox. However, when I use the “Request Test Notification” option in App Store Connect, the notification is received successfully. My sandbox server notification URL is configured correctly and publicly accessible. I also call finishTransaction() after purchase, and the receipt is verified successfully with the sandbox verification endpoint. To further debug, I used the getNotificationHistory API to fetch notifications for yesterday and today (Nov 3–4, 2025). Apple’s API response does not include any notifications or transaction IDs for my today’s purchases (Nov 4, 2025) — even though I can confirm from logs that those transactions were completed and verified successfully. It looks like sandbox purchase notifications are not being sent or logged, even though test notifications work fine. Could someone f

Hey guys 👋🏼 I'm trying to publish my first App, but it's not working and sadly the Support didn't have an answer too. Maybe someone experienced the same thing. Yesterday I enrolled in the Developer Program and today my account was switched from an individual to a corporation account (to display my business name instead of my private name). I got an email that the switch was successful. When Archiving the app in Xcode and trying to distribute I get this error message: App Record Creation failed due to an invalid attribute. Request failed with error code ENTITY_ERROR.ATTRIBUTE.REQUIRED, and reason The provided entity is missing a required attribute You must provide a value for the attribute 'companyName' with this request Fits to the thing the support said to me, I should go to appstoreconnect to add my first app there and then I should ask me to create my company name. But it doens't. I just get an error with no information what to do. All Agreements are signed, banking information is filled out … M

I am trying to make build for my project followed all step and all but Igot Showing Recent Errors Only Build target PCS_EmpApp of project PCS_EmpApp with configuration Debug ProcessInfoPlistFile /Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-bhccfqkphneiyabcysmesvskjrrm/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync/Info.plist (in target 'PCS_EmpApp' from project 'PCS_EmpApp') cd /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync builtin-infoPlistUtility /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync/Info.plist -producttype com.apple.product-type.application -genpkginfo /Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-bhccfqkphneiyabcysmesvskjrrm/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/PkgInfo -expandbuildsettings -format binary -platform iphon

Network.framework: Happy Eyeballs cancels also-ran only after WebSocket handshake (duplicate WS sessions) Hi everyone 👋 When using NWConnection with NWProtocolWebSocket, I’ve noticed that Happy Eyeballs cancels the losing connection only after the WebSocket handshake completes on the winning path. As a result, both IPv4 and IPv6 attempts can send the GET / Upgrade request in parallel, which may cause duplicate WebSocket sessions on the server. Standards context RFC 8305 §6 (Happy Eyeballs v2) states: Once one of the connection attempts succeeds (generally when the TCP handshake completes), all other connections attempts that have not yet succeeded SHOULD be canceled. This “SHOULD” is intentionally non-mandatory — implementations may reasonably delay cancellation to account for additional factors (e.g. TLS success or ALPN negotiation). So Network.framework’s current behavior — canceling after the WebSocket handshake — is technically valid, but it can have practical side effects at the application lay