“iPhone 16 pro”

I wish that was the case I can't see any phone number on the site I understand that some people can and others can't how do i get their number? I even called twice to the apple's global support and they couldn't refer me to the developers program group

i have called i am in the same boat and have sent emails too- no response...its crazy. we need an app to go live soon and cant even get it on after paying to. whats the number you have to call- when calling support they say they no longer have a team dedicated to phone service for developers

Same issue for me on M4 MacBook Pro

The other reply is correct that you can often ignore this warning, but I wanted to add some context since I have spent time debugging stride alignment issues with CoreML on ANE. The warning about unknown strides means that your model's hiddenStates tensor does not specify a memory layout that the E5ML compiler (the ANE backend) can optimize for. The ANE hardware has strict alignment requirements — specifically, the last axis of a tensor buffer needs to be aligned to 64 bytes (or 32 bytes on older chips). If your model runs correctly and produces accurate outputs, the warning is cosmetic — the runtime falls back to a compatible layout automatically. However, you may be leaving performance on the table. In my testing with speech models, fixing stride alignment reduced ANE inference latency by 15-25% because the hardware could use its native tiling strategy instead of the fallback path. When converting your model to CoreML (via coremltools), you can specify the output tensor's memory layout explicitly: import co

Thank you very much for your time. The issue is still unresolved. I tried using the Instruments memory tool and enabled malloc scribble, but unfortunately, the crash has not been reproduced yet. By the way, there is a crash on the iOS 26 system, and the crash stacks for iOS 26, 18, and 17 are the same as the ones I sent earlier. I noticed that on systems below iOS 17, the crash stack has changed to a different form, and the crash occurs in [AXSpeechThread main] (in libAXSpeechManager.dylib). I have attached the crashes for iOS 26 and iOS 16. Could you please provide guidance? iOS16-AXSpeechThread-Crash.txt iOS26-crash.txt

Wi-Fi, such as a smartphone hotspot, connects normally on the M5 Pro.

Thanks for the post. Unfortunately, there is no direct, programmatic way within the iOS SDK to automatically wake or launch your app specifically when the iPhone connects to CarPlay or a standard car Bluetooth system. Its important to mention your app is completely sandboxed from knowing anything about the CarPlay lifecycle. As a user, you can create a shortcut on your device. Open the Shortcuts app and go to the Automation tab. Tap + and select CarPlay or Bluetooth and select. The menu could be a little different. Set it to Connects and choose Run Immediately so it doesn't ask for permission every time like shortcuts do. For the action, they can select Open App and choose the app you want to run on the iOS device. Hope that give you an idea. I hope people do not provide you with ideas using Core Motion or Core Location to wake your app in the background when the user starts moving in a vehicle. It is advisable to avoid those options due to the potential issues they may cause. Albert
  Worldwide Dev

All apps should build with the latest SDK, so you have access to the latest APIs, regardless of the distribution mechanism used. Regarding the UIDesignRequiresCompatibility questions, it's useful to see how this was described in the WWDC25 Platforms State of the Union: As you evaluate your app's UI and the time you need to adopt the new design, we're providing an option to continue to use your app's current design with Xcode 26. We intend this option to be removed in the next major release. Hopefully you're on your way with the adoption of the new design already, or have upcoming plans to tackle it. You'll have to look at your own specific situations and determine how long you can continue using it for specific hot fix situations against the above statements and the timing of your own planned adoption of the new design. What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration chal