iPhone 16 pro

iPhone 17 (A19 Chips) do not require the fixed enablement of processor trace prior to boot. This means they do not require enabling a setting and just work.

I am able to sign in using my personal account, but not my account for app development. For some reason, it is no longer sending the codes to my phone, just my laptop, but every time I enter the code they have sent, it says it's wrong. Incredibly frustrating. I need to get my build out ASAP, and for the second day, it is once again timed out due to too many attempts.

Have you found a fix for this bug? I think that it's because iPhone go to deep sleep after some time when screen is locked and device is inactive. This bug happens on both iOS 18.7 and iOS 26.

Thanks. I got so focused on getting this added to the context menu I forgot about the “Paste and Match Style” item appearing in the Edit menu bar. Of course that only helps with the iPadOS 26 and Mac Catalyst versions of the app. For iPhones and for iPads on iPadOS before 26, my only option is to use the context menu. I guess I’ll stick with my buildMenuWithBuilder: approach.

Hello hah007, I have been in a similar starting point early this week, and everything went fine thanks to the Apple teams (the French ones) in about 48 hours, from the point where I had everything ready on my side. I would give the following advice: Slow down, double check your list of items. If you are just starting, there is a tremendous lot of things to learn to get in the Apple ecosystem. May be you did not get an answer because you asked in the wrong place ? As an example, you may have noticed you asked for help in the accessibility and inclusion forum, which is not about giving you access but about features intended for people with disabilities. ask for support directly, live on the phone. For me they called back in less than a minute, and were really helpful and empathetic. Try it here: https://developer.apple.com/contact/topic/select

I can confirm the behavior and want to add the developer perspective. I build an app that uses Apple’s on-device Foundation Models (with a Core ML fallback). When the device UI is set to Catalan, Apple Intelligence is disabled, so the Foundation Models APIs report unavailable. This blocks my app from handling prompts in English or Spanish even when the user explicitly selects those languages in-app. Developer impact • I must ship separate code paths and degrade features based on UI language, not user intent. • Users who prefer a Catalan UI lose on-device, privacy-preserving LLM features, so I am forced to route to cloud or third-party SDKs. • QA complexity rises because availability hinges on language toggles and reboots, as the bug report here illustrates. Repro (app context) 1. Set iPhone language to Catalan. 2. Call Foundation Models API from the app. availability reports not available. 3. Switch device language to Spanish. Availability often remains “unavailable” until reboot. 4. After reboot, av

Hi @rsingh05, Since you are not using automatic code signing, I do not have all of the information I need to begin investigating the underlying cause of the errors. Please follow the steps described in the post below and reply here with the Feedback ID: Gathering Required Information for Troubleshooting Tap to Pay on iPhone App https://developer.apple.com/forums/thread/775784 Cheers, Paris X Pinkney |  WWDR | DTS Engineer

We've finally found a way to bypass the iPhone's loading crash issue. We split the culprit CSS file into multiple files, leaving only the minimal CSS links needed to display the splash screen, and lazy-loaded the rest within the framework after the page's onLoad event. This allowed the pages to load without crashing, and it worked for all three sites mentioned in this article. However, this issue isn't resolved. It's simply unacceptable that a DOS-era 360KB memory limit exists in 2025. This issue still needs to be addressed, and until it is, it will remain a blemish on the iPhone. In that spirit, we'll keep the three separate sites mentioned in the reply above available for reproduction, and we'll await Apple's official response in this thread. If anyone reading this thread agrees with this, please give it a boost.