Overview

Hey, I've been banging my head against this for a few days now and genuinely can't figure out if it's something on my end or an Apple backend issue. My app has WeatherKit integrated and it works fine in the simulator, but on my physical device I consistently get this in the console: Failed to generate jwt token for: com.apple.weatherkit.authservice Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Things I've already tried and ruled out: WeatherKit capability is enabled in the App ID on developer.apple.com ✓ com.apple.developer.weatherkit = true is in the entitlements file ✓ Removed and re-added the capability in Xcode Signing & Capabilities ✓ Clean Build Folder, fresh install on device ✓ The location coordinates are valid (hardcoded lat/lon in Bavaria) ✓ The weird part is that it's not a location issue — Error Code 2 from WDSJWTAuthenticatorServiceListener suggests the JWT generation itself is failing before any location lookup even happens. I've had this App ID since early this year, WeatherKit was working at some point, and I'm not sure what changed. My fallback to Open-Meteo works fine so the app isn't broken, but I'd like to actually use the API I'm paying for. I also opened a support ticket but got redirected to the forums, so here I am. Anyone else seen this recently or know if there's something on the provisioning side I'm missing?

I’ve been using the Age Assurance support page and related Developer News posts as the source of truth for understanding Apple’s expectations around Age Assurance on Apple platforms: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/news/?id=sg176nne Can anyone from Apple clarify whether anything has recently changed with App Review expectations related to Age Assurance? Specifically, are there any new requirements or updated guidance around implementing technologies like DeclaredAgeRange or PermissionKit? I didn’t see any sessions or announcements that indicated these frameworks are now required but with all of the new child safety announcements I thought I'd ask and document for the developer community. I did see the new sample code for implementing Age Assurance and permissions, but nothing suggesting their use is mandatory for App Store approval. https://developer.apple.com/documentation/declaredagerange/implementing-age-assurance-and-permissions Just trying to confirm whether current guidance remains the same, or if App Review expectations are evolving.

https://developer.apple.com/documentation/declaredagerange/ https://developer.apple.com/documentation/declaredagerange/agerangeservice/requiredregulatoryfeatures For these API, (1) How is Apple determining the user is in Texas? IP or Address on the account? (2) How do we know if an API is active. Testing today (6/18) we are seeing both false in a region/state where the law is now in effect. (3) How will we know when Apple adds more regions to the API enablement? Is there a communication channel for this?

