Overview

I have been experiencing many issues trying to integrate the Apple AlarmKit in my app. I essentially keeping getting authorization errors. I was wondering if anyone else was experiencing issues like this and if anyone had guidance or a fix for what I am experiencing. I was under the impression that any devices IOS26+ could use the AlarmKit but maybe I am mistaken. Getting (com.apple.AlarmKit.Alarm error 1.) every time I try and enable alarms.

I asked AI to build a realistic ocean shader for a VisionOS project using RealityKit. It gave a bunch instructions and asked me to connect large amount of nodes for the ShaderGraph in the Reality Composer Pro. I am just wondering if AI can help to generate the Metal shader code directly, or build the ShaderGraph nodes for me automatically.

Hello, I’m implementing VoIP calling in an iOS application using PushKit (VoIP pushes) together with CallKit. The standard call flow works correctly: Happy scenario User A initiates a call. Server sends a VoIP push to User B. User B’s device receives the push and reports the incoming call using CallKit. User B answers the call. However, I would like clarification about non-happy scenarios and when it is acceptable to use VoIP pushes to update or stop a CallKit ringing state. Apple documentation warns that VoIP pushes must be used only when they result in a call-related action, so I want to ensure the following cases are compliant. Scenario A — Caller Cancels Before Answer User A calls User B. Server sends a VoIP push to User B. User B’s device starts ringing via CallKit. Before User B answers, User A cancels the call. Question: Is it acceptable to send another VoIP push to User B indicating that the call has been cancelled so the device can: stop the CallKit ringing UI end the call optionally mark it as missed or cancelled Or should this state change be handled using a regular remote push or another signaling mechanism instead of VoIP push? Scenario B — Callee Rejects the Call User B rejects the call from CallKit. The server must inform User A that the call was rejected. Question: Is it acceptable to send a VoIP push to User A to update the CallKit state and terminate the outgoing call UI? Scenario C — Multiple Devices per User User B may be logged in on multiple devices. User A calls User B. VoIP push is sent to all devices of User B. One device answers. Question: Is it acceptable to send a VoIP push to the remaining devices instructing them to: stop ringing end the CallKit incoming call UI Or is there a recommended alternative pattern for this case? Main Question Aside from the initial incoming call VoIP push, in which situations is it considered acceptable to send additional VoIP pushes to terminate or update CallKit state (cancelled, rejected, answered on another device)? The goal is to remain compliant with PushKit policies, particularly the guidance that VoIP pushes should only be used when they result in a call-related user action. Any guidance on the recommended architecture for these cases would be greatly appreciated. Thank you.

Hello everyone, I'm reaching out to see if anyone has experienced a similar situation or has any advice. My app "Currot" has been in "Waiting for Review" across multiple submissions since February 8, 2026. Despite following all recommended steps, the review team has not responded. Timeline: Feb 8: Initial submission Feb 11 (04:50 AM): Moved to "In Review" Feb 11 (05:17 AM): Rejected (Guidelines 2.3.6, 5.1.1, 1.2, 5.1.1v) Feb 11 (08:10 PM): All four issues resolved, resubmitted same day with detailed screenshots in Resolution Center Feb 14: Follow-up message sent via Resolution Center — no response Feb 23: After 12 days of no movement, canceled and resubmitted with review notes explaining all resolved issues Mar 4: Developer Support (Case 102831733019) confirmed they notified the review team Mar 9: Follow-up email and phone call requesting escalation Mar 10: Developer Support confirmed they escalated again Mar 12 (today): Still "Waiting for Review" — 32 days since initial submission, 17 days since latest submission Actions taken: Expedited review request Resolution Center messages with screenshots Multiple Developer Support emails and phone calls Two escalations to the review team Account status: No warnings or unresolved items in App Store Connect All agreements active DSA compliance completed The app has been approved on Google Play with no issues I understand the review team is busy, and I appreciate the work they do. However, 32 days without any review — despite two escalations — is significantly beyond normal timelines. I would be grateful for any guidance on whether there is a specific blocker on my submission or if this is a known queue issue. Thank you for your time.

I am requesting a dedicated toggle in Settings > Display & Brightness (or Accessibility) to enable/disable the Liquid Glass UI effects so that I am able to get frosted glass thingy effect that was in iOS 18 back.

