Hello🙏, I’m a new indie developer and I’m trying to understand review timing behavior. Context: App type: Game built with Unreal Engine 5 Initial submission: Entered “In Review” within 48 hrs. Result: Rejected due to icon similarity (icon too similar to an existing App Store icon) What I did next: I updated the icon to ensure it is clearly distinguishable and resubmitted. After 30 (?)hrs, I removed/rejected that submission myself while it was still in "Waiting For Review" because I suspected the icon asset might still contain a transparency issue (this was my own precaution before Apple flagged anything). I then corrected the icon asset and submitted again (current submission: Build 7). Current status: Status: Waiting for Review Duration: 9 days Calendar days ( Mon, 09 Feb and today is 17th Feb 26) in this state for Build 7 Additional notes: The app runs without crashes on my iPhone and iPad. During the earlier review, Apple only raised the icon similarity issue (no functional issues were mentioned). I contacted App Store Connect support; they couldn’t provide a queue timeline, but nothing appears flagged on their side. Question: Is it normal for a resubmitted build (after correcting an icon-related rejection, and after a developer-cancelled submission) to remain in “Waiting for Review” for an extended period before switching to “In Review”? I’m trying to understand if this is typical queue variability or if removing a submission and resubmitting can affect how long it stays in “Waiting for Review.” Thank you for any insights.

Hello🙏, I’m a new indie developer and I’m trying to understand review timing behavior. Context: App type: Game built with Unreal Engine 5 Initial submission: Entered “In Review” within 41 (?) hrs. Result: Rejected due to icon similarity (icon too similar to an existing App Store icon) What I did next: I updated the icon to ensure it is clearly distinguishable and resubmitted. A day later that, I removed/rejected that submission myself while it was "Waiting for Review" because I suspected the icon asset might still contain a transparency issue (this was my own precaution before Apple flagged anything). I then corrected the icon asset and submitted again (current submission: Build 7). Current status: Status: Waiting for Review Duration: 8 Calendar days in this state (09 Feb 1208 hrs and today is 17th Feb 26, 1044 hrs) for Build 7 Additional notes: The app runs without crashes on my iPhone and iPad. During the earlier review, Apple only raised the icon similarity issue (no functional issues were mentioned). I contacted App Store Connect support; they couldn’t provide a queue timeline, but nothing appears flagged on their side. Question: Is it normal for a resubmitted build (after correcting an icon-related rejection, and after a developer-cancelled submission) to remain in “Waiting for Review” for an extended period before switching to “In Review”? I’m trying to understand if this is typical queue variability or if removing a submission and resubmitting can affect how long it stays in “Waiting for Review.” Thank you for any insights.

following the update of the system of my MBP 16" M1 to beta 26.4 none of my external drives work anymore

I have a question about the full-time employment eligibility requirement for the Swift Student Challenge 2026. The rules state that applicants cannot be "employed full time as a developer" at the time of submission. My situation is a bit nuanced: I work as a software engineer at a company, but my contract explicitly distinguishes between summer and school year employment. During the summer I work full-time, but during the school year my hours are part-time and flexible, and therefore not a fixed schedule. Since the submission deadline is February 28th, I would be submitting during the school year, at which point I am not working full-time. My question: Does the eligibility rule apply strictly to full-time hours at the time of submission, or does being employed in a developer role at all (even part-time during the school year) disqualify me?

I'm working on my Swift Student Challenge 2026 submission and have a question about the evaluation environment. My app targets iOS 26 (I had to configure this on the Package.swift file directly) and uses the Speech framework for on-device speech recognition. I've selected Swift Playgrounds as my evaluation path (rather than Xcode) with the intention of having it run on a physical iPad rather than Simulator. My question: What version of iPadOS will the evaluation iPads be running? The reason I ask is practical, as my app's minimum deployment target is iOS 26. If the evaluation device is running an earlier version of iPadOS, the app won't launch at all. I've searched the eligibility and terms pages but couldn't find this documented anywhere.

My apps been live on the app store for over a day now and my subscriptions have been stuck on waiting for review, ive sent an email and even been on live imsg support but they cant help either and i have had nothing back via email. has anyone got any suggestions

So i and many other big youtubers out there use iphones for intense gaming such as callcof duty and fortnite. However apple never listens especially to those of us that have been your guys's clients since the early 2000's. Users have different guinsetups for their games and a lot of the time when in an intense conpetition and the the low battery animation pops up it blocks our screens and that 3 to 4 seconds it takes to disappear makes us lose a game. Apple needs to implement a feature that allows us to toggle the notification even if our phone dies or a more efficient route would be allow us to toggle or set it by default to show that your battery is low on the top of the screen where the black line expands when you start charging your phone so it doesn't affect my gameplay whatsoever. This is a crucial thing apple needs to do, many people won't report it because apple never listens. Another great feature would be if apple could make a charging port on the side for claw players.

