Overview

Post

Replies

Boosts

Views

Activity

popoverTips don't display for toolbar menu buttons in iOS 26.1
[Also submitted as FB20756013] A popoverTip does not display for toolbar menu buttons in iOS 26.1 (23B5073a). The same code displays tips correctly in iOS 18.6. The issue occurs both in the simulator and on a physical device. Repro Steps Build and run the Sample Code below on iOS 26.1. Observe that the popoverTip does not display. Repeat on iOS 18.6 to confirm expected behavior. Expected popoverTips should appear when attached to a toolbar menu button, as they do in iOS 18.6. Actual No tip is displayed on iOS 26.1. System Info macOS 15.7.1 (24G231) Xcode 26.1 beta 3 (17B5045g) iOS 26.1 (23B5073a) Screenshot Screenshot showing two simulators side by side—iOS 18.6 on the left (tip displayed) and iOS 26.1 on the right (no tip displayed). Sample code import SwiftUI import TipKit struct PopoverTip: Tip { var title: Text { Text("Menu Tip") } var message: Text? { Text("This tip displays on iOS 18.6, but NOT on iOS 26.1.") } } struct ContentView: View { var tip = PopoverTip() var body: some View { NavigationStack { Text("`popoverTip` doesn't display on iOS 26.1 but does in iOS 18.6") .padding() .toolbar { ToolbarItem(placement: .topBarTrailing) { Menu { Button("Dismiss", role: .cancel) { } Button("Do Nothing") { } } label: { Label("More", systemImage: "ellipsis") } .popoverTip(tip) } } .navigationTitle("Popover Tip Issue") .navigationBarTitleDisplayMode(.inline) } } }
3
3
355
20h
URGENT: Developer Program Expired – No Renewal Option – App Removed from App Store
Hello, We are currently experiencing a serious issue with our Apple Developer Program membership. Our membership has expired, but there is no option to renew the membership anywhere: Not on the Apple Developer website Not in the Apple Developer app Attempting to start enrollment again redirects to the main page Account details: Team ID: RZR56J4QQ8 Organization: E. V. I. ELECTRIC CARS LTD Role: Account Holder Because of this issue: All App Store agreements show as expired Our app has been removed from the App Store We are currently unable to restore service to users We already opened a Developer Support ticket about a week ago, but have not received any response. This is causing business impact, and we cannot find any way to trigger the renewal flow. Has anyone experienced this issue before, where the Renew Membership button does not appear at all? If anyone from Apple Developer Support / Apple Staff is able to assist or escalate this issue, it would be greatly appreciated. Thank you.
3
0
46
20h
App stuck on “Ready for Distribution” – Trader status not provided / DSA in review
Hi, My app status is currently “Ready for Distribution”, but it still hasn’t appeared on the App Store and I’m not sure what is blocking the release. In App Store Connect, I have already completed: • Agreements, Tax, and Banking (all active) • Pricing and Availability (countries selected) • Automatic release is enabled However: • My Digital Services Act (DSA) status is still “In Review” • I am also in the process of changing my account from Individual to Organization At this point, I’m not sure if the delay is caused by DSA review, account type change, or something else. Has anyone experienced a similar situation? Is there anything else I should check or complete to make sure the app goes live? Apple ID: 6760753842 Thank you.
2
0
62
20h
Digital Services Act: In Review for 14 days already.
Hi all, I was wondering if someone could provide more information about the Digital Services Act review process. I haven’t been able to find any details online, and I haven’t received a response to my support requests (it has been 9 days so far). I submitted the requested Digital Services Act information on February 27, but I haven’t received any update or automated confirmation email. The request is still visible under business agreements in my Apple Store Connect account. Does anyone know how long this review typically takes? Or whether I should contact support through a different channel? Thank you in advance!
7
4
249
20h
Apple Developer Program paid on March 31 but still not activated - No response from Support
Hi everyone, I am writing to seek help regarding my Apple Developer Program enrollment. I successfully paid the $99 USD enrollment fee on March 31, 2026. I received the official invoice (Web Order Number: D009560930), and my credit card was successfully charged. However, as of today, my developer account is still pending and has not been activated. I have already sent two separate emails to Apple Developer Support requesting assistance over the past few days, but I have not received any response or update from them yet. Has anyone experienced a similar delay recently? Is there any other way to escalate this issue or contact support directly to get my account activated? I have attached my invoice for reference. Any advice or help from the Apple team would be greatly appreciated! Thank you.
0
0
29
20h
Still in “Waiting for Review” despite multiple support cases and an accepted expedited review
Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.
0
0
20
20h
SwiftData document-based app crashes on undo/redo with autosaveEnabled
Overview I'm developing a document-based app for macOS using SwiftData. When I undo/redo changes using Command-Z/ Command-Shift-Z, the app randomly crashes with the following error: SwiftData/BackingData.swift:425: Fatal error: Failed to retrieve the identifier for \ChildItem.parentItem from KnownKeysDictionary:KnownKeysMap: ["parentItem": 2, "isModified": 1, "index": 0] values: [Optional(0), Optional(false), Optional(DocumentTest.ParentItem)] SwiftData._KKMDBackingData<DocumentTest.ChildItem> And sometimes, instead of the app crashing, my created @Model objects simply disappear. They do not reappear in the @Query on undo/redo. Both of these issues go away when I set modelContext.autosaveEnabled = false The issues are occurring with Xcode 26.4 (17E192) and macOS Tahoe 26.4 (25E246). I have modified the macOS Document App project template to showcase the issue. The project, along with a screen recording of the crash, can be downloaded from here: https://drive.google.com/drive/folders/1aDO34QleTm_rB9BuvVGjzzAP6jDXOc-o?usp=share_link Has anyone else experienced this? I'd like to know if this is a bug in the autosave feature of SwiftData and if I should file a bug report via Feedback Assistant. Steps to Reproduce To recreate the issue, follow these steps: Download and extract the "Xcode Project.zip" file linked above. Open the extracted "DocumentTest" project in Xcode. Build and run the "DocumentTest" app. In the document selection window, click "New Document" at the bottom-left. In the app, click the "+" button at the top-right to add a ParentItem with ChildItems. Click on the added ParentItem's button to modify one of its ChildItems. Repeat steps 5–6 until you have 5 ParentItems with a modified ChildItem. Press Command-Z 10 times to undo all the changes. Press Command-Shift-Z 10 times to redo all the changes. Repeat steps 8–9 until either the app crashes or some of the 5 ParentItems go missing in the list (you may have to repeat them 10–20 times before the issue occurs). If you change line 43 of ContentView.swift to modelContext.autosaveEnabled = false and repeat the same steps above, the app will not crash and no ParentItems will go missing. Code ParentItem Model @Model final class ParentItem { var timestamp: Date @Relationship( deleteRule: .cascade, inverse: \ChildItem.parentItem ) var childItems: [ChildItem] = [] init(timestamp: Date) { self.timestamp = timestamp } } ChildItem Model @Model final class ChildItem { var index: Int var isModified = false var parentItem: ParentItem? init(index: Int) { self.index = index } } Creating, Inserting, and Linking ParentItem and ChildItem // Create and insert ParentItem let newParentItem = ParentItem( timestamp: Date() ) modelContext.insert(newParentItem) // Create and insert ChildItems var newChildItems: [ChildItem] = [] for index in 0..<Int.random(in: 2...8) { let newChildItem = ChildItem(index: index) newChildItems.append(newChildItem) modelContext.insert(newChildItem) } /* Establish relationship between ParentItem and ChildItems */ newParentItem.childItems = newChildItems Modifying ChildItem let firstChildItem = parentItem.childItems .sorted(by: { $0.index < $1.index }).first if let firstChildItem, !firstChildItem.isModified { firstChildItem.isModified = true }
0
0
54
20h
Still in “Waiting for Review” despite multiple support cases and an accepted expedited review
Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.
0
0
17
20h
Apple Developer Program paid on March 31 but still not activated - No response from Support
Hi everyone, I am writing to seek help regarding my Apple Developer Program enrollment. I successfully paid the $99 USD enrollment fee on March 31, 2026. I received the official invoice (Web Order Number: D009560930), and my credit card was successfully charged. However, as of today, my developer account is still pending and has not been activated. I have already sent two separate emails to Apple Developer Support requesting assistance over the past few days, but I have not received any response or update from them yet. Has anyone experienced a similar delay recently? Is there any other way to escalate this issue or contact support directly to get my account activated? I have attached my invoice for reference. Any advice or help from the Apple team would be greatly appreciated! Thank you.
0
0
14
20h
Charged twice for Apple Developer Program, membership still inactive, no response from support
Hello, I’m looking for help with my Apple Developer Program enrollment. I was charged twice for the Apple Developer Program, but my membership is still not active. I have already contacted Apple Developer Support multiple times and have not received a response. Current support case IDs: 102858984144 102856097291 Timeline: First support requests were submitted on March 30, 2026 Another enrollment-related request was submitted on April 2, 2026 As of today, there has been no reply and my membership is still inactive What I need: Confirmation of the status of both payments Activation of my Apple Developer Program membership Refund of the duplicate charge if both payments were successfully captured I can provide masked order numbers and payment proof if needed. If anyone from Apple staff is able to review or escalate this case, I would greatly appreciate it. Thank you.
0
0
31
20h
Solving AVFoundation FigCaptureSourceRemote err=-17281 on iOS 26 — reliable workaround for repeated camera initialization
While working on a heart rate measurement app (photoplethysmography via camera), we faced systematic err=-17281 (FigCaptureSourceRemote) issues on real devices starting from iOS 17+, and the problem became more noticeable after iOS 26. The error often appeared during AVCaptureSession initialization or when restarting capture, especially under high frame rates (30-60 FPS) and frequent foreground/background transitions. Root cause (our understanding): Camera hardware/session not fully released after previous use Race conditions between session teardown and new setup Changes in AVFoundation capture pipeline in recent iOS versions Our solution: Instead of blocking delays, we implemented asynchronous retry logic with explicit hardware readiness check via AVCaptureDevice.lockForConfiguration().
0
0
17
20h
Payment processed 18 days ago, but Developer Program still not activated
Hi everyone, I’m looking for some advice or assistance regarding my Apple Developer Program enrollment. I completed my purchase and paid the $99 fee back on March 5th. Today is March 23rd, and my account is still not activated. It has been 18 days of total silence. I have already sent multiple follow-up emails to Apple Support, but I haven't received a single response. My payment was successfully processed, but I haven't received any confirmation or activation emails since then. Here are my transaction details: Invoice Number: MC55225030 Web Order Number: D009495884 Sales Order Number: AEU2369279 Has anyone else experienced such a long delay recently? Is there any other way to escalate this issue besides the standard contact form? Any help would be greatly appreciated. Thanks!
5
2
170
20h
Developer Program Payment Issues
Hello Everyone and @Apple Developer Support , I subscribed to the Apple Developer Program today, April 5th, 2026. The payment has already been charged to my bank account, but my account still shows the status “Purchase your membership. To continue your enrollment, complete your purchase now. Your purchase may take up to 48 hours to process.” In my naivety, I clicked it again, assuming the payment hadn’t gone through. As a result, I’ve now paid for the membership twice and been billed twice. Thanks in advance for your help and feedback! Gibril
0
0
11
21h
Please Help, $343 proceeds but only $258 paid, what explains the gap?
Hi everyone Please i need someone to explain this, I wanted to ask if anyone has experienced something similar with their payments. In March, in App Store Connect → Trends → Proceeds, I can see that my total proceeds are $343. However, in Payments and Financial Reports, Apple shows that they will pay me only $258 USD. From what I understand, taxes and Apple’s commission are already deducted when calculating proceeds, so I’m confused about why there is still such a big difference between the proceeds amount and the final payment. Has anyone faced this before or knows what could explain this gap? Thanks in advance for your help!
0
0
69
21h
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in "In Review" status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to "In Review" on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
2
1
80
21h
Acceptable level of obfuscation for App Review
New member here, please be gentle :) I am getting ready for App Review for my first iOS app, and I am curious if ANY level of obfuscation is allowed? Say I had a drone controller App, I might have something like this: struct Drone{ var name : String var forwardVelocity : Double var lateralVelocity : Double var verticalVelocity : Double var receivedSignalStrength : Int var rssThreshhold : Int var gpsCoordinates : Data func reverseCourse(){ //do a 180 //... } } func onUpdateReceivedSignalStength(drone:Drone){ if drone.receivedSignalStrength < drone.rssThreshhold{ drone.reverseCourse() } } But I don't really want to make it easy for someone to pull the strings from the binaries and try and copy my work. I realize it's pretty much inevitable, but it seems sensible to protect my IP as much as I can. Is something like this acceptable? struct D{ //obfuscated Drone var parameter1 : String //name var parameter2 : Double //forwardVelocity var parameter3 : Double //lateralVelocity var parameter4 : Double //verticalVelocity var parameter5 : Int //receivedSignalStength var parameter6 : Int //rssThreshhold var parameter7 : Data //gpsCoordinates func funcSeven(){ //do a 180 //... } } func funcSix(d:D){ //check if signal strength requires a course reversal if d.parameter5 < d.parameter6{ // signal strength less than threshhold d.funcSeven() //reverse course } } The comments make it clear what the similarly-named parameters are doing, and what the functions do. I fully understand that something like the below is a no-no, just writing it made my eyes bleed: struct DDF{ var SXR : String var KYV : Double var GTC : Double var DKY : Double var ENY : Int var WKN : Int var DJV : Data func BDO(){ //do a 180 //... } } func PUL(KHY:DDF){ if KHY.ENY < KHY.WKN{ KHY.BDO() } } Is there any level of IP protection through obscurity that is acceptable? I realize that the more genericized the variable and function names are, the harder it is to debug, but that might be an acceptable trade-off against IP protection. To be clear, my app isn't anything to do with drones, this was just a vehicle to ask the question with. My code isn't currently at all obfuscated, everything is in clear terms, but I am wondering if I could/should obfuscate the critical parts before App Review and release? The reason for my concern is that a key feature of the app is something very novel, and I have filed a patent application for it. The patent (if granted) won't be granted for 18-24 months, so anything I can do to protect the IP seems like the right thing to do. As a complete newcomer to releasing Apps, I have no experience at all, so I would be grateful for any help/steers from those that do have experience in trying to protect their IP while not making life difficult for the App Review team. Thanks in advance! 6502A
2
0
1.7k
21h
Unable to accept new developer program license agreement
I see a yellow banner on my App Store Connect page with the following message: Apple Developer Program License Agreement Updated The updated Apple Developer Program License Agreement needs to be reviewed. In order to update your existing apps and submit new apps to the App Store, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website." I am the account owner and I don't see any option to accept the license agreement. I see that the last agreement was signed on 13th December 2021 and it is accepted. I don't see any other agreements anywhere. I am unable to release any apps due to this issue. Does anyone know how to resolve this?
3
0
900
21h
The Problem with TestLight
I successfully registered an account a few days ago and tested the app internally, but when I published the link, the application automatically expired. When I submitted it again, I received the message: "There was an error processing your request. Please try again later." I have contacted support but have not received a response. Case ID: 102861441465
Replies
0
Boosts
0
Views
20
Activity
18h
Apple Swift Replacing Python
This YouTube video is very interesting, discussing Swift's power and its potential to replace Python. Here is the link. https://youtu.be/6ZGlseSqar0?si=pzZVq9FKsveca4kA
Replies
0
Boosts
0
Views
62
Activity
18h
popoverTips don't display for toolbar menu buttons in iOS 26.1
[Also submitted as FB20756013] A popoverTip does not display for toolbar menu buttons in iOS 26.1 (23B5073a). The same code displays tips correctly in iOS 18.6. The issue occurs both in the simulator and on a physical device. Repro Steps Build and run the Sample Code below on iOS 26.1. Observe that the popoverTip does not display. Repeat on iOS 18.6 to confirm expected behavior. Expected popoverTips should appear when attached to a toolbar menu button, as they do in iOS 18.6. Actual No tip is displayed on iOS 26.1. System Info macOS 15.7.1 (24G231) Xcode 26.1 beta 3 (17B5045g) iOS 26.1 (23B5073a) Screenshot Screenshot showing two simulators side by side—iOS 18.6 on the left (tip displayed) and iOS 26.1 on the right (no tip displayed). Sample code import SwiftUI import TipKit struct PopoverTip: Tip { var title: Text { Text("Menu Tip") } var message: Text? { Text("This tip displays on iOS 18.6, but NOT on iOS 26.1.") } } struct ContentView: View { var tip = PopoverTip() var body: some View { NavigationStack { Text("`popoverTip` doesn't display on iOS 26.1 but does in iOS 18.6") .padding() .toolbar { ToolbarItem(placement: .topBarTrailing) { Menu { Button("Dismiss", role: .cancel) { } Button("Do Nothing") { } } label: { Label("More", systemImage: "ellipsis") } .popoverTip(tip) } } .navigationTitle("Popover Tip Issue") .navigationBarTitleDisplayMode(.inline) } } }
Replies
3
Boosts
3
Views
355
Activity
20h
URGENT: Developer Program Expired – No Renewal Option – App Removed from App Store
Hello, We are currently experiencing a serious issue with our Apple Developer Program membership. Our membership has expired, but there is no option to renew the membership anywhere: Not on the Apple Developer website Not in the Apple Developer app Attempting to start enrollment again redirects to the main page Account details: Team ID: RZR56J4QQ8 Organization: E. V. I. ELECTRIC CARS LTD Role: Account Holder Because of this issue: All App Store agreements show as expired Our app has been removed from the App Store We are currently unable to restore service to users We already opened a Developer Support ticket about a week ago, but have not received any response. This is causing business impact, and we cannot find any way to trigger the renewal flow. Has anyone experienced this issue before, where the Renew Membership button does not appear at all? If anyone from Apple Developer Support / Apple Staff is able to assist or escalate this issue, it would be greatly appreciated. Thank you.
Replies
3
Boosts
0
Views
46
Activity
20h
App stuck on “Ready for Distribution” – Trader status not provided / DSA in review
Hi, My app status is currently “Ready for Distribution”, but it still hasn’t appeared on the App Store and I’m not sure what is blocking the release. In App Store Connect, I have already completed: • Agreements, Tax, and Banking (all active) • Pricing and Availability (countries selected) • Automatic release is enabled However: • My Digital Services Act (DSA) status is still “In Review” • I am also in the process of changing my account from Individual to Organization At this point, I’m not sure if the delay is caused by DSA review, account type change, or something else. Has anyone experienced a similar situation? Is there anything else I should check or complete to make sure the app goes live? Apple ID: 6760753842 Thank you.
Replies
2
Boosts
0
Views
62
Activity
20h
Digital Services Act: In Review for 14 days already.
Hi all, I was wondering if someone could provide more information about the Digital Services Act review process. I haven’t been able to find any details online, and I haven’t received a response to my support requests (it has been 9 days so far). I submitted the requested Digital Services Act information on February 27, but I haven’t received any update or automated confirmation email. The request is still visible under business agreements in my Apple Store Connect account. Does anyone know how long this review typically takes? Or whether I should contact support through a different channel? Thank you in advance!
Replies
7
Boosts
4
Views
249
Activity
20h
Apple Developer Program paid on March 31 but still not activated - No response from Support
Hi everyone, I am writing to seek help regarding my Apple Developer Program enrollment. I successfully paid the $99 USD enrollment fee on March 31, 2026. I received the official invoice (Web Order Number: D009560930), and my credit card was successfully charged. However, as of today, my developer account is still pending and has not been activated. I have already sent two separate emails to Apple Developer Support requesting assistance over the past few days, but I have not received any response or update from them yet. Has anyone experienced a similar delay recently? Is there any other way to escalate this issue or contact support directly to get my account activated? I have attached my invoice for reference. Any advice or help from the Apple team would be greatly appreciated! Thank you.
Replies
0
Boosts
0
Views
29
Activity
20h
Still in “Waiting for Review” despite multiple support cases and an accepted expedited review
Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.
Replies
0
Boosts
0
Views
20
Activity
20h
SwiftData document-based app crashes on undo/redo with autosaveEnabled
Overview I'm developing a document-based app for macOS using SwiftData. When I undo/redo changes using Command-Z/ Command-Shift-Z, the app randomly crashes with the following error: SwiftData/BackingData.swift:425: Fatal error: Failed to retrieve the identifier for \ChildItem.parentItem from KnownKeysDictionary:KnownKeysMap: ["parentItem": 2, "isModified": 1, "index": 0] values: [Optional(0), Optional(false), Optional(DocumentTest.ParentItem)] SwiftData._KKMDBackingData<DocumentTest.ChildItem> And sometimes, instead of the app crashing, my created @Model objects simply disappear. They do not reappear in the @Query on undo/redo. Both of these issues go away when I set modelContext.autosaveEnabled = false The issues are occurring with Xcode 26.4 (17E192) and macOS Tahoe 26.4 (25E246). I have modified the macOS Document App project template to showcase the issue. The project, along with a screen recording of the crash, can be downloaded from here: https://drive.google.com/drive/folders/1aDO34QleTm_rB9BuvVGjzzAP6jDXOc-o?usp=share_link Has anyone else experienced this? I'd like to know if this is a bug in the autosave feature of SwiftData and if I should file a bug report via Feedback Assistant. Steps to Reproduce To recreate the issue, follow these steps: Download and extract the "Xcode Project.zip" file linked above. Open the extracted "DocumentTest" project in Xcode. Build and run the "DocumentTest" app. In the document selection window, click "New Document" at the bottom-left. In the app, click the "+" button at the top-right to add a ParentItem with ChildItems. Click on the added ParentItem's button to modify one of its ChildItems. Repeat steps 5–6 until you have 5 ParentItems with a modified ChildItem. Press Command-Z 10 times to undo all the changes. Press Command-Shift-Z 10 times to redo all the changes. Repeat steps 8–9 until either the app crashes or some of the 5 ParentItems go missing in the list (you may have to repeat them 10–20 times before the issue occurs). If you change line 43 of ContentView.swift to modelContext.autosaveEnabled = false and repeat the same steps above, the app will not crash and no ParentItems will go missing. Code ParentItem Model @Model final class ParentItem { var timestamp: Date @Relationship( deleteRule: .cascade, inverse: \ChildItem.parentItem ) var childItems: [ChildItem] = [] init(timestamp: Date) { self.timestamp = timestamp } } ChildItem Model @Model final class ChildItem { var index: Int var isModified = false var parentItem: ParentItem? init(index: Int) { self.index = index } } Creating, Inserting, and Linking ParentItem and ChildItem // Create and insert ParentItem let newParentItem = ParentItem( timestamp: Date() ) modelContext.insert(newParentItem) // Create and insert ChildItems var newChildItems: [ChildItem] = [] for index in 0..<Int.random(in: 2...8) { let newChildItem = ChildItem(index: index) newChildItems.append(newChildItem) modelContext.insert(newChildItem) } /* Establish relationship between ParentItem and ChildItems */ newParentItem.childItems = newChildItems Modifying ChildItem let firstChildItem = parentItem.childItems .sorted(by: { $0.index < $1.index }).first if let firstChildItem, !firstChildItem.isModified { firstChildItem.isModified = true }
Replies
0
Boosts
0
Views
54
Activity
20h
Still in “Waiting for Review” despite multiple support cases and an accepted expedited review
Hello, I am posting here to ask whether anyone has recently experienced a similar situation. My app has remained in “Waiting for Review” for an unusually long time. Timeline: The initial submission stayed in “Waiting for Review” for about 10 days I assumed it might be related to a temporary queue or system issue, so I canceled that submission and resubmitted The current submission was resubmitted on March 19, 2026 It is still showing “Waiting for Review” I have contacted Apple through multiple support cases regarding this issue. Some of those cases have not received a response, and despite these inquiries, there has still been no visible review activity. In addition, I submitted an expedited review request on March 17, 2026. Later, on March 31, 2026, I received a response from Apple Developer Support confirming that the expedited review request had been accepted and that the review should begin shortly. However, even after that response, the submission still remains in “Waiting for Review,” and there has been no visible change indicating that the actual review has started. For reference, the related support case IDs are: 102846840976 102853198849 I have also already reviewed and updated the relevant account-side items, including agreements/contracts and related App Store Connect requirements, and I do not see any visible issue on my side. Current status: No rejection No “In Review” status No visible error in App Store Connect At this point, I am trying to understand whether: this is currently a known review queue delay, it is normal for an accepted expedited review to remain in “Waiting for Review” for this long, or there may be some hidden submission or account issue that does not appear in App Store Connect. If anyone has experienced a similar situation recently, I would appreciate hearing whether the review eventually started on its own or whether any additional action was required. Thank you.
Replies
0
Boosts
0
Views
17
Activity
20h
Apple Developer Program paid on March 31 but still not activated - No response from Support
Hi everyone, I am writing to seek help regarding my Apple Developer Program enrollment. I successfully paid the $99 USD enrollment fee on March 31, 2026. I received the official invoice (Web Order Number: D009560930), and my credit card was successfully charged. However, as of today, my developer account is still pending and has not been activated. I have already sent two separate emails to Apple Developer Support requesting assistance over the past few days, but I have not received any response or update from them yet. Has anyone experienced a similar delay recently? Is there any other way to escalate this issue or contact support directly to get my account activated? I have attached my invoice for reference. Any advice or help from the Apple team would be greatly appreciated! Thank you.
Replies
0
Boosts
0
Views
14
Activity
20h
Charged twice for Apple Developer Program, membership still inactive, no response from support
Hello, I’m looking for help with my Apple Developer Program enrollment. I was charged twice for the Apple Developer Program, but my membership is still not active. I have already contacted Apple Developer Support multiple times and have not received a response. Current support case IDs: 102858984144 102856097291 Timeline: First support requests were submitted on March 30, 2026 Another enrollment-related request was submitted on April 2, 2026 As of today, there has been no reply and my membership is still inactive What I need: Confirmation of the status of both payments Activation of my Apple Developer Program membership Refund of the duplicate charge if both payments were successfully captured I can provide masked order numbers and payment proof if needed. If anyone from Apple staff is able to review or escalate this case, I would greatly appreciate it. Thank you.
Replies
0
Boosts
0
Views
31
Activity
20h
Solving AVFoundation FigCaptureSourceRemote err=-17281 on iOS 26 — reliable workaround for repeated camera initialization
While working on a heart rate measurement app (photoplethysmography via camera), we faced systematic err=-17281 (FigCaptureSourceRemote) issues on real devices starting from iOS 17+, and the problem became more noticeable after iOS 26. The error often appeared during AVCaptureSession initialization or when restarting capture, especially under high frame rates (30-60 FPS) and frequent foreground/background transitions. Root cause (our understanding): Camera hardware/session not fully released after previous use Race conditions between session teardown and new setup Changes in AVFoundation capture pipeline in recent iOS versions Our solution: Instead of blocking delays, we implemented asynchronous retry logic with explicit hardware readiness check via AVCaptureDevice.lockForConfiguration().
Replies
0
Boosts
0
Views
17
Activity
20h
Payment processed 18 days ago, but Developer Program still not activated
Hi everyone, I’m looking for some advice or assistance regarding my Apple Developer Program enrollment. I completed my purchase and paid the $99 fee back on March 5th. Today is March 23rd, and my account is still not activated. It has been 18 days of total silence. I have already sent multiple follow-up emails to Apple Support, but I haven't received a single response. My payment was successfully processed, but I haven't received any confirmation or activation emails since then. Here are my transaction details: Invoice Number: MC55225030 Web Order Number: D009495884 Sales Order Number: AEU2369279 Has anyone else experienced such a long delay recently? Is there any other way to escalate this issue besides the standard contact form? Any help would be greatly appreciated. Thanks!
Replies
5
Boosts
2
Views
170
Activity
20h
Developer Program Payment Issues
Hello Everyone and @Apple Developer Support , I subscribed to the Apple Developer Program today, April 5th, 2026. The payment has already been charged to my bank account, but my account still shows the status “Purchase your membership. To continue your enrollment, complete your purchase now. Your purchase may take up to 48 hours to process.” In my naivety, I clicked it again, assuming the payment hadn’t gone through. As a result, I’ve now paid for the membership twice and been billed twice. Thanks in advance for your help and feedback! Gibril
Replies
0
Boosts
0
Views
11
Activity
21h
Please Help, $343 proceeds but only $258 paid, what explains the gap?
Hi everyone Please i need someone to explain this, I wanted to ask if anyone has experienced something similar with their payments. In March, in App Store Connect → Trends → Proceeds, I can see that my total proceeds are $343. However, in Payments and Financial Reports, Apple shows that they will pay me only $258 USD. From what I understand, taxes and Apple’s commission are already deducted when calculating proceeds, so I’m confused about why there is still such a big difference between the proceeds amount and the final payment. Has anyone faced this before or knows what could explain this gap? Thanks in advance for your help!
Replies
0
Boosts
0
Views
69
Activity
21h
App Stuck in “In Review'' status
Hi everyone, My app has been stuck in "In Review" status for over 20 days with no updates. I submitted the app on March 1, 2026, the status changed to "In Review" on March 4, 2026, and after that no changes. App ID: 6755649144 I also reached out to Apple Developer Support on March 15 but haven't received any response. Support Case ID: 102845096494 Could someone from App Review please take a look? Also any advice on how to move things forward would be appreciated. Thank you!
Replies
2
Boosts
1
Views
80
Activity
21h
Acceptable level of obfuscation for App Review
New member here, please be gentle :) I am getting ready for App Review for my first iOS app, and I am curious if ANY level of obfuscation is allowed? Say I had a drone controller App, I might have something like this: struct Drone{ var name : String var forwardVelocity : Double var lateralVelocity : Double var verticalVelocity : Double var receivedSignalStrength : Int var rssThreshhold : Int var gpsCoordinates : Data func reverseCourse(){ //do a 180 //... } } func onUpdateReceivedSignalStength(drone:Drone){ if drone.receivedSignalStrength < drone.rssThreshhold{ drone.reverseCourse() } } But I don't really want to make it easy for someone to pull the strings from the binaries and try and copy my work. I realize it's pretty much inevitable, but it seems sensible to protect my IP as much as I can. Is something like this acceptable? struct D{ //obfuscated Drone var parameter1 : String //name var parameter2 : Double //forwardVelocity var parameter3 : Double //lateralVelocity var parameter4 : Double //verticalVelocity var parameter5 : Int //receivedSignalStength var parameter6 : Int //rssThreshhold var parameter7 : Data //gpsCoordinates func funcSeven(){ //do a 180 //... } } func funcSix(d:D){ //check if signal strength requires a course reversal if d.parameter5 < d.parameter6{ // signal strength less than threshhold d.funcSeven() //reverse course } } The comments make it clear what the similarly-named parameters are doing, and what the functions do. I fully understand that something like the below is a no-no, just writing it made my eyes bleed: struct DDF{ var SXR : String var KYV : Double var GTC : Double var DKY : Double var ENY : Int var WKN : Int var DJV : Data func BDO(){ //do a 180 //... } } func PUL(KHY:DDF){ if KHY.ENY < KHY.WKN{ KHY.BDO() } } Is there any level of IP protection through obscurity that is acceptable? I realize that the more genericized the variable and function names are, the harder it is to debug, but that might be an acceptable trade-off against IP protection. To be clear, my app isn't anything to do with drones, this was just a vehicle to ask the question with. My code isn't currently at all obfuscated, everything is in clear terms, but I am wondering if I could/should obfuscate the critical parts before App Review and release? The reason for my concern is that a key feature of the app is something very novel, and I have filed a patent application for it. The patent (if granted) won't be granted for 18-24 months, so anything I can do to protect the IP seems like the right thing to do. As a complete newcomer to releasing Apps, I have no experience at all, so I would be grateful for any help/steers from those that do have experience in trying to protect their IP while not making life difficult for the App Review team. Thanks in advance! 6502A
Replies
2
Boosts
0
Views
1.7k
Activity
21h
developer pending
i payment on 6th SEP,its still pending ,cant finish the purchase
Replies
6
Boosts
0
Views
1.1k
Activity
21h
Unable to accept new developer program license agreement
I see a yellow banner on my App Store Connect page with the following message: Apple Developer Program License Agreement Updated The updated Apple Developer Program License Agreement needs to be reviewed. In order to update your existing apps and submit new apps to the App Store, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website." I am the account owner and I don't see any option to accept the license agreement. I see that the last agreement was signed on 13th December 2021 and it is accepted. I don't see any other agreements anywhere. I am unable to release any apps due to this issue. Does anyone know how to resolve this?
Replies
3
Boosts
0
Views
900
Activity
21h