“Apple Maps Guides”

Hey @THeberlein, This is unexpected behavior. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report; please include a link to your webpage and a sysdiagnose from your Vision Pro captured after this occurred, and post the FB number here once you do. Instructions on capturing a visionOS Sysdiagnose can be found on the Profiles and Logs webpage. Bug Reporting: How and Why? has tips on creating your bug report. Thanks for your help, Michael

Thanks for the post, interesting that's something in the process. TN3168: Making your App Clip available in the App Store | Apple Developer Documentation https://developer.apple.com/forums/thread/804858 There is something I always like to check when deploying AASA files. When the full app is installed, iOS handles the URL invocation locally via your apple-app-site-association (AASA) file and entitlements, bypassing the need to query Apple's App Clip CDN. The fact that this works proves your code, AASA file, and associated domains are configured correctly. The failure for fresh devices is happening because Apple's CDN has not yet been updated with your App Clip's metadata? Can you provide me a link to your AASA file in your server so we can see why is not syncing into the Apple servers? Is your server preventing or blocking IP address or user agents from requesting the AASA file? Sometimes, the job queue in App Store Connect simply drops the task. You can often forc

Dear Apple Entitlements Team, My app FocusPact (Bundle ID: com.hayashikento.FocusPact) has already been approved for the Family Controls (Distribution) entitlement. To resolve a critical bug where restricted apps remain unlocked after the user's Pact period ends, I have implemented a DeviceActivityMonitorExtension. This extension is essential for the app's core functionality to re-enable shields automatically. Could you please authorize the following new Bundle ID for the same Family Controls (Distribution) entitlement? New Extension ID: com.hayashikento.FocusPact.FocusPActMonitor Parent App ID: com.hayashikento.FocusPact Thank you for your continued support in helping me complete my MVP. Sincerely, Kent Hayashi

Our IAPs are stuck on In Review and Waiting for Review Waiting for Review: You have submitted your In-App Purchase to be reviewed by Apple. You can make edits to the product while it is in this status. In Review: Your In-App Purchase product is currently being reviewed by Apple. Only edits to the product’s reference name, pricing, and availability can be made when it has this status. This creates a deadlock because we cannot attach them since the section does not show, and the section does not show because they are not Ready to Submit. There is no need since you already submitted them for review. When submitting an In-App Purchase or subscription for the first time, you must submit it with a new app version. If there are multiple In-App Purchases or subscriptions related to that version, submit all of them together. Once App Review approves one or more In-App Purchases or subscriptions for your app, you can submit more In-App Purchases or subscriptions without a new app version. For more inf

@h2oconsulting I can't test it in the sandbox, since the application is not approved. Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review. For more information, see TN3186: Troubleshooting In-App Purchases availability in the sandbox. When submitting an In-App Purchase or subscription for the first time, you must submit it with a new app version. If there are multiple In-App Purchases or subscriptions related to that version, submit all of them together. Once App Review approves one or more In-App Purchases or subscriptions for your app, you can submit more In-App Purchases or subscriptions without a new app version. For more information about submitting In-App Purchases, see Submit an In-App Purchase. After submitting your In-App Purchases to App Review, they might also be missing or unresponsive during review. The sandbox environment is a test environment for testing the In-App Purchase implementation in your app with real product dat

If there is a better way than checking whether the URL contains “.Trash” to determine whether a file was deleted while the app was not running—like the method used by Numbers.app—we would like to adopt it in our app as well. Yes, this is basically what Numbers is doing. If the approach used by Numbers.app relies on Apple private APIs, we understand that it would not be available to third-party developers, and in that case, we will proceed with the “.Trash” URL check approach. There definitely isn't any special private API that numbers is calling that just handles this case. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

a long review process with many resubmissions The word 'many' doesn't convey the exact number to others. Can repeated resubmissions / iterative changes alone be interpreted as “evasion” under 3.2(f)? It depends on what you have done, and nobody but people from Apple, Inc. knows it. You have been told that you have some questionable, overly sexual content. Suppose that that you have covered a sexually-revealing person with a see-through material. You've been warned 5 times. And each time you increase its opacity from 10% to 11%, 12%, 13%... If you do it many times without entirely getting rid of this person, I would definitely flag it for evasion.

Details regarding how security issues are handled are available on the Apple security releases page.

I do hope someone at Apple is still paying attention to this. I haven't seen any updates on the bug reports I filed, and no one has reached out to me directly. I will just add that none of the issues I've reported have been fixed in the build of 26.4 (25E246) that released to the public this week.

Well I figured it out - for anyone still encountering this issue: My company has one domain to service multiple locations/storefronts. Each location has it's own separate Payment Processing account, requiring a unique Apple Pay Payment Processing Certificate/MerchantID. The docs and responses here made me think subdomains would be required, which is a headache in itself - especially since the Apple Pay Session must be started from that subdomain (not the parent domain). SOLUTION: If you register multiple MerchantIds within a single Apple Developer Identifier - all Domain Association Files tied to a certain domain are the same. So if you verify for one MerchantID, then add that same domain to another - it will count it as already verified. No need for subdomains. No need for swapping out Domain Association files. Really wish that Apple had made that clear.