“Apple Maps Guides”

Thank you for your post. Looks like you do not want to provide the URL to your AASA file. If you want to move this conversation privately for privacy. I'd like you to submit a code-level support request so we can discuss this further privately. When you create the request, indicate that you were referred by me at Apple and make sure to include a link to this thread. Before that, I would also recommend you to go over this great written Tech Note that goes over all the steps to troubleshoot Universal Links: TN3155: Debugging universal links | Apple Developer Documentation Most developers found this tech note a solution to their configuration. Including to answer your 2 questions at the end that seems like you are blocking the user agent or the IP address from Apple, as well as there is no way to invalidate the cache, you can always change the AASA file to change the cache. There is no public-facing API or portal to manually flush or invalidate the AASA CDN cache for a specific domain.

You're the best, Apple. Thank you. Hopefully see you there. https://developer.apple.com/events/view/8D4G7DD8LR/

Thanks for the post. I'm not an expert on audio and less when that involves watchOS. So other watchOS engineers are hopefully jumping into the thread soon. What I know is the behavior you are seeing is due to the strict differences in how watchOS handles background execution and audio compared to iOS. When your app goes into the background on watchOS, custom audio playback like AVAudioPlayer or AVAudioEngine playing a voice or beep is immediately suspended unless specific background modes and sessions are active. The reason the ping sound and haptics continue is likely because you are triggering them via WKInterfaceDevice.current().play(.notification) or similar system-level calls, which are handled by a separate system and can fire as long as your app has any background execution time. Since you want your app to play over music apps without stopping them, you must configure your AVAudioSession to mix with other audio. You should also consider using https://developer.apple.com/documentation/avfaudio/avaudiose

Scenekit works on Apple watch, will RealityKit?

[quote='883510022, ohadh123, /thread/808470?answerId=883510022#883510022, /profile/ohadh123'] Wondering if you got any resolution on this? [/quote] Hey @ohadh123! This might be fixed on iOS 26.5 beta 1, but we are still waiting for confirmation from Apple. Since this bug is not consistently reproducible, I don’t want to be too quick to give green light here :)

Thank you for your response. Upon reviewing the errors, this should not occur. However, there may be more experienced Apple Watch engineers who have identified this error and can provide a solution. For my understanding an HTTP 400 (Bad Request) means the network request Xcode made to the servers was rejected. If your developer account session has expired in Xcode's settings, the request to download the symbols might be sent with an invalid authentication token, resulting in a 400 error. Open Xcode and go to Xcode > Settings > Accounts. Select your Apple ID on the left. Click the - (minus) button at the bottom to remove it. Click the + (plus) button and sign back in. Restart Xcode and see if it successfully fetches the symbols. If you are using a VPN a corporate proxy, or custom DNS/firewall software, it might be intercepting and modifying Xcode's network request to Apple's servers, causing Apple to reject it as a Bad Request. Let me know if you get past the 400 error

Hi, as of now I am facing the same problem. I submitted 50 days ago and it went In review after 4 days but stayed In review for 3 weeks (without anyone loggin in to the app). Thinking something is broken I resubmited the app which is the worst thing I could have done. Now the app can not enter the priority queue (expedited review) and although Apple support and Apple emplyee on forums told me just to wait I am almost sure that the app will never be reviewed. I own a small company and have lost 2 000 users and there is nothing you can do, because if you try to submit it again they will decline it as duplicate. Not even another apple developer account helps. I got a sugesstion to change the whole app UI, colors and name and that then it might be reviewed. Sorry to disappoint you but that is how it went for me.

I’m still working on this. It’s proving to be challenging, not helped by the fact that WWDC is looming large on everyone’s calendar. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

applepayentitlements @apple.com just looked at the apple demo page and not documentation provided by token provider.