Our app Miiro (App ID: 6759159052) was rejected for Guideline 3.1.2(c) on March 13. We fixed the pricing hierarchy on the paywall (yearly price now displayed as primary, monthly equivalent as subordinate) and resubmitted the same day at 2:25 PM CET. We also replied in the Resolution Center explaining the fix. The build moved to "In Review" shortly after but has been stuck there for over 29 hours with no status change. We requested an expedited review on March 14. This is our first app submission. We are a small two-person team and the app is ready for launch. Any help moving this forward would be appreciated.

Recently I noticed that although my drive showed ~800Gb of usage, the folders within totally to around ~600Gb (and yes I was including hidden 'dot' files/folders. After some inspection I found that there are a whole set of Disk Media Images, that appear to be related to XCode simulators. Here's an extract from the command line diskutil list command: /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk5 Physical Store disk4s1 1: APFS Volume iOS 26.2 Simulator 17.1 GB disk5s1 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.2 GB disk6 1: Apple_APFS Container disk7 14.2 GB disk6s1 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.2 GB disk7 Physical Store disk6s1 1: APFS Volume XROS 26.2 Simulator 13.8 GB disk7s1 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.2 GB disk8 1: Apple_APFS Container disk9 17.2 GB disk8s1 /dev/disk9 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.2 GB disk9 Physical Store disk8s1 1: APFS Volume iOS 26.0 Simulator 16.7 GB disk9s1 /dev/disk10 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +8.5 GB disk10 1: Apple_APFS Container disk11 8.5 GB disk10s1 /dev/disk11 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +8.5 GB disk11 Physical Store disk10s1 1: APFS Volume XROS 2.5 Simulator B... 8.2 GB disk11s1 /dev/disk12 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +18.0 GB disk12 1: Apple_APFS Container disk13 18.0 GB disk12s1 /dev/disk13 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +18.0 GB disk13 Physical Store disk12s1 1: APFS Volume XROS 2.5 Simulator 17.5 GB disk13s1 /dev/disk14 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk14 1: Apple_APFS Container disk15 17.6 GB disk14s1 /dev/disk15 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk15 Physical Store disk14s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk15s1 /dev/disk16 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.1 GB disk16 1: Apple_APFS Container disk17 14.1 GB disk16s1 /dev/disk17 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.1 GB disk17 Physical Store disk16s1 1: APFS Volume XROS 26.1 Simulator 13.7 GB disk17s1 /dev/disk18 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk18 1: Apple_APFS Container disk19 17.6 GB disk18s1 /dev/disk19 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk19 Physical Store disk18s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk19s1 /dev/disk20 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +9.1 GB disk20 1: Apple_APFS Container disk21 9.1 GB disk20s1 /dev/disk21 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +9.1 GB disk21 Physical Store disk20s1 1: APFS Volume iOS 18.5 Simulator B... 8.8 GB disk21s1 /dev/disk22 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +20.7 GB disk22 1: Apple_APFS Container disk23 20.7 GB disk22s1 /dev/disk23 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +20.7 GB disk23 Physical Store disk22s1 1: APFS Volume iOS 18.5 Simulator 20.2 GB disk23s1 I am unable to unmount them, either from the command line or Disk Utility. How do I go about this?

Hi Writing an app in Swift on Xcode for my iPhone, all software is the latest version. If after making a minor change and re-building all the application data has disappeared, is there a way to see if it is still in the .modelContainer and just not showing up?

Hello, I recently submitted an enrollment request for the Apple Developer Program as an organization. After submitting the request, I realized that I entered incorrect contact information for the person authorized to confirm my authority to enroll the organization. I would like to update the email address for this contact. I already contacted Apple Developer Support by email but have not received a response yet. Is there a way to update this information while the enrollment is still under review? Or should I cancel the request and submit a new one? Any guidance would be greatly appreciated. Thank you.

Hello, according to reports from our users these two ManagedSettingsStore options seem to be stuck in the enabled state even after turning them off or removing screen time permissions and uninstalling the app that configured them. Is this possible? Has anyone seen it? The denyAppRemoval (https://aninterestingwebsite.com/documentation/managedsettings/applicationsettings/denyappremoval-swift.property) prevents the user from uninstalling any apps from their device when active. The denyAppInstallation (https://aninterestingwebsite.com/documentation/managedsettings/applicationsettings/denyappinstallation-swift.property) "hides" App Store, making it impossible to install any new apps. We haven't been able to replicate it yet. Does anyone know about workarounds when this happens? So far it seems like the only way is to reset the affected device.

Please help! I can’t update my developer info and when I renew my membership I’m taken to an account that I had in Europe which I no longer use or have money tied to. I want to switch my account to USA and use a usa account

Hello! I'm reaching out because we're seeing an inconsistency in App Store Connect data after we implemented the iOS Smart App Download Banner on our websites: when we go to App Store Connect → App Analytics → Acquisition → Campaigns, we see: “There isn’t enough data to display campaigns.” despite the fact that we expect to see some download data there. Context: Apps: HomeRun – Get Things Done (App ID: 1506390428) and ProntoPro - Trova Professionisti (App ID: 1274970171) We deployed the iOS Smart App Banner on the corresponding web pages on March 5 (https://homerun.pl/ and https://prontopro.ch/) We have also created corresponding campaigns in App Store Connect and are passing tokens via the banner meta tag: We tested this in real life by downloading both apps at least 5 times using distinct Apple accounts which never downloaded the apps before. Verification You can visit our websites (https://homerun.pl/ and https://prontopro.ch/) and verify the Smart App Banner configuration by viewing the page HTML source and locating the apple-itunes-app meta tag and its affiliate-data value. If helpful, we can provide any other additional resource of info you might need. Thanks a lot in advance for your help!

Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as "You receive this error when the system prompts a person and they decide not to share their age range with your app. ", as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorithm to test given feature for macOS (mock region, mock age, mock source of approval, revoke declared range, etc). Now I get a review with rejection, stating that I don't have age verification mechanisms present in my app. Also I found out that after filling the App Information regarding Age Ratings it spreads to all fresh releases, so even though my newest macOS release doesn't contain age verification mechanisms yet, it should, as iOS release has got this functionality up and running already and I had to check this when filling Age Ratings questionnaire. Now I'm stuck between removing this capability from App Information, so the macOS release can pass and stalling macOS releases until there is a proper usable API to implement Declared Age Range verification properly (at least the same way as on iOS). How should I properly develop and test this feature for macOS before releasing it publicly?

Stage Feed - Test Flight Link Tracking your favorite Artists, does NOT need to be so cumbersome! Please try our app, we would really love to have you! Any and all feedback would greatly be appreciated!

My app was submitted on February 14, 2026, and the Apple ID is 6758344632. It has now been over a month, but the app is still in Waiting for Review status. Could you please let me know when the review is expected to be processed?

I am currently running iOS 26.4 Beta and have encountered a critical issue with the in-app purchase system. Due to a system malfunction in this beta version, I was charged multiple times for the same purchase. I have already submitted a formal refund request through the official channels; however, the request was rejected/not processed. Has anyone else experienced similar billing issues on this specific beta build? Any advice on how to escalate this, given that the standard refund process has failed?

My app has been under review for longer than usual, and I would like to check if anyone else is experiencing the same situation. Submitted Date: Tuesday at 11:37 AM Apple ID: 6499260089 It has been more than 3 days now and the status is still “Waiting for Review” / “In Review.”

I’ve been developing apps for 8 years. On the tenth update of my latest app, I got yet another new rejection reason. I co-founded an app called Yuna AI with my wife, who is a Registered Dietitian and a member of the CDO. When trying to release version 1.0.10, I was told I can’t publish it under my name as a sole proprietor. I’m honestly starting to lose faith in the review process. My previous submission was rejected for not properly disclosing in-app purchases, even though my app doesn’t have any in-app purchases. Rejection reason "The app must be published under a seller and company name that is associated with the organization or company providing the services. In this case, the app must be published under a seller name and company name that reflects the Yuna AI name. The guideline 5.1.1(ix) requirements give users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data." Do i really have to pay to incorporate a company to put my app under and a sole proprietorship isn't enough? Im going to be moving soon and probably not best for me to incorporate now in Canada. does that mean i don't get to update my app anymore?

How can i get a simple figma layout with minimal art into xcode

Hello everyone, I’m running into an issue with my Apple Developer Program enrollment and hoping someone here or an Apple staff member can point me in the right direction. I tried to pay the annual fee, but my account status wasn't updating. Thinking the transaction had failed, I tried to make the payment a second time a few days later. Because of this, my credit card was actually charged twice. The charges appear on my bank statement as: February 19 (R$ 543.16 BRL) February 23 (R$ 536.70 BRL) Despite both payments clearing on my end, it is now March 16 and my account still shows as pending. My enrollment has not been approved yet. Has anyone else experienced this kind of delay? What is the best way to get Apple to activate the account using one of these payments and issue a refund for the duplicate charge? I have all the bank statements ready to show support, but the process has been completely stuck. Thank you in advance for any advice.