Search results for

“iPhone 16 pro”

80,714 results found

Post

Replies

Boosts

Views

Activity

Reply to Crashed: com.apple.CFNetwork.LoaderQ
Crash location: Crashed thread:com.apple.CFNetwork.LoaderQ Crash framework:libquic.dylib Crash function: quic_fc_service_pending_send_data + 360 Crash stack: Crashed: com.apple.CFNetwork.LoaderQ 0 libquic.dylib 0x36d84 quic_fc_service_pending_send_data + 360 1 libquic.dylib 0x3bcf0 _quic_conn_outbound_stopping_block_invoke 2 + 28 2 Network 0x23e428 nw_protocol_instance_access_flow_state + 136 3 libquic.dylib 0x3bcb8 __quic_conn_outbound_stopping_block_invoke + 744 4 libquic.dylib 0x3b754 quic_conn_outbound_stopping + 168 5 Network 0x3559b4 nw_protocol_implementation_finalize_output_frames + 576 6 Network 0x67308 nw_flow_service_writes + 5264 7 Network 0x58944 nw_endpoint_handler_add_write_request + 4860 8 Network 0x57880 nw_endpoint_handler_add_write_request + 568 9 Network 0x575a4 nw_connection_add_write_request_on_queue + 228 10 Network 0x5c314 nw_connection_async_if_needed + 76 11 Network 0x573c4 nw_connection_add_write_request + 312 12 Network 0x56868 nw_connection_send + 516 13 CFNetwork 0x66b30 NWIOConn
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
Thanks for your reply. I have already filed a report through Feedback Assistant. Case-ID: 18609190 (Apple DTS incident) Feedback ID: 22081725 The issue was submitted on Feb 28, 2026, but so far there has been no update in Feedback Assistant. The problem is still reproducible in Xcode 26.3 with Release (-O) builds when targeting iOS 16/17/18. Could you please help check whether this Feedback has been routed to the appropriate Swift/Xcode engineering team, and whether there is any information about which future Xcode version might include a fix? Thank you very much for your help.
2w
Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new SwiftUI App project using Xcode 26.3. Leave all project settings
3
0
149
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise. The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep
2
0
93
2w
Problem testing SignificantAppUpdateTopic with AskCenter
Hi, I have a problem testing sending a significantAppUpdateTopic request with AskCenter. Sending a request of type CommunicationTopic works correctly: let question = PermissionQuestion( handle: .init(value: description, kind: .custom) ) try await AskCenter.shared.ask(question, in: viewController) Receiving the response from the guardian also works correctly for a question of type CommunicationTopic. However, after changing the request from CommunicationTopic to significantAppUpdateTopic, I get the following cryptic error: Error returned from daemon: Error Domain=com.apple.accounts Code=7 (null) (and nothing happens). This is the code I am using: let topic = SignificantAppUpdateTopic(description: description) let question = PermissionQuestion(significantAppUpdateTopic: topic) try await AskCenter.shared.ask(question, in: viewController) These are my settings: I created a child account within a family group the child's age in the family group is set to 15 I am the group organizer I am not located in Texas or the
1
0
122
2w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be wait
4
0
234
2w
1 Month anniversary of "waiting for review"
Just want to celebrate with you all that today, is the 1 month anniversary of my app waiting for review. Submitted on Feb 12th, been waiting ever since. App ID is 6758779640 - not that it matters, because it really seems that no one at Apple is listening. So, one month of waiting time, on a £79 developer fee... that's £6.58 wasted ;) Phone support already requested an expedited review. Nothing happens. This is a joke. Actually now looking, as an Apple first user, and on-off developer for 25 years, to port all my current in progress work to Android and launch there first instead.
4
0
187
2w
Crashed: com.apple.CFNetwork.LoaderQ
com.apple.main-thread 0 StarMaker 0x5c40854 _isPlatformVersionAtLeast.cold.2 + 4425680980 1 StarMaker 0x526d278 -[FPRScreenTraceTracker displayLinkStep] + 191 (FPRScreenTraceTracker.m:191) 2 QuartzCore 0xbe924 CA::Display::DisplayLinkItem::dispatch(CA::SignPost::Interval<(CA::SignPost::CAEventCode)835322056>&) + 64 3 QuartzCore 0x9bf38 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 880 4 QuartzCore 0xaf770 CA::Display::DisplayLink::dispatch_deferred_display_links(unsigned int) + 360 5 UIKitCore 0x7dee4 _UIUpdateSequenceRunNext + 128 6 UIKitCore 0x7d374 schedulerStepScheduledMainSectionContinue + 60 7 UpdateCycle 0x1560 UC::DriverCore::continueProcessing() + 84 8 CoreFoundation 0x164cc __CFMachPortPerform + 168 9 CoreFoundation 0x460b0 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 60 10 CoreFoundation 0x45fd8 __CFRunLoopDoSource1 + 508 11 CoreFoundation 0x1dc1c __CFRunLoopRun + 2168 12 CoreFoundation 0x1ca6c _CFRunLoopRunSpecificWithO
5
0
203
2w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
2w
Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
Platform: macOS 26.3.1, M5 Pro MacBook Pro Framework: CoreWLAN Affected applications: NetViews, Air Tool 2, and our own tooling — appears to be specific to the new Wi-Fi 7 hardware Hardware Card Type: chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Firmware: Jan 27 2026 21:18:32 version XBS_BUILD_TAG GIT_DESCRIBE FWID chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Driver: IO80211_driverkit-1540.16 IO80211_driverkit-1540.16 Jan 27 2026 Background Both issues described below were working correctly on macOS 26 with previous-generation hardware. The regression is specific to the Wi-Fi 7 card shipping in the M5 Pro MacBook Pro. This is not an OS regression — it is a hardware/driver/firmware compatibility issue with the new card under macOS 26. Issue 1: disassociate() + tcpdump/Wireshark -I no longer enters monitor mode Previously, the standard
5
0
187
2w
App stuck in “Waiting for Review” for over a month – multiple contacts with Apple but no progress
Hello everyone, I would like to ask if other developers are currently experiencing unusually long App Review delays for new apps. Here is my timeline for this app (Apple ID: 6758083858): Jan 22, 2026: Initial build submitted Jan 22 – Mar 7, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 7, 2026: Cancelled and resubmitted a new build Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent follow-up emails regarding the delay Contacted Apple support by phone and asked them to leave a message for the App Review team Each time I was told that the situation would be checked or that the review team would look into it. However, it has now been about two weeks since my last contact and there has been no update or progress. While browsing the Developer Forums, I also noticed that many recent posts seem to describe the
3
0
247
2w
CarPlay: CPListImageRowItem images and CPNowPlayingTemplate buttons occasionally not displaying (requires device reboot)
Device: iPhone 17 Pro Max iOS version: iOS 26.3 CarPlay type: Wired We are encountering two intermittent UI issues in CarPlay when running our music application. The problems occur occasionally and cannot be recovered without restarting the device. Issue 1: CPListImageRowItem image not displaying On the CarPlay home page, some images occasionally fail to appear. Implementation details: The list is updated using CPListTemplate.updateSections. Each item is a CPListImageRowItem. On iOS versions below 26, images are updated using updateImages. On iOS 26, images are provided through CPListImageRowItem.elements, where each element is a CPListImageRowItemRowElement. Observed behavior: Logs confirm that the data is correctly provided. However, in failing cases the CPListImageRowItemRowElement appears with both title and subtitle equal to nil. The image is not rendered in the UI even though the item exists. Issue 2: Now Playing bottom buttons occasionally missing On the Now Playing screen, the bottom
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
69
2w
App in "Waiting for Review" for 32 days — two escalations with no resolution
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 subm
5
0
203
2w
Reply to Crashed: com.apple.CFNetwork.LoaderQ
Crash location: Crashed thread:com.apple.CFNetwork.LoaderQ Crash framework:libquic.dylib Crash function: quic_fc_service_pending_send_data + 360 Crash stack: Crashed: com.apple.CFNetwork.LoaderQ 0 libquic.dylib 0x36d84 quic_fc_service_pending_send_data + 360 1 libquic.dylib 0x3bcf0 _quic_conn_outbound_stopping_block_invoke 2 + 28 2 Network 0x23e428 nw_protocol_instance_access_flow_state + 136 3 libquic.dylib 0x3bcb8 __quic_conn_outbound_stopping_block_invoke + 744 4 libquic.dylib 0x3b754 quic_conn_outbound_stopping + 168 5 Network 0x3559b4 nw_protocol_implementation_finalize_output_frames + 576 6 Network 0x67308 nw_flow_service_writes + 5264 7 Network 0x58944 nw_endpoint_handler_add_write_request + 4860 8 Network 0x57880 nw_endpoint_handler_add_write_request + 568 9 Network 0x575a4 nw_connection_add_write_request_on_queue + 228 10 Network 0x5c314 nw_connection_async_if_needed + 76 11 Network 0x573c4 nw_connection_add_write_request + 312 12 Network 0x56868 nw_connection_send + 516 13 CFNetwork 0x66b30 NWIOConn
Replies
Boosts
Views
Activity
2w
Reply to Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
Thanks for your reply. I have already filed a report through Feedback Assistant. Case-ID: 18609190 (Apple DTS incident) Feedback ID: 22081725 The issue was submitted on Feb 28, 2026, but so far there has been no update in Feedback Assistant. The problem is still reproducible in Xcode 26.3 with Release (-O) builds when targeting iOS 16/17/18. Could you please help check whether this Feedback has been routed to the appropriate Swift/Xcode engineering team, and whether there is any information about which future Xcode version might include a fix? Thank you very much for your help.
Replies
Boosts
Views
Activity
2w
Swift compiler fails in Release (-O) when using generic ObservableObject with @Published on iOS < 26 in Xcode 26.3
When building a SwiftUI project in Xcode 26.3, Swift compilation fails in the Release configuration with Optimization Level set to -O, when the iOS deployment target is lower than iOS 26 (e.g. iOS 16, 17, or 18). The failure occurs when using a generic class conforming to ObservableObject that contains a @Published property. The same code: Compiles successfully in Xcode 16.3 (Release, -O) with iOS 16/17/18 Compiles successfully in Xcode 26.x when the deployment target is set to iOS 26 Compiles successfully in Xcode 26.x Debug configuration (-Onone) Compiles successfully in Xcode 26.x Release when optimization is disabled (-Onone) However, in Xcode 26.3, the build consistently fails in Release (-O) when targeting iOS 16, 17, or 18. This appears to be a Swift compiler optimization issue related to generics, ObservableObject, @Published, and back-deployment to iOS versions prior to iOS 26. STEPS TO REPRODUCE Create a new SwiftUI App project using Xcode 26.3. Leave all project settings
Replies
3
Boosts
0
Views
149
Activity
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise. The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep
Replies
2
Boosts
0
Views
93
Activity
2w
Reply to MacOS 26.4 beta “Failed to prepare software update”
I have the same issue on my Macbook Pro M4 I tried the update in safe mode without success. Very frustrating and the first update failure in over 10 years.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
2w
Problem testing SignificantAppUpdateTopic with AskCenter
Hi, I have a problem testing sending a significantAppUpdateTopic request with AskCenter. Sending a request of type CommunicationTopic works correctly: let question = PermissionQuestion( handle: .init(value: description, kind: .custom) ) try await AskCenter.shared.ask(question, in: viewController) Receiving the response from the guardian also works correctly for a question of type CommunicationTopic. However, after changing the request from CommunicationTopic to significantAppUpdateTopic, I get the following cryptic error: Error returned from daemon: Error Domain=com.apple.accounts Code=7 (null) (and nothing happens). This is the code I am using: let topic = SignificantAppUpdateTopic(description: description) let question = PermissionQuestion(significantAppUpdateTopic: topic) try await AskCenter.shared.ask(question, in: viewController) These are my settings: I created a child account within a family group the child's age in the family group is set to 15 I am the group organizer I am not located in Texas or the
Replies
1
Boosts
0
Views
122
Activity
2w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be wait
Replies
4
Boosts
0
Views
234
Activity
2w
1 Month anniversary of "waiting for review"
Just want to celebrate with you all that today, is the 1 month anniversary of my app waiting for review. Submitted on Feb 12th, been waiting ever since. App ID is 6758779640 - not that it matters, because it really seems that no one at Apple is listening. So, one month of waiting time, on a £79 developer fee... that's £6.58 wasted ;) Phone support already requested an expedited review. Nothing happens. This is a joke. Actually now looking, as an Apple first user, and on-off developer for 25 years, to port all my current in progress work to Android and launch there first instead.
Replies
4
Boosts
0
Views
187
Activity
2w
Crashed: com.apple.CFNetwork.LoaderQ
com.apple.main-thread 0 StarMaker 0x5c40854 _isPlatformVersionAtLeast.cold.2 + 4425680980 1 StarMaker 0x526d278 -[FPRScreenTraceTracker displayLinkStep] + 191 (FPRScreenTraceTracker.m:191) 2 QuartzCore 0xbe924 CA::Display::DisplayLinkItem::dispatch(CA::SignPost::Interval<(CA::SignPost::CAEventCode)835322056>&) + 64 3 QuartzCore 0x9bf38 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 880 4 QuartzCore 0xaf770 CA::Display::DisplayLink::dispatch_deferred_display_links(unsigned int) + 360 5 UIKitCore 0x7dee4 _UIUpdateSequenceRunNext + 128 6 UIKitCore 0x7d374 schedulerStepScheduledMainSectionContinue + 60 7 UpdateCycle 0x1560 UC::DriverCore::continueProcessing() + 84 8 CoreFoundation 0x164cc __CFMachPortPerform + 168 9 CoreFoundation 0x460b0 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 60 10 CoreFoundation 0x45fd8 __CFRunLoopDoSource1 + 508 11 CoreFoundation 0x1dc1c __CFRunLoopRun + 2168 12 CoreFoundation 0x1ca6c _CFRunLoopRunSpecificWithO
Replies
5
Boosts
0
Views
203
Activity
2w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
Replies
Boosts
Views
Activity
2w
Monitor mode capture broken with Wi-Fi 7 (M5 Pro MacBook Pro) on macOS 26 - worked previously on same OS with older hardware
Platform: macOS 26.3.1, M5 Pro MacBook Pro Framework: CoreWLAN Affected applications: NetViews, Air Tool 2, and our own tooling — appears to be specific to the new Wi-Fi 7 hardware Hardware Card Type: chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Firmware: Jan 27 2026 21:18:32 version XBS_BUILD_TAG GIT_DESCRIBE FWID chip id: 0x11 api 1.2 firmware [Rev 72.11.260 N1B1 devFused=0] phy [17.1.17.0], core80211 [324.10.260 N1_silicon_b] Driver: IO80211_driverkit-1540.16 IO80211_driverkit-1540.16 Jan 27 2026 Background Both issues described below were working correctly on macOS 26 with previous-generation hardware. The regression is specific to the Wi-Fi 7 card shipping in the M5 Pro MacBook Pro. This is not an OS regression — it is a hardware/driver/firmware compatibility issue with the new card under macOS 26. Issue 1: disassociate() + tcpdump/Wireshark -I no longer enters monitor mode Previously, the standard
Replies
5
Boosts
0
Views
187
Activity
2w
App stuck in “Waiting for Review” for over a month – multiple contacts with Apple but no progress
Hello everyone, I would like to ask if other developers are currently experiencing unusually long App Review delays for new apps. Here is my timeline for this app (Apple ID: 6758083858): Jan 22, 2026: Initial build submitted Jan 22 – Mar 7, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 7, 2026: Cancelled and resubmitted a new build Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent follow-up emails regarding the delay Contacted Apple support by phone and asked them to leave a message for the App Review team Each time I was told that the situation would be checked or that the review team would look into it. However, it has now been about two weeks since my last contact and there has been no update or progress. While browsing the Developer Forums, I also noticed that many recent posts seem to describe the
Replies
3
Boosts
0
Views
247
Activity
2w
CarPlay: CPListImageRowItem images and CPNowPlayingTemplate buttons occasionally not displaying (requires device reboot)
Device: iPhone 17 Pro Max iOS version: iOS 26.3 CarPlay type: Wired We are encountering two intermittent UI issues in CarPlay when running our music application. The problems occur occasionally and cannot be recovered without restarting the device. Issue 1: CPListImageRowItem image not displaying On the CarPlay home page, some images occasionally fail to appear. Implementation details: The list is updated using CPListTemplate.updateSections. Each item is a CPListImageRowItem. On iOS versions below 26, images are updated using updateImages. On iOS 26, images are provided through CPListImageRowItem.elements, where each element is a CPListImageRowItemRowElement. Observed behavior: Logs confirm that the data is correctly provided. However, in failing cases the CPListImageRowItemRowElement appears with both title and subtitle equal to nil. The image is not rendered in the UI even though the item exists. Issue 2: Now Playing bottom buttons occasionally missing On the Now Playing screen, the bottom
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
1
Boosts
0
Views
69
Activity
2w
App in "Waiting for Review" for 32 days — two escalations with no resolution
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 subm
Replies
5
Boosts
0
Views
203
Activity
2w
Reply to MacOS 26.4 beta “Failed to prepare software update”
I am reciving the same issue on my m1 pro (MK183LL/A).
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
3w