Overview

Hello, I have an app that is using iOS 26 Network Framework APIs. It is using QUIC, TLS 1.3 and Bonjour. For TLS I am using a PKCS#12 identity. All works well and as expected if the devices (iPhone with no cellular, iPhone with cellular, and iPad no cellular) are all on the same wifi network. If I turn off my router (ie no more wifi network) and leave on the wifi toggle on the iOS devices - only the non cellular iPhone and iPad are able to discovery and connect to each other. My iPhone with cellular is not able to. By sharing my logs with Cursor AI it was determined that the connection between the two problematic peers (iPad with no cellular and iPhone with cellular) never even makes it to the TLS step because I never see the logs where I print out the certs I compare. I tried doing "builder.requiredInterfaceType(.wifi)" but doing that blocked the two non cellular devices from working. I also tried "builder.prohibitedInterfaceTypes([.cellular])" but that also did not work. Is AWDL on it's way out? Should I focus my energy on Wi-Fi Aware? Regards, Captadoh

Hello Community I have a current app that is live in production that was last deployed under Account X. I had to change my account name to Account Y so I created a new Account and asked Apple to transfer my app. They have done and I can see my App on the new Account as well as transferring my app id (bundleID) and provisioning profiles. I am trying to push a new version of the app that was transffered but I keep on Running into this error. My Account X has expired but the new Account (Account Y) is valid and has no agreement exceptions on it. Couple of questions The Transfer Status is Active (not complete) is this correct? Is it possible there is still ties to the bundle id to the old Account X that I can no longer see I have a paid agreement present and sitting in New Status under the business page. I do not have any paid app functions on my app.

Hello, I recently applied for enrollment in the Apple Developer Program, and my application has been under review for some time (5 days now). I would appreciate any guidance or insight into the status or typical processing time. Here are my details: Full Name: Kingsley Ibok Enrollment ID: FX678S24XD Please what steps can I take now, I’d really appreciate Thank you.

I was invited to join development team. so after receiving mail to my account I clicked accept invitation button in email. but the page of appstoreconnect shows that link is expired or invalid. however admin Is inviting me 2 min ago. how can I solve this problem? what should I do?

I'm trying to release my first app (so may be missing something obvious), but it passed review 4 days ago and has been 'Ready for distribution' since then without going live. Is this normal, or am I missing some step I have to take? I saw another thread that mentioned setting pricing, but I've done that. TIA

We have an iOS app using StoreKit 2 only (no RevenueCat). Products: pro1 (non-consumable) monthly (auto-renewable) annual (auto-renewable, 14-day introductory free trial) Current App Store Connect state: all products are submitted / attached to app version 1.0 subscriptions and IAP are now in Waiting for Review annual has an introductory offer configured in App Store Connect monthly and annual are in the same subscription group App behavior: We load products using Product.products(for:) with all three product IDs. In TestFlight, for multiple tester accounts, StoreKit still returns no usable products and the paywall remains in retry state. Earlier debug checks showed: annual.subscription?.introductoryOffer == nil isEligibleForIntroOffer == false Because introductoryOffer is nil, this does not appear to be only a tester-eligibility issue. It looks like the annual subscription product is not yet surfacing its intro offer/product data in TestFlight. Question: Is it expected that Product.products(for:) / Product.SubscriptionInfo.introductoryOffer may continue returning no subscription products or no introductory offer in TestFlight while the products are only in Waiting for Review? If so, is there a typical propagation delay, or is there anything else we should verify beyond: products attached to app version products in Waiting for Review Paid Apps agreement active intro offer configured on the annual subscription Any guidance would be appreciated.

This issue has persisted for a week. Whenever I tap on "View Analytics" in Product Page Optimization, I always get the error: "The page you're looking for can't be found." Is anyone else encountering this issue? Thanks.

Updated to the latest developer beta and while on VPN I am no longer able to connect to any website with Safari. Firefox has no issues with the connection and the computer is definitely online. Firefox is able to load and use both internal pages and external sites, without any issue. Other apps on the computer are able to access the network. Safari fails immediately, with "There was a bad response from the server." If I enable developer mode and look at the network tab in Safari I don't see any requests going out for the pages, it just immediately loads ErrorPage.html and page-load-errors.css Disconnect from VPN and everything works again. Anyone else seeing this?