Please help. I purchased an Apple Developer account subscription through the iPhone app. It's listed in the App Store, but it's not listed in Apple Developer itself. I've been waiting for a response from support for over a week, but it's as if they've completely forgotten about me; no one's responding. Although, in fact, it says two days ago. Has anyone else encountered this and can help? It's asking me to pay a second time, and through the website.

Criei uma conta dev em outubro, mas até o momento não tive nenhum retorno.

Hello Apple Developer Technical Support team, We have an iOS app that provides caller identification via a Call Directory extension (CXCallDirectoryProvider). Our extension provides identification entries (phone number → label), and users enable it in Settings > Phone > Call Blocking & Identification. We would like to confirm whether Call Directory is used only for incoming calls, and understand why the outgoing call UI sometimes shows labels. Observed behavior Incoming calls: After a user logs in again (which triggers a server sync and then reloads the Call Directory extension), the caller label is shown correctly on the incoming call screen for matching numbers. Outgoing calls: In general, the outgoing call screen often shows only the phone number (no label), even when the same number exists in our identification entries and the extension is enabled. However, on some devices, the outgoing call screen does show a label even when the number is not saved in the local Contacts app. In at least one customer case, the outgoing label behavior changed after an iOS update: before updating iOS, labels were not shown on outgoing calls; after updating iOS, labels started appearing (with no changes in our app settings/config). Questions Is the Phone app expected to consult Call Directory identification entries only for incoming calls (caller ID), and not for outgoing call UI? If labels can appear on outgoing calls, what are the possible sources and rules (e.g., Recents cache, carrier Name Display/CNAM, other system caches), and is any of that behavior documented? Are there known iOS version changes or issues that could explain “outgoing label not shown” becoming “outgoing label shown” after an OS update? We can provide: A minimal repro project, steps to reproduce, and exact iOS versions/devices Screenshots/video sysdiagnose / device logs (please advise what log types are most useful) Thank you,

As the title says, in apple developer site under (Certificates, Identifiers & Profiles) all my devices are set to inactive, and I cannot enable them back because my twices are glitched I have 2 devices and they are there twice each with the same UDID. So I cannot enable a single one. I’m hit with “A device with number 'UDID number' already exists on this team.” I have an iPad Pro and iPhone 17 Pro Max, I cannot sign any apps to them at all or do anything because my devices are set to inactive, I’ve contacted apple numerous times, and I can’t seem to get any help regarding this issue. I’ve called and emailed, and the developer team has yet to respond to me, if anyone’s had this issue please tell me how you solved it. i also cannot erase any devices myself until my renewal date. ive tried manually adding my devices, and its the same message that my devices already exist on team. Ive signed out of my apple account on my devices, changed pw, turned off developer mode and renabled it numerous times, I really don’t know what to do.

Is anybody using Airbnb's Lottie-ios dependency inside your swift student challenge project? If yes can u please discuss about how did u approach using it ? Actually I wanted to use it so I downloaded the official repo maintained by Airbnb from GitHub but the package had too large size so I deleted many part's leaving just src files and some other files as it is and even modified it's package.swift file and finally deleted the .git folder which had been taking way too much space. And now I have been using it as local dependency which I can include it in my .zip submission ( as that's the rule I guess to include the packages our project depends on in our .zip submission file ). So far there have been no problems, I wanna know am I doing anything wrong here? Can someone advise me ?

I was working on my challenge submission but when I created a iOS swift playground through Xcode, the playground generated get's defaulted to iOS 18, and I can't use latest features like the new glass design seemlessely without using #if available macro's everywhere so I manually changed iOS 18.0 to iOS 26.0 in the package.swift file. So far there have been no problems but as the package.swift file recommends not to change it manually so am I in any problem can someone give me advice of whether it's a legit option ??

I am trying to develop a Watch and iOS app as companion. It is beyond stupid how I can not keep the watch connected to Xcode to develop. I have tried all the so-called tricks. Why is this so fragile? The phone is USB connected to my Mac I have tried turning off the wifi on my Mac and have the phone and watch on the same network. Nada I have tried just having everything on the same network. The watch is connected maybe 20% of the time. I have tried creating a hotspot network with my phone. The watch is connected maybe 50% of the time. This is truly an awful experience. Am I doing something wrong? Any advice would be grateful.

