Search results for

“Apple Maps Guides”

155,927 results found

Post

Replies

Boosts

Views

Activity

Reply to Don't automatically sign out when closing browser

[quote='821926021, matthewruzzi, /thread/821926, /profile/matthewruzzi'] FB22441056 [/quote] Thanks for that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Developer Tools & Services Developer Forums

Reply to First-time notarization submissions stuck "In Progress" for 20+ hours

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Code Signing Notarization

Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile

This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this. AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test: Using the same Xcode, create a new project from the iOS > App template. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B). In Signing & Capabilities, make sure automatic code signing is enabled for all configurations. And that the correct team is selected. At the top, make sure that you have a test device selected as the run destination. Then add the Contactless Pass Provisioning (SharableCredential) capability. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish. Assuming that works, try running the app on a test device. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

Developer Tools & Services Xcode

Reply to I would like to know if AWS ALB StickySession Cookies can be used on an iphone

Are you working on an iOS app that talks to your server? Or are you expecting users to access it via Safari? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App & System Services Networking

Reply to Account pending

I paid for the developer program 10 days ago, I received the invoice and everything, but the product does not appear in my developer account. I contacted support after 2 days but did not receive a response. After 7 days I received a response saying we are sorry, our system did not process the payment and I received a refund from them (without my consent) so I could try again. On the 2nd attempt I still did not receive the product, now I am waiting for support to respond and I do not know when I will have access to the product. A bad experience and a lot of unprofessionalism from Apple.

Community Apple Developers

Reply to Using mTLS with YubiKey via USB-C and PIV

[quote='821896021, RobJones, /thread/821896, /profile/RobJones'] I've also created a CTK extension [/quote] So, yeah, you don’t want to go down that path. Because the YubiKey presents a PIV interface over USB, it will be picked up by the built-in PIV support, so you don’t need to mess around with a CTK app extension. And this also means that you’re correct that you don’t need to install Yubico Authenticator. As to what you should be doing, I recommend that you break this up into two steps: Find and then use the key, just to make sure it’s working. Then try to pass the corresponding digital identity to URLSession for mTLS. For step 1, see my advice in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Privacy & Security General

Auto-renewable subscriptions stuck in "Developer Action Needed" - Cannot attach to binary

