It would be really helpful to know which iOS major versions are security supported by Apple. As developers, we use this information to determine how many hours, we put into backwards compatibility. As owners of iPhones, we use this information to determine when we need to upgrade. And to valuate used iPhones. Sites such as https://endoflife.date/ios and https://en.wikipedia.org/wiki/IOS_version_history#Overview are used a lot in giving an overview of support. I have tried to argue that Apple still supports iOS 26, 18, 16, 15 and 12 https://github.com/endoflife-date/endoflife.date/issues/9852#issuecomment-4312532484, but it is hard, when Apple does not publish any such statement. Please consider publicly documenting which iOS versions are supported. It does not necessarily have to set a future date for how long they will be supported. I am aware of the pages https://developer.apple.com/news/releases/ and https://support.apple.com/en-us/100100, but these are just presented as lists of previous releases, with no statement that the versions are considered supported by Apple. As BiNZGi wrote on https://github.com/endoflife-date/endoflife.date/issues/9852#issuecomment-4413680961 Hm, that is an interessting link, but unfortunately it does not state about support status or dates. I checked previous versions of the page in web archive and on 9th jan version they only have iOS 26 & 18: https://web.archive.org/web/20260109033359/https://developer.apple.com/news/releases/ I would be very helpful, if that page https://developer.apple.com/news/releases/ would have a headline saying supported releases, or similar. Clearly Apple is not communicating clearly enough that those versions are supported, since wikipedia and https://endoflife.date/ios says they are not supported. https://github.com/endoflife-date/endoflife.date/issues/9852#issuecomment-4409020504 this matters beyond classification accuracy: regulators (BSI in Germany, others) cite endoflife.date directly, and security-relevant app developers, including in regulated domains like medical software, are being forced to drop iOS 18 support based on endoflife.date

Hi everyone, I’m facing a confusing issue with my Apple Developer Program enrollment. I had previous payment/enrollment attempts that failed or were withdrawn. Later, I completed a new enrollment payment successfully and received both the order confirmation and invoice showing that the payment was charged. The problem is that Apple Developer Support seems to be replying to older failed/withdrawn attempts instead of the successful paid one. Their replies feel delayed and out of sequence, which is creating a misunderstanding. For example, they treated one old withdrawn enrollment as if I was asking for a refund, but I’m not asking for a refund. I want the successful paid membership to be activated. Now my Developer account is still not active, and it shows “Join the Apple Developer Program” / “Enroll today” as if I never enrolled, even though I already paid and received an invoice. Has anyone experienced this before? How can I get Apple Developer Support to review the correct successful paid enrollment instead of old failed attempts? Is there any way to speak with someone who can logically review the full case and activate the account?

My game has been stuck in “Waiting for Review” since March 18 (2 months now). I already received confirmation that my expedited review request was accepted (although it was only accepted about a week ago, despite requesting it much earlier), but the app still has not entered active review. Developer Support keeps confirming that the app is in queue and that it will be “reviewed shortly,” but I have heard that four times already, with no concrete action or explanation provided. Has anyone experienced something similar recently or found a solution?

Hello everyone, I’m a new indie developer building an app to help families locate kid-friendly spots like parks, splash pads, and indoor play areas. I'm currently using the Google Places API for my data, but I’ve found it to be surprisingly expensive. Even though I'm strictly in the testing phase and haven't shared the app yet, I've already accrued a $150 bill and am forecasting over $400/month. Is this pricing typical for the Google Places API? I would appreciate any advice on how to optimize these API calls to reduce costs, or if anyone can recommend more cost-effective alternatives for POI (Point of Interest) data. Thanks in advance for any feedback!

