Overview

Hello DTS team, the request review from StoreKit is not working in iOS 26.4 beta 3. I have filed a feedback (FB22157147). Sample code: import SwiftUI import StoreKit struct ContentView: View { @Environment(\.requestReview) private var requestReview @State private var count = 0 var body: some View { VStack { Button("Increase Count") { count += 1 } Text(count, format: .number) .font(.largeTitle) } .onChange(of: count) { if count == 3 { Task { try await Task.sleep(for: .seconds(2)) requestReview() print("Request Review triggered!") // On iPadOS 26.4 beta 2 & 3, requestReview() does not trigger any review system sheet when testing in Xcode 26.3 // Works on iOS 26.3.1 } } } } }

I’m interested in hearing what currently concerns other indie iOS developers, as 2026 feels both exciting and somewhat fragile to me, with the constant worry that an Apple account issue or unexpected rejection could undo years of hard work overnight. AI has made cloning apps easier than ever and even strong niches can quickly attract well funded competitors, so while I’m optimistic about building, these are the realities I often find myself thinking about.

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

Should you rely only on organic installs, or would a mix of strategies work better? Isn’t optimizing keywords and refining creatives essential for higher visibility? Would running Apple Search Ads not further amplify reach? And doesn’t encouraging strong reviews ultimately help in improving both ranking and credibility?

My app has been in "In Review" for 30 days now. I have e-mailed once with no reply and called twice with no helpful information. I have also requested a Expedited Review but that hasn't helped. If App Review could respond and help out in any way that would be greatly appreciated, thank you.

I am submitting my first macOS app for notarization and all submissions have been stuck at "In Progress" for over 24-36 hours. The notarytool log command returns "Submission log is not yet available" for all of them. App details: macOS menu bar app (Apple Silicon only, arm64) Signed with Developer ID Application certificate Hardened Runtime enabled Secure timestamp included No get-task-allow entitlement Team ID: 3426FSU868 Submission history: bd5a8bf3-809f-42d5-9ab3-1cb665e4dfa6 (Mar 3, 13:02 UTC) - Status: Invalid This was expected. It was a Debug build with get-task-allow and missing secure timestamp. c3e54eef-650e-41ba-ac8f-8948147cc7e1 (Mar 3, 13:06 UTC) - Status: In Progress (36+ hours) b6c4515a-93dd-417c-8956-158a73f62dee (Mar 3, 14:06 UTC) - Status: In Progress (35+ hours) 478b7e57-3492-46eb-98fb-04b52bff1f17 (Mar 4, 01:08 UTC) - Status: In Progress (24+ hours) Submissions 2-4 were all built with Release configuration, signed with Developer ID Application certificate, hardened runtime, and secure timestamp. The codesign output confirms correct signing: Authority=Developer ID Application: Waseem Khan (3426FSU868) Authority=Developer ID Certification Authority Authority=Apple Root CA I understand first-time submissions may go through in-depth analysis but it has been well over 24 hours for all three. Is there anything wrong with my submissions or is this expected? Any help would be appreciated.

I display the BackgroundLocationIndicator (blue/white bubble in status bar) in all my apps, that use background location service. Up to iOS 18 it allowed the user to tap on the bubble from within any other non fullscreen app and bring the app using the background location service to the foreground. In iOS26 this only works from the home screen. Is this intended behaviour or a bug ? If intended, please provide us with an option to allow the user to keep the pre iOS26 behavour. This was a quite convenient shortcut to jump directly to the locationservice using app.

One app submitted Feb 21st. The app is currently showing "Waiting for Review". It hasn’t been rejected and there hasn’t been any action taken yet. This is my first submission with this developer account, so I just want to confirm everything was submitted correctly and that I’m simply waiting on Apple’s review process. For anyone from Apple who might be able to look into it, the app details are: App name: Coop Keeper: Chore Cards SKU: com.lukaambros.coopkeeperchorecards Apple ID: 6759481708

Hey everyone, I need to vent and also ask for some advice because I’m starting to lose my mind here. I submitted a new build for my app 10 days ago, and it has been stuck in "Waiting for Review" ever since. Not "In Review," just waiting in the queue. The App ID is 6759559007 I get that Apple has millions of apps to sift through, but come on. The App Store is a core part of the iPhone experience, and having a review team that moves this slowly feels like a bottleneck that shouldn't exist in 2026. It’s especially frustrating because: There are no rejection messages, so I know it’s not a guideline issue. I have a planned marketing push that is now completely out of sync. There is zero transparency. The status just sits there mocking me. Any advice on how to actually get a human to look at this? Should I reject the binary and resubmit to "bump" it, or is that just sending me to the back of the line? Feeling pretty hopeless here. Any insights would be hugely appreciated. Thanks

My app has been stuck on "Waiting for Review" for a long time now and there has been absolutely no progress. It’s pretty frustrating considering the review time that’s usually mentioned is around 24–48 hours. SKU: com.igos.simonchace Apple ID: 6759446309

I am trying to upload an App Preview to App Store Connect for a iphone app,I created the preview as an "App Preview". When I try to upload the app preview I get the message " your app preview is too big". The preview is 30 sec. It is 6 MB in size. MP4 format. Who know how to change my app preview

I would like to renew my Apple Developer membership but I'm faced with this : I've filled the form and hit sent, but I didn't receive either a response or a receipt ; it's been multiple days. Is Apple ever going to respond ?

After reviewing the following Apple Technote, I have confirmed the statement below: https://aninterestingwebsite.com/documentation/technotes/tn3187-migrating-to-the-uikit-scene-based-life-cycle In the next major release following iOS 26, UIScene lifecycle will be required when building with the latest SDK; otherwise, your app won’t launch. While supporting multiple scenes is encouraged, only adoption of scene life-cycle is required. Based on the above, I would appreciate it if you could confirm the following points: Is my understanding correct that the term “latest SDK” refers to Xcode 27? Is it correct that an app built with the latest SDK (Xcode 27, assuming the above understanding is correct) will not launch without adopting the UIScene lifecycle, with no exceptions? Is it correct that an app built with Xcode 26 without UIScene lifecycle support will still launch without issues on an iPhone updated to iOS 27?

Looking for help with or to help with, due to the pending document enhancement, the Vibe Coders edition of cml editor. Also for more information on how to use the .mlkey whether or not my model is suppose to say IOs18 when I am planning to use it on Mac Apple Intelligence seems to think coreML is for iOS but are the capabilities extended when running NPU on the book? How to use this graph. coming in hot sorry. btw. there are 100s of feedback and crash reports sent in form me for additional info? I attached a image that might help with updating Tags

Hello everyone. I want to do navigationTitle (located on the top side on MacOS system) in LiquidGlass style. now my solution look like: just black rectangle. But i want like this: opacity and LiquidGlass. Like in Photo app in MacOS. Please help me, thank you in advance. My code: struct RootView: View { @Environment(\.horizontalSizeClass) var hSize var body: some View { if hSize == .regular { DesktopLayout() .navigationTitle("title") .toolbarBackground(.ultraThinMaterial, for: .automatic) } else { MobileLayout() } } }

I’m working with Reality Composer and noticed that images added directly to a scene appear significantly darker when viewed in AR. This seems different from how other objects in the scene respond to lighting, especially under varying real-world light conditions. Is this expected behavior? Are images treated with a different lighting model in Reality Composer? Is there any recommended way to get more consistent light response for image-based artworks?

Subject: Technical Report: Float32 Precision Ceiling & Memory Fragmentation in JAX/Metal Workloads on M3 To: Metal Developer Relations Hello, I am reporting a repeatable numerical saturation point encountered during sustained recursive high-order differential workloads on the Apple M3 (16 GB unified memory) using the JAX Metal backend. Workload Characteristics: Large-scale vector projections across multi-dimensional industrial datasets Repeated high-order finite-difference calculations Heavy use of jax.grad and lax.cond inside long-running loops Observation: Under these conditions, the Metal/MPS backend consistently enters a terminal quantization lock where outputs saturate at a fixed scalar value (2.0000), followed by system-wide NaN propagation. This appears to be a precision-limited boundary in the JAX-Metal bridge when handling high-order operations with cubic time-scale denominators. have identified the specific threshold where recursive high-order tensor derivatives exceed the numerical resolution of 32-bit consumer architectures, necessitating a migration to a dedicated 64-bit industrial stack. I have prepared a minimal synthetic test script (randomized vectors only, no proprietary logic) that reliably reproduces the allocator fragmentation and saturation behavior. Let me know if your team would like the telemetry for XLA/MPS optimization purposes. Best regards, Alex Severson Architect, QuantumPulse AI

Hello Apple Developer Community, I’m looking for advice regarding a prolonged App Store review that has been ongoing for some time now. Our mobile application was submitted to the App Store on Feb 19, 2026 at 7:06 AM, and since then the status has remained “Waiting for Review.” There has been no progress or change in status. Because review times are typically described as taking around 24–48 hours in many cases, the length of this delay has become concerning and somewhat unclear. At this point, I’m mainly trying to understand whether this is simply an unusually long queue or if there might be another issue affecting the review. We have not received any rejection, request for additional information, or communication related to the submission. App details: Apple ID: 6759366887 Summary of the situation: • Submission date: Feb 19, 2026 at 7:06 AM • Current status: Waiting for Review • No rejection or review notes received • No changes in status since submission I understand that review times can vary depending on workload and other factors. However, remaining in the queue for this length of time without any updates makes it difficult to understand whether everything in the submission is proceeding normally. If anyone in the community has experienced a similar situation or has insight into the current review queue, I would really appreciate any guidance, including: • Whether extended “Waiting for Review” times are common recently • If there are recommended steps to follow in cases like this • Whether contacting App Review or Developer Support again would be advisable Any advice or shared experience would be very helpful. Thank you in advance.

In my multiplatform SwiftUI document app, where should I implement undo? In the Views with Forms and Lists, Bindings, data classes or somewhere else? I am now implementing undo in Bindings and Lists, but I'm wondering if that's the right way to do it.

Hello everyone, I’m facing an issue with my app where it's stuck at the paywall screen because my app has been approved but my subscriptions are still "Waiting for Review". This prevents me from fetching the subscription options needed to display behind the paywall. I've resubmitted my app multiple times and also created tickets and used Feedback Assistant to report this issue, but I haven't received a resolution yet. Has anyone encountered a similar situation or have any suggestions on how to resolve this? My app is live, but without approved subscriptions, users can't access its full functionality. Any advice or insights would be greatly appreciated. Thank you.