We are an App Developer for past 16 years so have seen a lot happen with App Review over the years (even back when 2 month review times were the norm). However, we have all come to expect app review to take only 48 hours typically.
We submitted several macOS Tahoe updates in Feb all approved within 24 to 48 hours, but 2 updates submitted on 25th Feb are stuck in 'waiting for review'. Very strange indeed and checking this forum, it seems many other devs are having the same issue, but from way earlier than us.
Is this a known issue currently? I suspect their are different app review queues by region and maybe even app category and popularity of the app, but even accounting for all that, this is unusual. There seems to be no logic to which apps are approved same day vs those kept stuck in 'waiting for review'.
Overview
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Created
Is it somehow possible to get the transport layer (UDP and TCP) payload amounts for TLS or QUIC connections established via the Network framework? (From within the app itself that establishes the connections.)
I am currently using the ntstat.h kernel socket calls, but I hope there is a simpler solution.
With ntstat, I have not yet been able to observe a specific connection. I have to search for the connection I am looking in all (userspace) connections.
Hello. We've developed a compatibility engine for the App Store. We collect very detailed profile information from users and use this information to dynamically calculate compatibility scores with the help of AI, recommending users to each other. The app is newly completed and we don't have any real users yet. My questions are:
We are at the initial approval stage,
Should we submit a completely empty application, or will the reviewer account create accounts with matching genders?
Should we create one or more fake users?
We have profiles that we created as demos (to inspire users) and indicated with a badge as "demo"s, but these don't appear in the "Explore" section. Should we add these people to the explore section?
Assuming the people appearing in the explore section are demos, should the "request to meet" button be active for these demo content? Should it be possible to chat with demo people?
After the submission is approved, will we delete the fake people or remove the demo people from the Explore section again? Is this possible?
Which approach is correct to avoid being perceived as "fake content"?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store
App Review
App Store Connect
Custom Apps
Hi,
where i can change the company information? We have renamed our company and are moving to an other adress.
Topic:
Community
SubTopic:
Apple Developers
Hi,
where can i find my invoice for the subscription I pay yearly to apple?
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Hello,
I am seeing sever delay in app review completion of my app. The version I submitted for review is pending since Feb 15th. This is the first time it happened like this as earlier it was quicker.
I tried to contact apple through support email but have not received any update.
Any suggestions on what I can do?
Thank you.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Hello iOS developer community,
I submitted an app on App Store Connect on February 4, 2026, but I don't understand why, as of today (March 2, 2026), its status is still "Waiting for Review."
I have emailed Developer Support but only received the following automated reply: "Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible. Your case ID is 102824763035."
It has been over ten days, and I still haven’t received any official follow-up or updates from Apple regarding this issue.
What should I do now?
The email address I use for my Apple Developer account is
Hello iOS developer community,
I submitted an app on App Store Connect on February 4, 2026, but I don't understand why, as of today (March 2, 2026), its status is still "Waiting for Review."
I have emailed Developer Support but only received the following automated reply: "Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible. Your case ID is 102824763035."
It has been over ten days, and I still haven’t received any official follow-up or updates from Apple regarding this issue.
What should I do now?
Hi everyone
I would like to achieve having unidirectional relationships in my SwiftData project (which I believe is possible: https://developer.apple.com/documentation/updates/swiftdata?changes=_9) but I'm afraid I'm struggling to overcome the errors I'm experiencing.
For example, I have the following models:
@Model
final class Quota {
@Attribute(.unique) var id: UUID
var allowance: Int
@Relationship(inverse: nil) var fish: Fish
init(id: UUID = UUID(), fish: Fish, allowance: Int) {
self.id = id
self.fish = fish
self.allowance = allowance
}
}
@Model
final class Fish {
@Attribute(.unique) var id: Int
var name: String
init(id: Int, name: String) {
self.id = id,
self.name = name
}
}
However, when I attempt to save a quota as so:
let quota: Quota = .init(fish: Fish(id: 2, name: "Salmon"), allowance: 50)
modelContext?.insert(quota)
try save()
I keep getting the following error:
SwiftData.DefaultStore save failed with error: Error Domain=NSCocoaErrorDomain Code=1570 "%{PROPERTY}@ is a required value." UserInfo={NSValidationErrorObject=<NSManagedObject: 0x600002217390> (entity: Fish; id: 0x83319d001151328d <x-coredata://C76A2A64-146E-432F-A565-319B5A2F23F5/Fish/p12>; data: { id = nil; }), NSLocalizedDescription=%{PROPERTY}@ is a required value., NSValidationErrorKey=id, NSValidationErrorValue=null} %{PROPERTY}@ is a required value.
However, if I set up Quota and Fish with an inverse relationship then the data saves as expected, so I'm a little confused. Is there anyone out there who can provide some guidance as to why I'm seeing this error when I try to save a record in SwiftData with no inverse relationship?
I do fully understand about unidirectional vs bidirectional relationships but I have a scenario where I need the relationship to be unidirectional. Also, as a side note, the Fish record already exists in my database, but if I delete it and try to save the record I still see this error.
Thank you so much in advance for any help.
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.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store
App Review
App Store Connect
In SwiftUI for macOS, how do I configure a Picker as a segmented control to have a flexible width? This design pattern is present in Xcode 26 at the top of the sidebar and inspector panel.
I can't figure out the combination of view modifiers to achieve a similar look.
import SwiftUI
struct ContentView: View {
@State private var selection = 0
var body: some View {
VStack {
Picker("", selection: $selection) {
Image(systemName: "doc")
Image(systemName: "folder")
Image(systemName: "gear")
Image(systemName: "globe")
.frame(maxWidth: .infinity) // Doesn't do anything.
}
.labelsHidden()
.pickerStyle(.segmented)
.frame(maxWidth: .infinity) // Doesn't affect segment sizes.
Spacer()
}
}
}
I want the entire Picker to fill the width and for each segment to be of equal widths. How?
In AppKit I would use AutoLayout for the flexible width and NSSegmentedControl.segmentDistribution for the segment widths. Is there a SwiftUI equivalent?
macOS 26 / Xcode 26.3
the iOS app store package's entitlements file has an issue. After updating to a new version to fix the entitlements file, the app still crashes upon opening but can function normally after a restart. What methods can the app side use to resolve this entitlements file issue without requiring a restart to open and use the app properly?
Apple Developer Program membership purchased but still being asked to renew — cannot access services
I recently purchased the Apple Developer Program — 1 Year Membership, and the payment has been successfully processed. However, even after the purchase, I am still being prompted to renew my membership and cannot access any of the developer services that should be available with an active membership.
It is very frustrating to pay for a membership and then be told to renew it again without being able to use the services I paid for. The membership status does not seem to reflect the completed purchase at all.
Has anyone else experienced this issue? Why does Apple charge for a membership and then continue to block access while asking for renewal? I would appreciate any guidance on how to resolve this, or if an Apple representative could look into my account.
Thank you.
PLEASE HELP! All of the sudden, today I cannot get onto sites I use normally. Like chat, claude, canva etc. I keep getting this error message. Can someone please tell me is going on? This needs to be fixed!
I tried to enroll for the Apple Developer Membership but keep failing at the payment authorization.
Used different cards (7 of them) that was setup on my Apple Pay which I have been using them for daily expenses. So no issue on those cards.
Anyone experiencing the same issue as me and how did you resolve it?
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
I requested the Family Controls (distribution) capability but am not sure if I did it correct. I applied, answered the questions why i needed it and submitted. Its been about 2 weeks since applying. In the app configurations, it on apple dev site, it shows in the request history that I submitted it on March 17, but I can click the request (+) button and request it again. Just want to make sure I didn't mess anything up--it seems like they would prevent me from sendin another request if I had already requested it. It hasn't taken them this long to get back to me in the past which is why I am confused. If anyone knows how to speed up the process, please let me know! Thanks.
Hello everyone,
I am desperately seeking guidance. My app has been stuck in the "Waiting for Review" status for over 17 days (since at least Feb 13). It hasn't even entered the "In Review" stage.
I completely understand that review times can vary, but what's concerning is that we seem to be caught in a system loop. We have proactively contacted Apple Developer Support multiple times over the past few weeks. Specifically, we have open cases (Case ID: 102820493078 and Case ID: 102820491288) with messages sent on:
Feb 13
Feb 18
Feb 23
Feb 24/25
Unfortunately, we have only received generic automated responses, and the status remains firmly stuck at "Waiting for Review".
At this point, we are extremely worried that our binary might be caught in a system glitch or ghosted in the queue.
Could any Apple Staff here kindly look into these Case IDs to see if there is a technical issue preventing our app from entering the review queue?
Has any other developer experienced a similar >17 days wait time just to enter the queue recently?
Any help to untangle this would be greatly appreciated. Thank you!
Our iOS & tvOS apps are stuck in Waiting for Review for several days.
We have already submitted expedite review requests multiple times but received no response.
This is a critical bug fix for production crash issues that affect all users.
Submission IDs:
iOS: 98a69297-4f1f-4a1a-80f1-6f9aa4e007bd
tvOS: 4202becb-9eef-45ee-a333-de076f1bf66a
Please help escalate to the App Review team.
We need urgent review to fix user issues.
Thank you very much.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Guideline 3.1.1 - Business - Payments - In-App Purchase
The app includes an account registration feature for businesses and organizations, which is considered access to external mechanisms for purchases or subscriptions to be used in the app.
Next Steps
Remove the account registration features for business and organizations.
Our application currently allows users to register and create multiple accounts using a phone number.
All users can freely create an account. The app is designed to help users manage their own products, orders, and sales invoices. It is purely a sales management tool. We do not provide any external purchase links, external payment methods, or subscription mechanisms outside of Apple’s In-App Purchase system.
However, our app was rejected under Guideline 3.1.1 with the explanation that the app includes “account registration for businesses or organizations,” which is considered access to external purchase mechanisms.
We are confused about this interpretation.
From our understanding:
Any individual user can register.
The registration process is only for authentication and data management.
The app must include an account registration feature in order to function properly.
There is no external purchasing mechanism involved in the registration process.
Could someone please clarify:
Why would allowing users (including small business owners) to register accounts be considered “access to external purchase mechanisms”?
What specifically qualifies as “account registration for businesses or organizations” under Guideline 3.1.1?
What changes would be required to comply with the guideline while still keeping mandatory account registration?
We would greatly appreciate clarification so we can properly address the issue and ensure full compliance with App Store policies.
Thank you.
Topic:
Business & Education
SubTopic:
General
I'm submitting a native macOS app (Swift/SwiftUI, arm64) that includes Sparkle.framework for auto-updates. All binaries are signed with a Developer ID Application certificate using --options runtime and --timestamp.
I've submitted 12+ times over the past two days, both from local notarytool submit and from GitHub Actions CI. Every submission uploads successfully and returns a valid submission ID, but then stays at "In Progress" indefinitely — none have resolved to Accepted or Invalid.
Two early submissions did eventually come back "Invalid" — Apple's rejection log showed the Sparkle nested binaries had ad-hoc signatures (they were being signed as individual Mach-O files instead of bundle directories). I fixed this with proper inside-out bundle signing. Since the fix, local codesign --verify --deep --strict passes cleanly, but all ~10 subsequent submissions remain stuck at "In Progress".
9UT54V24XG
Would appreciate any guidance, or if someone from the notary team could check our queue. Happy to provide specific submission IDs.
Topic:
Code Signing
SubTopic:
Notarization