I'm trying to notarize a macOS app. Every time, I get an error: "Team is not yet configured for notarization". This has been an issue for a few weeks now. I've contacted Developer support (https://developer.apple.com/support/) repeatedly. I've been asked to provide personal information and to upload a government ID. Did everything, nobody got back to me. This is very distressing - we've had this issue in total for almost a month, are about to deploy our app to real customers, and this is completely blocking. Not sure what to do here. Apple is blocking us completely and is not responding.

This is our second App Store submission for Rex, a social entertainment discovery app whose core features depend on account-based personalization, saved history, and social/group functionality. Rex’s core features include Rex AI, which provides personalized movie and TV recommendations, along with social watchlists and Party Mode for group recommendations. These features do not function in any meaningful way without an account because they rely on user preferences, saved history, social connections, and persistent recommendation data to deliver the intended experience. Our app is being rejected under Guideline 5.1.1(v), even though account-based functionality is central to the premise of the product. Sign-in is not being used as a gate in front of otherwise accessible content. It is required because the product itself depends on an account-based experience. We have now received the same generic rejection message twice, with no indication that our previous responses were reviewed or considered. We submitted detailed explanations of how Rex works and why sign-in is foundational to the experience, but those points have not been acknowledged or addressed. The responses we have received do not engage with the specific nature of our app, do not address the 5.1.1(v) exception for apps whose core functionality is account-dependent, and appear to repeat the same form language without responding to the context we provided. This is a significant investment of time and resources, and we are trying to understand what Apple is specifically asking us to change. We are not trying to gate free content behind a login. We are trying to ship a product that, by design, requires an account for its core functionality to work. Can someone from Apple or the developer community help clarify how Guideline 5.1.1(v) should be applied to apps where personalization, social features, saved history, and group recommendations are the core product experience?

Hello everyone, I am dealing with an unresolved payout issue and hoping someone here has experienced something similar or that an Apple representative can help. Here is the situation: My April 2026 earnings ($563.73) were sent on June 5, 2026 to my previously registered Wells Fargo account. However, that account had been deactivated by my payment provider (Raenest) on May 30, 2026. I had already updated my banking details in App Store Connect on June 3, 2026 — before the payment was sent. Raenest has since confirmed in writing that: The payment was rejected and returned to the sender (Apple) The old Wells Fargo account is no longer active I should contact Apple to arrange reissuance to my new account I have been following up with Apple Support since early June with no response. My open case is: Payments and Financial Reports (Team ID: 686F6BLM3U); Case-ID: 20507794 My next payout is July 2, 2026 and I am urgently trying to confirm whether the returned funds will be included in that cycle. If any Apple representative or developer who has been through this can advise on next steps or escalation paths, I would really appreciate it. Thank you.

Is anyone else finding model switching a bit disruptive during longer coding sessions? As we start using different models for exploration, implementation and review, having to go through settings interrupts the workflow. I would love to see model and reasoning controls directly inside the Coding Assistant UI.

My app runs as expected when debugging, trigging the MacOS to ask the user for permission to use the microphone. The notarized version of the app does not have the MacOS asking for user permission but the app gets the message 'User rejected permission'. I'm seeing this after upgrading to 26.5.1 and so is one of my users. What changed in getting microphone permission?

I develop a tool on macOS which is composed of an UI app to manage the main app settings, and an Agent that runs in background doing some tasks ? (Running the agent is optional, can be launched from the UI app, and can be launched by macOS at startup with SMAppService. ) Agent has the LSUIElement flag set, and only shows a Menu Extra (or whatever it now named), and sometimes some notifications. The whole App package is bundled this way MainAppUI.app/Contents/Library/LoginItems/AppAgent.app (for SMAppService to work) This has been working correctly for years Now on macOS 27 beta, once I quit the UI App, having launched the Agent, the Dock reports the UI App is still running in background (with the grey dot) . But only the Agent is running, not the UI app process. Moreover, System Settings->Background apps reports both the UI app AND the Agent as both requesting to run in background. I would have expected only the Agent being listed in System Settings, and nothing appearing in the Dock. Is this a bug in the OS beta , showing the top-level container bundle as the app running in background instead of the executable direct container ? Or maybe it's on me and I should bundle my app differently ? (I cannot "reverse" the bundle and put the Agent as the main app, with UI "inside", as double clicking the main app should launch the UI App , not the Agent. ) BTW, filed FB23203848 for the same subject. thanks for any direction

Hello Apple Developer Support, We are using ILMessageFilterExtension with the IdentityLookup framework to classify carrier messages. We have already verified that the Message Filter extension is invoked for RCS messages. Our remaining question is specifically about end-to-end encrypted RCS messages on iOS 26.5. Could Apple please clarify the expected behavior for RCS E2EE messages? When an RCS conversation is end-to-end encrypted, is ILMessageFilterExtension expected to receive an ILMessageFilterQueryRequest callback? If the extension is invoked for RCS E2EE, does ILMessageFilterQueryRequest.messageBody contain the decrypted message body locally on device? If the extension is not invoked for RCS E2EE, is this expected behavior because the message content is end-to-end encrypted? Is the behavior different based on carrier, region, or RCS encryption availability? Is there any public Apple documentation that explicitly describes IdentityLookup / Message Filter behavior for RCS E2EE messages? Environment: iOS version: 26.5 Framework: IdentityLookup Extension: ILMessageFilterExtension API: ILMessageFilterQueryHandling.handle(_:context:completion:) Confirmed behavior: Message Filter extension is invoked for RCS messages Question: Whether the same behavior applies to end-to-end encrypted RCS messages We need this clarification to finalize expected product behavior and test coverage for RCS E2EE message filtering.

Hello, I enrolled in the Apple Developer Program as an individual on June 8, 2026. The USD 99 payment was successfully charged to my credit card, and I received an Apple invoice receipt. However, my Apple Developer account is still showing “Pending” and continues to display the “Purchase your membership” / “Complete your purchase” message, as if the payment had not been applied. I have not received a membership confirmation email, any request for additional documents, or any identity verification instructions. I already contacted Apple Developer Support but have not received a response yet. I have not attempted to purchase the membership again because I want to avoid a duplicate charge. Could an Apple representative please advise whether the payment needs to be manually linked to my enrollment, or whether there is any additional verification required? I can provide my Enrollment ID, order details, and invoice information privately through the official support channel if needed. Thank you.

I had planned on using the new version of Reality Composer Pro to export USDZ files for interactivity, but I noticed it can only export selected objects, and they export to a new '.reality' file type. I can't open these on MacOS26.6 or MacOS27. On the old version of Reality Composer Pro you could export the entire project as a USZ file, which was really cool since it was kind of universal and maintained many of the interactions. is this something that just hasn't been integrated yet?

I contacted developer support 3 days agovia email and they are sharing any response regarding removal of an app that I stoped publishing two years ago. And no advisor is lifting call I kept on listening to music for nearly an hour twice and anoth half an hour the third time I tried to call developer support team.

Environment: iOS 26; iPad Mini/Air/Pro Problem: In a TextField, I am using a keyboard with the type .decimalPad. When I initially tap into the TextField, the "popover" keyboard (i.e. the decimalPad) shows up and focusses the TextField. However, when I click outside the TextField (to dismiss the keyboard), the TextField is still focussed (the keyboard was dismissed though). When reentering in the TextField, another keyboard (from the bottom of the screen) appears (most likely .numeric). Does anybody know how to solve this? What I already tried: I tried listening to the dismissal of the keyboard to manually set the FocusState to nil. However, the dismissal of the "popover/decimal" keyboard is not recognized as such a dismissal. I also tried to build a custom component out of that, but then I lose the TextField behavior, conflicting with HIG.

I'm the developer of Spivot, a golf launch monitor app available on the App Store. When users search for "Spivot" directly, the App Store treats it as a misspelling and returns "Showing results for 'spigot'" with a prompt asking if they'd like to search for "Spivot" instead. This is causing issues with users being able to locate the app. The app name is intentional and trademarked — Spivot is not a misspelling of spigot. Because it's a coined brand name not in Apple's dictionary, the search algorithm is incorrectly flagging it as an error and redirecting users before they ever see the app. This creates significant friction and likely causes user drop-off for anyone who doesn't notice the small "search for Spivot instead" prompt. This appears to be a broader issue — I've seen at least one other developer report the same behavior with a unique app name (MathAppy, Jan '25). Questions: Is there any way as a developer to flag a brand name so the App Store search won't autocorrect it? Is this something that can be escalated to the App Store search team? Has anyone else run into this and found a workaround? I've already ensured the app name appears in both the title and subtitle fields in App Store Connect. Happy to provide any additional info. Thanks in advance.

Im trying to implement add to Apple Pay feature in my app. I have an issuer bank's credit card as an existing feature. Now question is, say its added successfully already, I relaunch my app, how to tell if already added to Apple Pay? I have made some reads, and asked AIs, but I can't seem to get a clear answer. Passkit's primaryAccountIdentifier - if use this, how will our backend store this? I mean, I don't think its ideal approach for mobile app to be responsible for calling backend api. deviceAccountNumberSuffix - what if my app have other cards that can be added to Apple Pay and has same suffix. Then seems broken flow.

https://support.apple.com/en-us/126655 As stated in the “Prepare your network environment for stricter security requirements.” my understanding is that additional security requirements will be introduced from OS 27 onward and that we need to prepare for them. However, I understand that the content on this page is mainly about distributing apps and operating the app itself. For example, I believe that simply accessing a web page within the app, or conducting HTTP communications with servers unaffiliated with Apple, will remain possible as before. Is my understanding correct?

Hi everyone, App Name: StAIle Build: 6 (Version 1.0.0) I submitted this build for TestFlight external testing on June 12, 2026. It has been stuck in "Waiting for Review" status ever since (6+ days now), well beyond the typical 24-48 hour window. What I've tried so far: Sent an email to App Store Connect support — no response after 2+ days Submitted an expedited review request via the official form — still waiting on that too No message in the Resolution Center, no compliance flag I'm a solo developer trying to run external beta tests before submitting the app for full App Store review, and this delay is blocking that step entirely. Has anyone else experienced something similar recently, or found a way to get this moving? Any advice appreciated. Thanks!

What is wrong with you people man I've been bashing my head for two days it just won't work, I'm trying build a React Native app but unable to connect my phone to my macbook local server I have stopped development it's taking out all the enthusiasm out of it. I'm on the edge, everything work when it's xcode building, installing the app but the moment I switch to React Native(Antigravity) it just wont connect, sometime it connects randomly and then is suddenly stops, should I drop everything and just use apple for everything? Why wont you just ban app development outside xcode completely?

Hi everyone! I'm writing a watch app using backgroud refresh. But the backround task was not triggered either on simulator or real watch device. main code