Apple Maps Guides

Hi @skitudeiosdevelopers, You wrote: [...] What is the correct and Apple-approved approach for handling age verification and restricting access for minor users on iOS versions prior to 26, given that the Declared Age Range API is not available on those systems? To enable all the technologies and access all the signals Apple has made available to comply with regional age assurance requirements, starting with Texas, you must build your app against, you must build your app against iOS 26.2 and iPadOS 26.2 SDKs with Xcode 26.2 (17C52). View the latest Xcode versions and SDKs here. Existing adult accounts and child accounts for kids and teens will not be affected. To learn more, see Next steps for apps distributed in Texas. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

What is not clear is what actually happens after that date. My understanding is that you will not be able to submit a new release, but they don't tell the app will be blocked. So I fear it is case B. That's how I interpreted, to be on the safe side. if you can't provide a new build yet In fact, there is no need to develop a new version. You can simply re-archive the former version of the app with incremented build and version numbers, complete age ratings information and then submit with this new build. In the what's new field of AppStoreConnect, simply say: minor bug fixes. Given the many times this question is raised on the forum and how much it worries developers, it would be great to have a comprehensive answer from Apple.

Thanks for the post and the details, the error is not about having the latest version of Xcode, looks like you do have it as Xcode Version 26.2 (17C52). The error message you're encountering, ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing., indicates that your app submission to App Store Connect is missing a required folder named SwiftSupport. So this is extremely interesting to me for sure. When archiving your app, ensure there are no build warnings about folders. Go to > , and then check the Organizer to ensure everything is correctly packaged. If your app uses Swift Package Manager, ensure that all packages are updated and correctly integrated. Sometimes issues arise from improperly configured packages? I believe this issue is always about packages you are using. Can you check that? read until the end where a post from an Apple engineer will give you more information. If you're manually managing your app bundle, ensure the folder is present in the archive's structure. It

Thank you Justin. There's one more quirk I've observed - Apple doesn't expose the analog proximity sensors on the trigger or grip buttons. These are the sense part of Sony's Playstation VR Sense Controller branding ;) In OpenXR / SteamVR with the Playstation VR2 these paths as independent triggers i.e. /user/hand/right/input/r1_sensor, /user/hand/right/input/r2_sensor, /user/hand/right/input/l1_sensor, /user/hand/right/input/l2_sensor, corresponding to the grips & triggers. Yes, this means the l2/r2 triggers have TWO analog capabilities - one for the analog relative touch/proximity, and one for the analog degree of trigger pull (which can be accessed via the .value on the button). Since this is an entirely new thing, should I update my existing feedback or file a new one?

You might be better off contacting Apple directly rather than posting on the forums if this happens again. No one on the forums can fix this, unless an Apple employee comes across your post and investigates it - and they don't investigate everything. If you're paying Apple for the service and the service isn't working, there must be some contact details you can use?

Thanks for asking @darkpaw, as you can see in the original thread, it fixed itself after talking to an Apple Engineer, but it takes time. And during this time, people complain and demand refunds...

I have also feedback using apple FeedbackAssistant system. FB21353175 (iOS26 Live Activity always display in Dark Mode)

Is there an Apple employee who can help us with this issue? Our business bank account is with UBS Switzerland and has been registered in App Store Connect for over five years. All payouts have worked without any issues during this time. App Store Connect has now suddenly marked the account as invalid, even though nothing has changed and the account is fully functional. A payout from Google Play was credited to this account today. We temporarily added a private account, removed the UBS account, and then added it again. However, the error message in App Store Connect remains unchanged. We need payouts to continue going to this account, as our accounting and business processes depend on it. Other business accounts exist but are used for different purposes. The error message refers to an incorrect “routing number”. However, when adding a Swiss bank account, there is no routing number field. Instead, a bank clearing number is required. We selected this number using App Store Connect’s search, and it match

Deedback Assistant ID: FB21352672 (Apple Pay In-App Provisioning – Apple server failure when adding a card)