Good morning, the link https://applepaydemo.apple.com/wallet-extensions returns a {"detail":"Not Found"} when accessed. This is one of the links that are present in https://developer.apple.com/documentation/PassKit/implementing-wallet-extensions, could this be looked at please ? The exact place is: For more information on Wallet Extensions, see the Apple Pay Demo - Wallet Extensions documentation.

Environment: Device: MacBook Pro (Mac16,7) Chip: M4 Pro (SoC ID 6040, Revision 11) OS: macOS 15.2 (24C101) Kernel: Darwin Kernel Version 24.2.0; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 Summary: I am developing a Windows emulator on the MacBook Pro M4 Pro platform. During testing with certain applications, the system frequently triggers an instantaneous reboot. This issue appears to be highly specific to the M4 Pro hardware and current OS version. Observation & Diagnostic Challenges: Upon reboot, the system generates a bug_type 210 (SoC Watchdog Reset) report. The panic string indicates: "Unexpected SoC (system) watchdog reset occurred after panic diagnostics were completed". The primary difficulty in debugging is that the hardware reset happens so rapidly that the kernel fails to capture a stackshot or any detailed panic trace. We have practically no actionable information from the standard diagnostic reports. However, we did find the following recurring entries in the system log prior to the resets: Ignored NI0 NI0 niGeneral 1 NO_ACCESS error (0x00000010) cmd/st:0x14(ncrdincr)... srcchildid/srcparentid:0x8ea/0x1d Comparison & Testing: We have performed extensive cross-version and cross-device testing to isolate the cause: M1/M2 Series: Identical tests on M1 and M2 devices running macOS 15 do not trigger this issue. The applications run stably. OS Versions: Interestingly, this issue seems significantly harder to reproduce on newer system builds (e.g., version 26 series), suggesting it might be a regression or a specific incompatibility in the current macOS 15.2 environment for M4 Pro. Request for Assistance: Since we cannot collect stack traces through conventional means, we are seeking your expertise: Known Issues: Has Apple received similar reports from other developers working on low-level emulation or virtualization on M4 Pro? Is this a known issue in macOS 15.2 / build 24C101? Debugging Guidance: Given that the system reboots without leaving a stackshot, what are the recommended methods to capture more granular data? Are there specific boot-args or instrumentation tools that can help log the state of the SoC fabric (NI0) before the watchdog kicks in? Architectural Insights: Based on the NI0 NO_ACCESS error and srcchildid: 0x8ea, could you suggest which subsystem or memory operation we should investigate further?

I am a developer from Hong Kong and do not have a credit card or the like issued by the United States. Currently, I am unable to make payments. What should I do?

Hi everyone, I’m new to the Apple Developer side of things and I want to make sure I’m handling this correctly. I hired a freelance iOS developer to build my app. I have my own Apple Developer account (Individual), and I want the app published under my account. The developer says he needs me to create a Certificate Signing Request (CSR), then he will generate the distribution certificate on his end and send me the .cer file back. From there, he would use that for signing and submitting the app. My questions: 1. Is this the correct and modern way to handle app signing? 2. Should I instead just add him to my App Store Connect account with Developer access and let him manage signing through Xcode? Dev claims this won’t work, which I haven’t been able to prove or disprove. ChatGPT says it does,but other AI tools says it doesn’t. 3. Is there any risk in sharing certificates like this? 4. What is considered best practice in 2026 for working with freelancers while keeping full control of the account? My goal is simple: • The app stays fully under my Apple Developer account. • I retain long term control. • The developer can build and submit without needing my Apple ID or password. I’m not trying to make things complicated, I just want to do this the right way and avoid issues later. Thanks in advance.

Hi, I have a big suggestion for the next update! My suggestion is to upgrade the call filtering system : - “Block suspicious calls” It automatically block numbers that are likely to be unwanted or spam. These calls should not ring, should not appear in the call history, and should be silently discarded. - “Block unknown callers/hidden numbers” Instead of receiving a call from a hidden or unknown caller and seeing it appear in the missed calls list, the call should be completely blocked and not recorded at all, no notification, no sight of call. - “Filter numbers that are not from contacts” If the same unknown number calls too frequently within a week and the user never answers (for example 10 times per day, or 5 times per day if considered suspicious or too much spam in a little time), the iPhone should automatically block this number. The device would display a message such as: “This number has called too many times and has been automatically blocked for 3 day(or 1 week).” The block could also apply to the entire IP range or source associated with the unknown caller. It is very helpful for most of unwanted calls.

Is the MacOs tahoe 26.2 Finder's Column "column width" not adjustable in column mode?