Hi everyone, yesterday i installed some package in my ios app , but i had a lot of problems to compile , due to reset my branch and get started from 0. My project have pods with firebase, lottie, instana and truskit but now, when a i try to run my project, xcode show "Unable to resolve module dependency" into LOTTIE, INSTANA, TRUSKIT, FIREBASE . I visited a lot of forums and websites, and i tried the followings steps: Pod deintegrate pod repoupdate pod install Clean build folder Delete derived data but isnot working. Also,I reinstalled xcode , 2 versions , i "re"clone my repository and the issue persist. Sorry, my english is basic only

[Submitted as FB21958289] A minimal SwiftUI app logs framework warnings when a bottom bar Menu is used with the system search toolbar item. The most severe issue is logged as a console Fault (full logs below): Adding 'UIKitToolbar' as a subview of UIHostingController.view is not supported and may result in a broken view hierarchy. Add your view above UIHostingController.view in a common superview or insert it into your SwiftUI content in a UIViewRepresentable instead. This appears to be a framework-level SwiftUI/UIKit integration issue, not custom UIKit embedding in app code. The UI may still render, but the warnings indicate an internal hierarchy/layout conflict. This occurs in simulator and physical device. REPRO STEPS Create a new project then replace ContentView with the code below. Run the app. The view uses NavigationStack + .searchable + .toolbar with: ToolbarItem(placement: .bottomBar) containing a Menu DefaultToolbarItem(kind: .search, placement: .bottomBar) EXPECTED RESULT No view hierarchy or Auto Layout warnings in the console. ACTUAL RESULT Console logs warnings such as: "Adding 'UIKitToolbar' as a subview of UIHostingController.view is not supported..." "Ignoring searchBarPlacementBarButtonItem because its vending navigation item does not match the view controller's..." "Unable to simultaneously satisfy constraints..." (ButtonWrapper/UIButtonBarButton width and trailing constraints) MINIMAL REPRO CODE import SwiftUI struct ContentView: View { @State private var searchText = "" @State private var isSearchPresented = false var body: some View { NavigationStack { List(0..<30, id: \.self) { index in Text("Row \(index)") } .navigationTitle("Toolbar Repro") .searchable(text: $searchText, isPresented: $isSearchPresented) .toolbar { ToolbarItem(placement: .bottomBar) { Menu { Button("Action 1") { } Button("Action 2") { } } label: { Label("Actions", systemImage: "ellipsis.circle") } } DefaultToolbarItem(kind: .search, placement: .bottomBar) } } } } CONSOLE LOG Adding 'UIKitToolbar' as a subview of UIHostingController.view is not supported and may result in a broken view hierarchy. Add your view above UIHostingController.view in a common superview or insert it into your SwiftUI content in a UIViewRepresentable instead. Ignoring searchBarPlacementBarButtonItem because its vending navigation item does not match the view controller's. view controller: <_TtGC7SwiftUI32NavigationStackHostingControllerVS_7AnyView_: 0x106014c00>; vc's navigationItem = <UINavigationItem: 0x105530320> title='Toolbar Repro' style=navigator searchController=0x106131200 SearchBarHidesWhenScrolling-default; vending navigation item <UINavigationItem: 0x106db4270> style=navigator searchController=0x106131200 SearchBarHidesWhenScrolling-explicit Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. ( "<NSLayoutConstraint:0x600002171450 _TtC5UIKitP33_DDE14AA6B49FCAFC5A54255A118E1D8713ButtonWrapper:0x106a31fe0.width == _UIButtonBarButton:0x106dc4010.width (active)>", "<NSLayoutConstraint:0x6000021558b0 'IB_Leading_Leading' H:|-(8)-[_UIModernBarButton:0x106a38010] (active, names: '|':_UIButtonBarButton:0x106dc4010 )>", "<NSLayoutConstraint:0x600002170eb0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x106a38010]-(8)-| (active, names: '|':_UIButtonBarButton:0x106dc4010 )>", "<NSLayoutConstraint:0x60000210aa80 'UIView-Encapsulated-Layout-Width' _TtC5UIKitP33_DDE14AA6B49FCAFC5A54255A118E1D8713ButtonWrapper:0x106a31fe0.width == 0 (active)>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x600002170eb0 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x106a38010]-(8)-| (active, names: '|':_UIButtonBarButton:0x106dc4010 )> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful. Failed to send CA Event for app launch measurements for ca_event_type: 0 event_name: com.apple.app_launch_measurement.FirstFramePresentationMetric Failed to send CA Event for app launch measurements for ca_event_type: 1 event_name: com.apple.app_launch_measurement.ExtendedLaunchMetrics

Hi, My app (Team ID: H4DH43B9X7), despite the requested expedited review, has been stuck in “Waiting for Review” since Thursday. This occurred after the app had already been approved multiple times and then received an incorrect rejection referring to “gender,” whereas the app actually requests biological sex, clearly described in the UI as required for metabolic calculations (BMR/TDEE), which are core to its functionality. Since this is causing us financial problems, I would greatly appreciate an update on its review status as soon as possible.

Hi, I purchased the Apple Developer subscription yesterday and the payment has already been successfully processed. However, my account is still not showing as active. Given that the payment has been completed, I would expect the activation to be reflected by now. This delay is impacting my ability to proceed with development and deployment, so I need clarification on what is causing the issue. Please review my account status as soon as possible and let me know: • If there is any pending verification or required action on my end • The reason for the delay in activation • The expected timeframe for the subscription to become active I would appreciate a prompt resolution to this matter. Thank you.

Hi devs and Apple support team, I’m waiting for updates on two Apple Developer Support cases: 102870790200 102870755282 Both are related to changing my Apple Developer / App Store Connect region and entity information from UAE to Kazakhstan. The requests were submitted last Thursday (5 days ago), and I still haven’t received any update. This is currently blocking my app release. Has anyone dealt with a similar issue, and is this waiting time normal for this type of request? Thank you very much.

My enrolment is pending since 13 April and I haven't heard from Apple yet. I have requested for call backs and sent emails. How long does it generally take to get enrolled?

I have an app that has suddenly gotten a non-public API error after uploading the archive to TestFlight. The error is posted in full below, and has never occurred before. I'm not using the _UIDeviceOrientationDidChangeNotification symbol but I do have two extensions that use UIDevice.orientationDidChangeNotification. However those extensions are not included in the target for the two watch extensions where the error occurs. Has anyone seen this problem before or have some advice? 90338: Non-public API usage. The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/watchkitappExtensionBeta: _UIDeviceOrientationDidChangeNotification,The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/PlugIns/watchkitappWidgetExtensionBeta.appex/watchkitappWidgetExtensionBeta: _UIDeviceOrientationDidChangeNotification. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

I enrolled in the Apple Developer Program on April 13, 2026 (Order Number: W214****). Payment was completed and the invoice was issued, but my account has not been activated yet. It has now been 4 days. I have not received any activation email, nor any request for identity verification or additional information. Could anyone help? I am waiting to publish my app and this delay is blocking my progress.

As of this morning, I have been unable to reach the Mac App Store or Test Flight .

Hi everyone, I'm currently experiencing an issue when trying to submit my app/build via App Store Connect. Details: App name: Daily Habit Tracker 2026 Bundle ID: com.DailyHabitTrackerPro.2026 Case ID: 102871415765 Issue: Whenever I try to submit the build (TestFlight / App Review), I get the following error: "There was an error processing your request. Please try again later." This issue has persisted for several days. What I've tried: Retried submission multiple times Waited and tried again later Checked app metadata and settings Contacted Apple Developer Support on April 17, 2026 (no response yet) Question: Has anyone encountered this issue recently? Is this a known backend issue on Apple’s side, or is there anything else I should check? Thanks in advance.

Good morning. I have an APPLE DEVELOPER ACCOUNT. I am inquiring about Distributing In House Apps using my own website. All the links so far do not help. They all seem to be relevant to the Apple Store and not In House apps. I have my apps ready for evaluation. I understand you need to evaluate them. I want to apply for a certificate that will allow me to put the apps on my OWN website and have users download these and install to their Apple devices. So far I have been testing using own devices but every build I create does NOT create a manifest file. They do work but obviously I need a manifest for the website. I assume a relevant certificate would provide that. Can you please let me know of any and all information that applies on how to apply for an In House Distribution Certificate and how and where I should upload my apps for evaluation. Thank you so much. John

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.