“iPhone 16 pro”

The one time we got Apple on the phone, we spoke to someone who said she was in charge of the testing team reviewing our app. The call was frustrating—she didn’t seem familiar with basic app testing for a location-based product (for example, how to emulate a different location) I don't know what 'emulating a different location' means, either. If it's not her own app that you are talking about, why does her unfamiliarity to your app make her incompetent? It is your responsibility, not hers, to explain how the app works. Right now we are averaging about a week at best to two weeks. What does that mean?

Same issue with Mac Studio M2 Max and MacBook Pro M4 Gave up on MacBook and reinstalled from recovery menu. Update then worked OK. About to do the same on Studio. No response from Apple to multiple feedback reports

@App Review Following up on your response from 2 days ago. Our app (Apple ID: 1505684382) has now been in Waiting for Review for 16 days — submitted March 4th. Despite your message that you would contact us via App Store Connect, we have received no communication there. To summarize what we have tried: 2x Expedited Review requests — no response 2x Support cases via Contact Us — no response This forum post — your team replied but no follow-through yet We have exhausted every available channel. Our app includes a time-sensitive subscription pricing test, and every day of delay is causing measurable revenue loss. We respectfully ask for a concrete answer: What is preventing our app from entering review, and when will it be reviewed? Thank you.

Albert Pascual -- I am unable to send a code-level support request because I no longer have a paid developer account. Without going into grim detail, since I could no longer type very well after the accident, I had to leave my career as a developer. It sucked. I had been doing backend development back when there was a Mac OS X Server and an ADC membership was $500 a year. But being disabled as I am gave me a lot more appreciation for accessibility in macOS. Having these things working is important to my quality of life. Last night I installed 26.4 RC and there are multiple new issues. At this point I'm going to have to reset to 26.0 because too much of what I rely on either doesn't work or has become too irritating. A few examples: the orange dot in the upper right corner somehow became more distracting as it is now an orange square with a black border. Still just as useless but now extra annoying. Now when I say Hey Siri and my computer is locked, Siri responds with You will need to unlock you device first

Thanks for the reply! I have also tested AVAudioSession with .playback + .mixWithOthers on watchOS. That works for mixing my metronome with Spotify while the metronome app is in the foreground, which matches the behavior I already see on iPhone. However, on watchOS the metronome stops once the app goes to the background, while longFormAudio keeps it alive but then conflicts with Spotify. So this seems to be a watchOS-specific limitation rather than a general AVAudioSession limitation on Apple platforms. It would be very useful if watchOS supported a way to combine background audio persistence (longFormAudio) with cooperative mixing behavior (mixWithOthers) for lightweight apps like metronomes, cues, or coaching audio. Is there any way I can formally request this feature other than the FB22273077 I have already submitted?

Hello, I don't have any information since one week from this forum. No phone call no email and always waiting for review.... HELP !!!

Definitely a hell of an experience in the worse way. Apple Watch Series 4 iPhone 11 Mac Neo I had 0 issues developing/deploying to Pixel WearOS, but obstacles after obstacles, developing for and deploying to Apple WatchOS. After several days of working around each obstacle with the help of Gemini, I'm adding the summary of what I had to do so far to get to initial deployment in case this helps Apple/others with fix/workarounds: Here is the complete technical post-mortem for the development environment setup. This summarizes the specific hurdles cleared to get a Watch Series 4 (watchOS 10.6.2) communicating with your Mac via a No-SIM iPhone bridge. 🛠️ Environment Recovery Summary The Networking Layer The primary blocker was extreme network instability on the default 10.0.0.x gateway. The Symptom: ping tests showed 62% packet loss and 1,000ms+ latency. The Fix: Migrated all devices to a clean 192.168.86.x subnet. The Result: Achieved 0% packet loss and ~13ms latency, providing the stable pipe