Hi everyone, I am trying to submit the first version of my app with auto-renewable subscriptions, but I am stuck in a loop. Both of my subscriptions (Yearly and Monthly) are stuck with the status Developer Action Needed. Because of this status, they do not appear in the list of available In-App Purchases when I try to attach them to my app binary on the App Store Connect submission page. Here is what I have already done/checked: All metadata is filled out (Display Name, Description, Pricing). Review Information is complete (Screenshot and Review Notes are provided). My Paid Applications agreement in the Agreements, Tax, and Banking section is Active. I contacted Apple Developer Support by phone, but they were unable to resolve the issue and suggested I post here for help. Has anyone experienced this limbo before? How can I trigger the status to change to Ready to Submit so I can finally attach them to my build and send the app for review? (I have attached screenshots of my App Store Connect dashboard

App Store Distribution & Marketing App Store Connect Subscriptions App Store Connect In-App Purchase

314

Reply to Screen Time APIs showing severe inconsistencies (DeviceActivity not firing + impossible usage data)

[quote='882176022, hkbm215, /thread/819997?answerId=882176022#882176022, /profile/hkbm215'] Any OS-version-specific observations would be really helpful. Thanks in advance! [/quote] Hey @hkbm215! My radar regarding this one specific issue FB18061981 has just been updated by Apple (No. 3 from my list above): Apparently this regression has been addressed in iOS 26.5 beta 1! The bug has been present in iOS 26.0 (during the whole beta phase since June 2025), iOS 26.1, iOS 26.2, iOS 26.3, and iOS 26.4. I am currently not able to reproduce on my device…but I’m not yet closing my bug report. This issue is not consistently reproducible, sometimes it goes away for a couple of days or weeks…just to come back and hit even harder the next time. So we have reason to be careful optimistic! However, the other issues of my list still remain. But I think it’s good news that after half a decade of silence Apple is starting to put some engineering efforts into the Screen Time frameworks again!

App & System Services General

Screen Time APIs showing severe inconsistencies (DeviceActivity not firing + impossible usage data)

Hi everyone, I’m the developer of one sec, an app used by a large number of users globally to reduce time spent on social media and to build healthier digital habits. Because of this, we rely heavily on Apple’s Screen Time / DeviceActivity / FamilyControls, ManagedSettings APIs – and unfortunately, we’re seeing increasingly severe issues in production that directly impact hundreds of thousands of real iOS users. During the past years, we have been busy filing dozens of feedback requests for different Screen Time issues – and there has been no response from Apple at all. Developer Relations might be able to confirm that the bugs are present and that they ended up with the right team – but they are never addressed, neither are workarounds provided. Instead, the situation gets worse and worse. iOS 26 introduced a series of heavy regressions (which have been reported via Apple’s official bug report tool Feedback Assistant on iOS 26 beta 1 in June 2025 – and have not been addressed 10 Mo

App & System Services General Family Controls Device Activity Managed Settings Screen Time

506

Reply to iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

[quote='882166022, kgaidis, /thread/809410?answerId=882166022#882166022, /profile/kgaidis'] that's iOS 26.2, iOS 26.3 and iOS 26.4 (3-4 months) of limits automatically activating most mornings without reaching the limit, and this also affects the default Apple Screen Time [/quote] Just for the record: it’s been one year almost. The regression was introduced with iOS 26.0 beta 1 in June 2025. I filed a radar about this serious regression the very same week…but did not get any response from Apple until now. Apparently now in iOS 26.5 it’s addressed, but that still takes a month or so to ship to customers. So 11 months in total to have the bug fix shipped that shouldn't have made it into the public release of iOS 26 at all. I hope some internal investigation will follow at Apple to prevent a horrible scenario like this from happening again!

App & System Services General

iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

Hi there, Starting with iOS 26.2 RC, all my DeviceActivityMonitor.eventDidReachThreshold get activated immediately as I pick up my iPhone for the first time, two nights in a row. Feedback: FB21267341 There's always a chance something odd is happening to my device in particular (although I can't recall making any changes here and the debug logs point to the issue), but just getting this out there ASAP in case others are seeing this (or haven't tried!), and it's critical as this is the RC. DeviceActivityMonitor.eventDidReachThreshold issues also mentioned here: https://developer.apple.com/forums/thread/793747; but I believe they are different and were potentially fixed in iOS 26.1, but it points to this part of the technology having issues and maybe someone from Apple has been tweaking it.

App & System Services General Family Controls Device Activity Managed Settings Screen Time

3.4k

Reply to iOS 26.2 RC DeviceActivityMonitor.eventDidReachThreshold regression?

[quote='883582022, kgaidis, /thread/809410?answerId=883582022#883582022, /profile/kgaidis'] How are people doing on iOS 26.5? So far so good, but this happened with the first 26.4 release too: it seemed to be fixed, but then (maybe) something got reverted. [/quote] Same: so far so good. But I’m hesitant to confirm the bug fix haha. As we all know the Screen Time frameworks are quite flaky and bugs come back all the time after a couple of weeks. Or even worse: new regressions. This time I’m hopeful though because my radar FB18061981 has been updated by Apple indicating that there has been a bug fix attempt for iOS 26.5 beta 1. So all in all, I think we can be carefully optimistic that this issue has been addressed on 26.5 🤞

App & System Services General

Developer enrollment is still pending after 4 days of payment

I created my Apple developer account and made the payment on Saturday, April 4th. Apple sent me a receipt via email and confirmed the payment. I need to start optimizing my app for the App Store as soon as possible, but Apple still hasn't approved my developer account. I created a support ticket but received no response. I tried to reach them by phone, and after waiting for minutes, I finally got through to an authorized person, but they were unhelpful and just told me to wait. Why is this process so difficult and uncertain?

App Store Distribution & Marketing General Developer Program

Reply to Xcode now hangs; SDKs are "status unavailable"

Ok, here is my step by step (what I think is) a solution guide... (worked for me) Fix: Xcode Hangs on macOS Tahoe 26.4 (SDKs Status Unavailable) The Problem macOS Tahoe 26.4 introduces a bug where a CoreSimulator subprocess (simdiskimaged) repeatedly exceeds its 20MB memory limit and gets killed by the system. This causes CoreSimulatorService to hang indefinitely, which in turn causes Xcode to freeze, SDKs to show status unavailable, and all simulators to become inaccessible. The root cause is a runaway loop that creates new SimRuntimeBundle files every 11 seconds in /Library/Developer/CoreSimulator/Cryptex/Images/mnt/, bloating the state that simdiskimaged must load on startup beyond its jetsam memory limit. The Fix Step 1 — Grant Terminal Full Disk Access The files that need to be deleted are protected by TCC (Transparency, Consent, and Control). Without this step, sudo rm will return Operation not permitted. Open System Settings → Privacy & Security → Full Disk Access Click the + button Add Te

Developer Tools & Services Xcode

Reply to Universal Links: Apple CDN returns SWCERR00301 Timeout for specific domains while others on same server work fine

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.

App & System Services General