“iPhone 16 pro”

I’m facing a similar issue where my app has been stuck in the 'Waiting for Review' status for over a month now. During this period, I’ve contacted technical support twice and submitted an expedited review request. I even had a scheduled phone call with Apple support to discuss the app's status. During the call, they mentioned they would notify the review team to look into it, yet 3 days have passed since then with no update. It is quite frustrating to see some developers getting approval within 2-5 days while others, like myself, are stuck for a month or more. This delay is significantly impacting our launch roadmap. Apple advises against withdrawing and resubmitting to avoid losing our place in the queue, but it makes me wonder: how deep is this queue exactly? And why is there such a massive discrepancy in wait times between different developers? Has anyone else experienced a similar 'limbo' even after direct communication with Apple?

I had the same issue for about a week or so. I tried contacting apple support through the email option in the contact us page but there was no response from them. Then after a while I was able to request a call back from apple and only then did they ask me more details for verifying my identity and organization. I submitted the documents but then was again in the endless waiting loop. Then after a few days I had to request a call back from them again, told them I submitted all the documents and that's when I was able to proceed to making the payment for the program. You can find the phone/call option here Contact us. Although this call button keeps appearing and disappearing at very random times. So i'd suggest you to keep looking at it from time to time.

I Have the same issue. MacOS 26.3.1, Xcode 26.2, iOS 26.3.1 iPhone 17 Pro Max and WatchOS 26.3 Apple Watch S10.

I also have this issue in the Simulator with iOS26.2+iOS26.3.1, on what looks like all devices. It might happen for my phone as well if it was on iOS26.3.1, but I'm hesitant to upgrade it from iOS26.3 and have it break emoji entirely for who knows how long. Opening the emoji picker keyboard in the simulator now looks like this: Removing and re-adding the emoji picker from the list of keyboards does not appear to help. Nor does disabling Stickers, as someone recommended in another forum. I'm not sure what could be different about my setup (and those of the folks above) that makes the emoji break, when they aren't broken for most people. I'm located in the US, not Australia, so it's probably not that.

... key phases would be marked as inappropriate. I tried to stifle these using prompts and rules but couldn't get it to take hold. Thanks for sharing the specific phrases! We're continually working to improve our guardrails and reports like this are super helpful! Just in case this issue is blocking you, here are some key things to know: stifle these using prompts and rules often times this approach won't work, since the guardrails are a set of classifiers and systems that typically can't easily be persuaded. One prompting approve we've seen sometimes work, is starting your Instructions with a role that gives the model clear permission to act in a specific context. Something like You are an aviation assistant. Your job is to help the use with information about global airports and planes If you really get stuck with terms being wrongly-blocked, consider switching to a more lenient guardrail setting. The article section here explains the pros and cons of this approach and how to do it: https://develope

Thanks Kevin, I really didn't know what else to do about it. The external device works well on the iPad, but we wanted it to work the same way on the iPhone as well. Now everything makes sense, the iPad uses DriveKit, which is why doesn't work on the iPhone. I'll try to check with the people responsible for the device so we can test these alternatives. Thanks again

Thank you for your post. It is intriguing that you are considering restricting device installations. I would be more interested in understanding the specific reasons behind your desire to avoid iPad installations. Supported Destinations: iPhone / UIDeviceFamily: 1 : By itself, this does not prevent iPad installation. It simply tells the App Store: “this app is designed for iPhone. The App Store will still allow iPad users to download it, and it will run in compatibility mode (the letterboxed, zoomed-in iPhone screen on an iPad). However the UIRequiredDeviceCapabilities: telephony iPads (even cellular models) do not have the telephony capability (the ability to make standard cellular phone calls). By adding this to your Info.plist, you are telling the App Store that your app physically cannot function without a phone dialer. I believe that means the App Store will completely hide your app from iPads and iPod Touches. Then again, apps that run on an iPhone s

I also have same issue on the iphone 14, which I bought from my brother. Iphone 14 was reset and then i logged in with my apple account and when trying to do apple developer account enrolment, i get this error. I reached out to Apple support team and they simply say, that I cannot enrol using my apple account on this device. Is anyone aware of this issue and its resolution.