Hi everyone, I need help because I'm currently in a dead end: I cannot even start the enrollment process for the Apple Developer Program, and I've been stuck like this for 45+ days. Current Status: Completely Blocked When I open the Apple Developer app on my iPhone or Mac, the "Enroll Now" button is either missing or shows this message: "Enrollment through the Apple Developer app is not available for this Apple Account. Visit developer.apple.com/programs/enroll/" When I follow that link and try to enroll via the website, I hit another wall: the only payment option offered is credit card. My payment situation: I fund my Apple Account balance (this works perfectly for iCloud+, App Store purchases, subscriptions, etc.) I have sufficient funds in my Apple Account balance specifically for the Developer Program membership However, Apple Account balance is not accepted as a payment method for Developer Program enrollment on the web And the app won't even let me reach the payment step Result: I have no working pathway to enroll. App = disabled. Web = doesn't accept my Apple Account balance. How I Got Here Initially, the "Enroll" button in the app was active, but at the payment step I received "Unknown Error. Please try again." Apple Support reset my enrollment status to allow app-based enrollment (Case #102843620484). After multiple attempts (and a failed web enrollment attempt due to payment method), the app now shows the "not available for this Apple Account" message. I've submitted all requested documentation: screen recording, SEID, device info (iPhone 15 Pro, MacBook Air M1), government ID. Case escalated to senior advisor — only generic "we're still reviewing" responses for weeks. My Situation Region: Russia Apple ID: Personal account (long-standing, verified) Payment method: Apple Account balance (funded via mobile carrier) — works for all consumer Apple services Goal: Enroll as an individual developer to publish personal apps Questions Has anyone seen the message "Enrollment through the Apple Developer app is not available for this Apple Account" after a failed enrollment attempt? Is this a permanent block or a temporary glitch? Is there a way to reset or restore the "Enroll" button in the app without creating a new Apple ID? Is Apple Account balance officially supported for Developer Program enrollment in any region? If yes, how can it be enabled for my account? If Apple Account balance is unsupported: what legitimate alternatives exist for developers in Russia who don't have access to international credit cards? Has Apple Support ever resolved this specific combination of issues (app disabled + payment method restriction)? What I'm NOT Looking For "Just use a credit card" (not available to me) Workarounds that violate Apple's terms or regional policies Advice to create a new Apple ID (I need to use my primary, verified account) I'm committed to joining the program legally — I just need a working path to do so. Any insights, similar experiences, or official guidance would be incredibly helpful. Thank you in advance. — Sergey Case ID: #102843620484 (for reference)

Hi everyone, I need help because I'm currently in a dead end: I cannot even start the enrollment process for the Apple Developer Program, and I've been stuck like this for 45+ days. Current Status: Completely Blocked When I open the Apple Developer app on my iPhone or Mac, the "Enroll Now" button is either missing or shows this message: "Enrollment through the Apple Developer app is not available for this Apple Account. Visit developer.apple.com/programs/enroll/" When I follow that link and try to enroll via the website, I hit another wall: the only payment option offered is credit card. My payment situation: I fund my Apple Account balance (this works perfectly for iCloud+, App Store purchases, subscriptions, etc.) I have sufficient funds in my Apple Account balance specifically for the Developer Program membership However, Apple Account balance is not accepted as a payment method for Developer Program enrollment on the web And the app won't even let me reach the payment step Result: I have no working pathway to enroll. App = disabled. Web = doesn't accept my Apple Account balance. How I Got Here Initially, the "Enroll" button in the app was active, but at the payment step I received "Unknown Error. Please try again." Apple Support reset my enrollment status to allow app-based enrollment (Case #102843620484). After multiple attempts (and a failed web enrollment attempt due to payment method), the app now shows the "not available for this Apple Account" message. I've submitted all requested documentation: screen recording, SEID, device info (iPhone 15 Pro, MacBook Air M1), government ID. Case escalated to senior advisor - only generic "we're still reviewing" responses for weeks. My Situation Region: Russia Apple ID: Personal account (long-standing, verified) Payment method: Apple Account balance (funded via mobile carrier) — works for all consumer Apple services Goal: Enroll as an individual developer to publish personal apps Questions Has anyone seen the message "Enrollment through the Apple Developer app is not available for this Apple Account" after a failed enrollment attempt? Is this a permanent block or a temporary glitch? Is there a way to reset or restore the "Enroll" button in the app without creating a new Apple ID? Is Apple Account balance officially supported for Developer Program enrollment in any region? If yes, how can it be enabled for my account? If Apple Account balance is unsupported: what legitimate alternatives exist for developers in Russia who don't have access to international credit cards? Has Apple Support ever resolved this specific combination of issues (app disabled + payment method restriction)? What I'm NOT Looking For "Just use a credit card" (not available to me) Workarounds that violate Apple's terms or regional policies Advice to create a new Apple ID (I need to use my primary, verified account) I'm committed to joining the program legally - I just need a working path to do so. Any insights, similar experiences, or official guidance would be incredibly helpful. Thank you in advance. — Sergey Case ID: #102843620484 (for reference)

I appear to have found a reproducible issue/bug in the iPad version of Apple Pages relating to word-processing documents being converted into page layout documents after an automatic “Updating Document” process. Issue summary: New word-processing documents initially open correctly with “Document Body” enabled. After opening/saving/moving the document on iPad, Pages displays “Updating Document”. Once the update completes, “Document Body” becomes greyed out permanently and the document behaves like a page layout document with text boxes only. This affects: Apple’s built-in Blank template Custom templates I created myself Documents created using “Start Writing” Documents created on my iPhone and later opened on iPad Important observations: The problem only occurs on iPad. The same documents behave normally on iPhone. Documents are initially correct before Pages performs the “Updating Document” action. Holding down the Pages icon and selecting “Start Writing” creates a usable word-processing document initially. However, once the document is later moved/opened/saved from within Pages on iPad, it updates and becomes corrupted again. If I move documents while they are CLOSED using the Pages document browser or Files app, they can sometimes avoid corruption. If I move or manage the document while OPEN inside Pages, the issue almost always occurs. Restarting the iPad temporarily fixed the issue once, but the problem later returned. Reinstalling Pages without restarting did not fix it. The issue seems connected to Pages rewriting document metadata during save/update/sync operations. Things already tested: Creating new Blank documents Creating custom “true blank” templates Restarting iPad Force closing Pages Reinstalling Pages Using “Start Writing” Opening documents from iPhone Moving documents between folders Testing with iCloud and local files Current workaround: Use “Start Writing” Avoid moving/opening/saving documents from inside Pages when possible Move files only while closed via Files app or Pages document browser This appears to be either: a Pages document metadata corruption bug on iPad or an issue with the iPad Pages document management/update process converting word-processing documents into page layout documents unexpectedly.

Hello everyone, My Apple Developer membership has expired, my apps were removed from the App Store, and I’m currently unable to find any option to renew the membership. I already tried: Signing in through the Apple Developer account page Checking the Membership section Checking App Store Connect Trying different browsers/devices Visiting the enrollment and membership URLs directly However, there is no “Renew Membership” or “Re-enroll” button showing anywhere. Has anyone faced this issue before? Is there another process for restoring an expired account, or does Apple Support need to manually reactivate it? Any help would be appreciated. Thank you.

I tried creating an account on my computer and it got stuck with the same 401, i then tried it from my phone (not on wifi) and it got passed that but then when I had to enter the code that i was texted it said that my "Your account cannot be created at this time". I tried to just go create a new account and looked at the developer tools while I did it, got the same error but looking at the developer tools it sends back a 400 from the accounts api....... Come on guys, this isn't that hard. You literally have people in this doing the debugging for you.

In SwiftUI 6 when developing for MacOS in Xcode 26, there does not seem to be a way to provide an automatic increment of the current build number, i.e. "Current Project Version" in settings. Does anyone have a solution that works in the latest version of Xcode. i.e. 26? All the solutions that I have tried are based on older versions that involve running scripts to update the build file, (.xcconfig) or the .info.plist file which simply will not work in the current configuration.

Videos recorded on older iOS versions (including beta builds) play choppily in the Photos gallery preview layer, appearing to drop frames or have incorrect frame pacing. The same video plays perfectly smoothly when opened in Edit mode, and also plays smoothly after trimming even 1 frame and saving as a new clip — suggesting the source file is intact. The issue appears to be stale or incompatible preview proxy data / frame timing metadata (likely elst/ctts box mismatches) generated by older or beta AVFoundation versions, which the current PLPlaybackView fast-path renderer cannot handle correctly — while the full AVAsset decoder used in Edit mode tolerates these gracefully. No workaround exists to bulk-rebuild video proxies on iOS without manually trimming each clip. A “Rebuild Video Previews” option (similar to the Mac Photos library repair tool) would resolve this globally. Steps to reproduce: Open any video recorded on iOS 16 beta or earlier in the Photos gallery. Observe stuttering. Open same video in Edit mode — stuttering gone. Trim 1 frame, save — new clip plays smoothly in gallery too. Expected: Gallery preview plays at the same smoothness as Edit mode. Actual: Gallery preview stutters; Edit mode is smooth. HDR off. Most Compatible format enabled. Issue persists after reboot.

Does anyone have a free VPN tool for cross-external networks in mainland China? I can't read my Twitter. Whether it's Android or iOS, if you have it, can you send me the installation package or the download address? Thank you!

Hello My organization was enrolling developer program and during email verification, I have resent the code as I couldn't receive it to my organization email. After resending couple of times, now I have a message saying that exceed maximum attempt number. I have created a case with an ID : 20000115716550

We have submitted an enrollment request and cannot see the status. I cannot submit a support ticket as it is throwing a javascript exception. Unable to contact support or view status. Enrollment ID is F5T6HL5534

A while ago, I was able to go through the enrollment process all the way to the payment step, but I didn’t have an app ready to publish at that time, so I didn’t complete the payment. Two days ago, I finished developing my app and wanted to publish it on the App Store, so I tried to enroll in the Apple Developer Program. I attempted the enrollment on both my iPhone and Mac. On the Mac, after taking the required photo, I got an “unknown error”. Then I tried on my iPhone, but when I tapped the “Enroll Now” button, I was immediately shown a message saying “Contact Support”. After contacting Apple Support, I was told that my enrollment cannot be completed for “one or more reasons”. They couldn’t tell me the specific reason, nor could they tell me when I might be able to enroll again. I’m very confused — I was able to reach the payment step before, and when I searched online for “one or more reasons”, some people said it means being permanently blacklisted. But I have no idea what I did wrong, or why I would be permanently banned without any explanation. This is completely unacceptable.

FirstByte: Code-Core is a floating developer HUD for iPad that helps decode technical acronyms, coding terminology, and infrastructure concepts in real time. Designed for developers, students, operators, and AI-assisted workflows, the app features draggable transparent overlays, flip-card explanations, customizable themes, adjustable transparency, and a compact non-intrusive interface built for multitasking. Perfect for GitHub workflows, Web3 tooling, cloud infrastructure, SwiftUI development, and learning complex technical stacks without breaking focus.

Markup Tool: Support for persistent tool presets (color, stroke, fill settings) I use Markup heavily for work — up to 20 images per day, always with the same settings: red arrow or rectangle, no fill, specific stroke width. The problem has two parts: Part 1 – Markup resets everything: Every time Markup is opened, all settings reset: tool, color, fill, stroke width. This means 3–4 manual steps per image, adding up to 80 unnecessary interactions per day. Part 2 – The default red is unusable: The red in Apple’s color palette is muted and too pale for clear, high-contrast annotations. I have to open the color wheel every single time to manually select a proper, vivid red. The copy/duplicate workaround only helps within one image — as soon as a new photo or screenshot is opened, everything starts over from scratch. Markup has no memory between different images. Switching to a third-party annotation app is not a solution — the entire advantage of Markup is its native integration directly within the Photos app, without switching apps. And Markup cannot be configured in depth through Shortcuts either — color, fill, and stroke width are not controllable there. The attached images: Image 1 shows the entry point in the Photos app. Image 2 shows Markup open with the current color palette. The blue-outlined fields do not indicate colors to be replaced — they mark the position where personally configured tool presets should appear: not individual colors, but fully pre-configured tools with color, stroke width, and fill setting already saved, ready to use with a single tap. My suggestion: Tool presets — configure once, saved permanently, available directly in the Markup toolbar. No need to re-configure color, fill, or stroke width for every new image. iOS already remembers last-used settings in many areas: camera mode, emojis, colors in Notes, Pages, and Keynote. Markup behaves as if it’s being opened for the first time, every time. This inconsistency costs me measurable time every single day.

i placed my payment exactly one week ago and still havent been approved, im from argentina,

The first review was on May 5th and got rejection with 2.1 (b) and 3.1.2(c). I took my time to localize screenshots, app metadata, and the subscription pricing and re-submitted for review (also replied to the early rejection) on May 10th. It's been more than 48 hours, but the status is still 'waiting for review'. I wonder if it's normal or if I should reply to the rejection again? Thanks!

Hello juice community. firts of all, i'm brazilian dev, soo this conversation will be a lot errors of english. but i'm think is a nice to prove is not a AI generate post here. hehe I want a big tip, how i integrate my app in the fruit ecosystem. Soo, i launch a AI prompt plataform, the idea is make users your own prompt, you make a context for him, like " you are a food master chief", and configure the inputs, like a photo of your freezer, to the AI take the ingredients e make a recipe with AI. The aplication is infinite! The integration, now, is with AI provider. the idea is not make a context with complex Skills.sh, but the common user create your own Prompt/AI and feel a prompt engineer master. i'm think the is a powerful plataform for native apple system. the plataform has url, and if any one has interesting a will chat in the comments the name for see how beaut is.