Navigate the App Store landscape. Share strategies for app submission, distribution, marketing, and user acquisition. Discuss best practices for getting your app discovered and downloaded.

All subtopics
Posts under App Store Distribution & Marketing topic

Post

Replies

Boosts

Views

Activity

Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
0
0
1.6k
Jun ’26
From an Uber driver to a solo app founder, and losing it all overnight
Hi everyone, I want to share what the last year has been like, partly to be heard, and partly because I think other solo developers should know this can happen. Two years ago, I was driving Uber in New Zealand. Somewhere during those long shifts, talking to passengers and thinking about the same idea every single day, I decided to build my own ride-hailing platform. I had no background in coding. None. I just started. I hosted my own server. I learned to build a backend. Then a frontend. Then a whole driver app and a whole rider app. My daily routine was this: I'd drive with my MacBook sitting on the dash of my Prius. When rides were quiet, I'd pull over to the side of the road and code. I drove close to 70,000 km around New Zealand while building these apps. I gave up a large part of my time with my family, and there are moments with my baby girl that I won't get back. My family supported me the whole way, and they were proud of me. After nine months, I had four apps built. The Android versions went live and have been running with no issues, no complaints, and no flags. Then I built the iOS versions too, got them through TestFlight and into production. The first time they were live, I felt something I'd never felt before—that I'd actually made something. I showed them to friends, family, and even my Uber passengers. That feeling of accomplishment was everything. I had two apps: A driver app for drivers. A rider app that riders use to hail taxis. We had live tracking and every feature that Uber had. The only thing I assume I did wrong (since I was inexperienced) was that I gave login credentials to the Apple review team so they could access my driver app. So far, so good. I wanted them to experience the full flow of the app, so I decided to dispatch demo (dummy) offers so they could see the complete journey. A new offer would appear whenever they tapped Go Online, repeating every two or three minutes. My intention was for them to see the incoming offer and go through the different stages of the app—receiving an offer, accepting it, driving to the destination, ending the trip, seeing the reward card, fare, and so on. They would never have seen all of this if I hadn't created a dummy offer. This mechanism was activated only for the Apple reviewer credentials. No one else would ever experience it. I think they assumed I was giving fake offers or misrepresenting the app. A human reviewer, understanding the intent, would hopefully have recognised what I was trying to demonstrate. At the very least, I wish they had flagged it and given me a chance to explain instead of terminating my account overnight. Based on this, I recreated the exact timeline from my backend logs. Here's exactly what happened: Time (NZ) 15:03:47 — Logged in — ✅ 200 15:03–15:04 — Browsed earnings, job history, past trip #1164, payouts, and Stripe status — ✅ All fine 15:04:23 — Tapped Go Online — ✅ 15:04:23 — Backend seeded a fake ride offer (#1038) — Offer appears 15:04:27 — Rejected the offer (after 4 seconds) — ✅ 15:06:00 — Last seen timestamp — Last successful moment 15:06:10 — A second Apple login (17.185.64.86) accessed the same account — First session disconnected 15:06:12–15:07:47 — Reviewer's live connection failed 7 times ("session_token mismatch" → 403) — ❌ Broken 15:06:13 — Tried to go offline — ❌ 401 15:06–15:12 — Received a new fake offer approximately every 2 minutes; attempted to reject them but received 400 errors — ❌ ~15:13 — Reviewer left — Nothing completed Then one day, I got a notice from Apple. My Developer Program membership was terminated under Section 3.2(f). All my apps were pulled from the App Store overnight. Here's the part I want other solo founders to understand, because it's the part that still keeps me up: There was no warning. No email first. No "this looks wrong, can you explain or fix it?" Just termination, and everything was gone in one moment. I filed an appeal through the official channel. It came back as a final denial, and they said there would be no further appeals on the account. From my own server logs, I could see that between the termination and the denial, no reviewer ever opened the app again. The decision was made from their records, not from a fresh look. So there was genuinely nothing I could have shown them—no fix, no explanation—that would have been seen. I'm not writing this to argue that Apple has no right to protect its platform. It does. But for a one-person team, a Section 3.2(f) termination means your entire business can disappear overnight, with no warning and no practical way back. I don't think many solo developers realise how final and how fast that is until it happens to them. So I wanted to ask the community a few honest questions: Has anyone here been through a Section 3.2(f) account termination? What happened next? Is there genuinely any path forward once an appeal is marked final—a separate entity, a legal channel, or anything else? And a broader question: do you think there should be a warning, or a short window to fix things, before a lifetime ban, especially for solo developers whose whole livelihood is on the line? This has been one of the hardest stretches of my life. I put everything into this. If even a few people read it and it saves them from the same fall, or if someone genuinely knows a path forward, that would mean a lot. Thank you for reading.
10
0
569
9m
Guideline 5.1.3(ii) — does encrypted, per-user private CloudKit storage count as "storing personal health information in iCloud"?
Guideline 5.1.3(ii) says apps "may not store personal health information in iCloud." Does this apply to any use of a private, per-user CloudKit database for health-related data, or is it specifically about unencrypted/shared storage, or data sourced from HealthKit? If a health app end-to-end encrypts sensitive fields so that even Apple's infrastructure can't read them, and the data never leaves the individual user's own iCloud account, does that change how 5.1.3(ii) applies — or is the guideline a blanket restriction regardless of encryption? Has anyone gotten reviewer feedback (approval or rejection) that clarifies how this is actually enforced in practice? Thanks in advance!
0
0
5
1h
TestFlight: "Could not install . The requested app is not available or doesn't exist."
Hi everyone, We've been stuck on this issue for several days and would really appreciate any guidance from anyone who has encountered this before. Issue Our app uploads successfully to App Store Connect, appears in TestFlight, and the build status is Ready for Internal Testing. However, every internal tester receives the following error when trying to install the app through TestFlight: Could not install . The requested app is not available or doesn't exist. Environment Apple Developer Program: Individual Distribution: Internal TestFlight Framework: React Native (Expo SDK) Build Service: Expo EAS Build Submission: Expo EAS Submit Platform: iOS What we've already verified The app builds successfully. The IPA is signed successfully. Build upload to App Store Connect succeeds. Build processing completes successfully. The build is assigned to an Internal Testing group. Internal testers have accepted the invitation. The bundle identifier is correct. Distribution certificate and provisioning profile are valid. We generated fresh builds and submitted them again. We recreated the App Store Connect app and submitted a new build. We also regenerated signing credentials where applicable. The issue persists across multiple builds. Additional Information During eas build, Apple successfully authenticates, registers the bundle identifier, creates the distribution certificate and provisioning profile, and the build completes without errors. eas submit also completes successfully, and the build appears in TestFlight. The failure only occurs when attempting to install the app from the TestFlight app. Error Could not install . The requested app is not available or doesn't exist. Has anyone experienced this issue recently? Is this likely a TestFlight/App Store Connect backend issue, or is there any App Store Connect configuration that we may have overlooked? And this is our active case id for the support: 102930164003 Any suggestions would be greatly appreciated. Thank you!
4
2
297
1h
Please update Expo Go
I’m using Expo to develop apps and the Expo Go app currently supports SDK 54. I want to be able to use SDK 56 and incorporate Liquid Glass into my apps. Can you please approve to update Expo Go so that way developers can gain access to test their apps in SDK 56?
0
0
8
1h
Nothing Works
App Store Connect does not work. These forums do not work. Xcode does not work. Mac OS 26 navigation bars do not work. It's getting a little frustrating. App Store Connect: "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." How? I added a new app build (are "builds" and "versions" the same, I thought they were different, but why would I create a new version of my product?) and submitted it for review. It did not take the "Ready for Review" subscription items with it. They're stuck in a separate draft review. There is no control anywhere to "add an app version." Useless error, pathetic UI, designed by people who have never used this product themselves before, clearly. These forums: Try searching for "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." Get a 403 Forbidden error. Fun. Very useful. Xcode does not work. Spent a good part of my day debugging why Xcode will automatically mask Mac OS 12 icons when there is no Mac app icon specified in an asset collection in a Catalyst context, but will not mask the icon when there is a Mac icon specified. There's no messaging, no warnings, no errors, no nothing. It just does random things. The entire Catalyst idea is nice in theory but there are gotchas like these everywhere. Should you build for iOS, Mac, or iOS + Mac? The answer is "Good luck." Mac OS 26 navigation bars do not work. I'm getting black text on black backgrounds, white text on white backgrounds, sometimes, depending on whether a view loads. Seems like another Apple bug. Support is useless as always, and my record on these forums so far is that no one answers any of my questions. So I'm not sure why I bother. But maybe something I've written will help someone.
3
0
39
1h
App Delay: macOS stuck 'Processing' for over 10 days
NB Dev Support ticket has been open for 9 days 102922985821 We are experiencing significant roadblock as macOS app are stuck 'Processing' after uploading. Current 10 days stuck. It's now affecting our release roadmap, and this is even before we have to wait for the usual extended TestFlight and Production review times that exist for macOS (compared to iOS). The .pkg app is uploaded via Transporter. Transporter reports it has uploaded ok, but in App Store Connect shows it is stuck 'Processing'. Subsequent upload has the same effect. Two previous builds for this build number were rejected (Invalid Binary = signing) but have been fixed - we shouldn't have to bump the build number to free the slot to try again... Note there were a flurry of these issues in Jan 2026, but also at least one other ticket now: https://developer.apple.com/forums/thread/818208 Anyone else seeing this, or been able to resolve? Cheers!
2
1
382
4h
6 Days Waiting in Review - Is this normal?
Hi, I am reaching out because I submitted my build for distribution on Sunday, July 12th, and it still shows that its waiting for review. I received an email saying it typically takes between 24-48 hours. This is my first distribution build, so I understand if it takes longer; however, I just want to make sure there is not anything missing on my end.
1
0
98
5h
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.
19
1
1.6k
5h
App Stuck in "Waiting for Review" for Over 3 Weeks After Re-Submission
Hello, My app was reviewed and rejected on June 26, 2026 (3:48 PM). I fixed every issue mentioned by the App Review team and submitted a new build. After about one week, the app was still stuck in "Waiting for Review" and had never moved to "In Review." Thinking there might have been an issue with the submission itself, I canceled it and submitted it again. Submission ID: 0e03f336-27f3-42d0-9d15-a0df4e8ac77a Unfortunately, even after re-submitting, the app is still in "Waiting for Review", and I haven't received any communication explaining the delay. Has anyone experienced a similar situation? If so, how did you get the review process moving again? Any guidance would be greatly appreciated. Thank you.
1
0
41
5h
App Review stuck in "Waiting for Review" for over 72 hours after replying to a rejection – Is anyone else experiencing this?
Hello everyone, I'm looking for some advice because I'm not sure if this is normal or if there is currently a delay with App Review. Here is my situation: My app was initially rejected under Guideline 5.6. The issue was fixed immediately. The fix only required changing my Firebase Remote Config (no code changes or new binary were necessary). I replied to the App Review message explaining the fix and resubmitted the same version for review. Since then, the app has been stuck in "Waiting for Review" for more than 72 hours. I have already: Requested an expedited review. Contacted Apple Developer Support. Received no response so far. My questions are: Is anyone else currently experiencing unusually long "Waiting for Review" times? Does replying to a rejection with the same build place the submission in a different review queue? Would submitting a new build (with a higher build number) help, or would that simply restart the waiting time? Is there anything else I can do to get the review moving? For those who have experienced this before: How long did your review stay in "Waiting for Review"? What ultimately resolved the situation? Any advice or recent experiences would be greatly appreciated. Thank you!
1
0
45
8h
company/entity name as part of submission
I am trying to understand what's required when you have an app connect account and what the business name has to be. Mine currently has ,Inc. American Express simply says "American Express" but if you look into their registration with New York, they are "American Express Company" both on DUNS and with the state of New York. Help me understand what our options are here and where Apple really gets this information.
0
0
28
8h
Facing issue while submitting First app with subscriptions
I'm submitting my first app version along with my first auto-renewable subscription group, and running into an issue. My app version (1.0) submits for review fine on its own — no problems there. But I also need to submit my subscription group for the first time, and Apple requires the first subscription group to be submitted together with an app version. I've created two subscriptions inside one subscription group. For both subscriptions I've completed: Product ID and duration Subscription pricing App Store localization (display name + description) An App Review screenshot (uploaded under Review Information) On the subscription group's "Prepare for Submission" page, when I try to add it to a submission, I get this warning: "Unable to Submit for Review New subscription groups must be submitted with an auto-renewable subscription from within that group. To submit your items for review, add an app version for the selected platform." The "Submit for Review" button stays greyed out. Even though both subscriptions inside the group show "Prepare for Submission" status (not yet "Ready to Submit"), and I don't see where to add the app version to this same submission so they go together. Has anyone run into this? What's the exact sequence to get a subscription group and its subscriptions to actually become submittable alongside a first app version? Is there a step I'm missing on either the subscription pages or the app version page? Any advice appreciated.
0
0
25
8h
Long delay in my First App Publishing
Hi, I want to know is it normal to expect time of more then 5 days in Waiting for Review for my iOS App to be avaiable on Apple App store ? I sent my new App first release a week back for Review and I still see its status as Waiting for Review in my Connect. There are no mails even raised to flag any issue in my uploaded release. So I want to know should I contact the Support or continue waiting ? Thanks in advance .
0
0
13
8h
subscription stuck in "Prepare for submission" state
I have an app update that is completely ready for submission. This update incorporates a subscription for new functionality. I'm unable to submit as the subscription is stuck in the "Prepare for submission" state instead of going to "Ready to submit" and I'm unable to include it with my app. After doing some research, I found that the banking information on my developer account is broken. I tried to update and fix this information. However, I get an error saying that it is unable to find "Bank of America". I suspect this is causing everything else to be stuck in the "Prepare for submission" state. Does anyone know how to work around this issue or can someone at Apple give me an ETA as to when things will be fixed. This issue is delaying my release. - Ken
0
0
73
18h
App unable to load all requested Subscriptions and IAPs
I have two subscription in the same group and the same level 1. One is a monthly one and the other a yearly one. I also have an IAP for Lifetime Unlock. When my app requests for these it only loads Monthly. Debugging reveals that the ASC doesn't return the yearly subscription and the lifetime IAP. When I added a StoreKit config to the app, it correctly show the Yearly subscription as well and the view loads it appropriately. But the storekit config doesn't load IAP. I have checked things several tiles in ASC and in code. What can I do to fix this?
0
0
74
18h
First IAP never included in submission group — Draft Submission only shows app binary
I have a live app with a fully-configured non-consumable IAP that has never been reviewed by Apple, despite three attempts across app versions 1.1, 1.2, and 1.3 (all approved and released). Setup: IAP status: Ready to Submit Type: Non-Consumable, $3.99 USD Metadata complete: reference name, price, availability set to all countries, English (U.S.) localization, review screenshot uploaded Product ID matches exactly between my Swift code and App Store Connect Workflow followed (per Apple's documented instructions): Create the IAP with all required metadata On the app version page, attach the IAP to the "In-App Purchases and Subscriptions" section Save the version page Click "Add for Review" Observed behavior: The Draft Submission modal opens and shows only "iOS App [version]" as an item. The IAP does not appear as a second item, and there is no visible affordance (button, +, menu) to add it. Submitting the version proceeds normally, the app version is approved and released, but the IAP remains at "Ready to Submit" status permanently. Impact: Users hitting the app's paywall receive "Product not found. Please try again later." from StoreKit.Product.products(for:) because the IAP has never been made available in Apple's public product catalog. I have an open standard support case (#102935323676) filed July 7 with follow-up July 9. No substantive response after 5 business days. I've now submitted version 1.4 with reviewer notes explaining the situation and requesting the reviewer include the IAP alongside. Has anyone else encountered this? Is there a workflow step I'm missing that adds the IAP to the submission group? Is there a way to force the IAP into a submission group after the fact? Thanks in advance for any guidance.
1
0
164
22h
Account-level TestFlight failure after app transfer
Account-level TestFlight failure after app transfer. All apps (including brand-new, non-transferred app) fail with "The requested app is not available or doesn't exist" (Team JYHS43K259) Since receiving several apps via App Transfer, no app on my team can be installed through TestFlight. Every install attempt fails with: "Could not install [App Name]. The requested app is not available or doesn't exist." Critically, this affects not only the transferred apps but also a brand-new app created directly on this account with no transfer history. This indicates an account-level distribution problem rather than an app-record issue. Account details Account holder: BULENT TEKBAS Team ID: JYHS43K259 Account type: Individual Support case: 102936985904 — open for 5+ business days with no substantive response Affected apps Uyku Sesleri — Bundle ID: com.octo8.uykusesleri — Apple ID: 6759616379 — transferred to this account on June 13, 2026 Bekçilik Sınavı 2026 — Bundle ID: com.alhn7.bekciliksinavi2026 — Apple ID: 6756800265 — transferred July 1, 2026 VitaminD — Bundle ID: com.octo8.vitamind — Apple ID: 6768099487 — transferred July 9, 2026 Arete — Bundle ID: com.octo8.arete — created natively on this account, never transferred, currently TestFlight-only All four apps exhibit the identical install failure. Symptoms Builds upload, process, and reach "Testing" status normally Builds are visible in the TestFlight app with an Install button Tapping Install immediately fails with "The requested app is not available or doesn't exist" Reproduced on iPhone 16 Pro running iOS 26 and iOS 27 Internal testing, external testing, and public links all fail identically Already verified / attempted Paid and Free Applications Agreements: Active; banking and tax information complete Pricing and Availability: available in all territories; no app is Removed from Sale Created new versions in "Prepare for Submission" state App Privacy details published; export compliance resolved on all builds Trader status / DSA declaration completed Deleted and reinstalled TestFlight; signed out of Media & Purchases; restarted device; signed back in; accepted freshly generated invitations Removed all testers and re-invited them; generated new public links Uploaded multiple new builds with incremented build numbers — all process successfully, all fail to install Why this appears to be account-level Arete (com.octo8.arete) is a new app with a new bundle ID, created, signed, and uploaded entirely under Team JYHS43K259, with no connection to any previous team. It fails identically to the three transferred apps. The only common factor across all four apps is the team itself. Request Could someone from Apple please check whether Team JYHS43K259 is in a held or degraded distribution state following the recent app transfers? Case 102936985904 has been unanswered for over five business days, and this is blocking updates to live apps with active subscribers. I can provide sysdiagnose logs, build IDs, or any additional information immediately.
0
0
86
1d
Auto-renewable subscription fails to submit — generic "errors with one or more of your items" / "unexpected error," but no field-level error shown
I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.
0
0
62
1d
Update stuck in "Waiting for Review" for 10 days — no Resolution Center message, banking/agreements current
Hi App Review, An update to an app that's already live on the App Store has been in "Waiting for Review" for 10 days with no status change, and I wanted to check whether it's proceeding normally or whether anything is required from my side. Submission ID: b4e5d54c-de30-4003-9f3c-232e366d01c4 Version: 1.1.0 (build 7), an update to a live app (1.0.0 currently in production) Submitted: 16 June 2026, 22:10 Current status: Waiting for Review (has not moved to In Review) I've already checked the usual things my end: there's no message in Resolution Center, no "action required" banner on the app or version page, the build shows as valid and is correctly attached to the version, export compliance/encryption is answered, and Agreements, Tax, and Banking are all current. I also contacted Developer Support via the contact form on 23 June [add: case #102923511308 if you have one] but haven't had a reply yet. Could you confirm whether the review is proceeding normally, or let me know if there's anything I need to do? Happy to provide any further detail. Thanks.
1
0
299
1d
Auto-renewable subscription fails to submit — generic "errors with one or more of your items" / "unexpected error," but no field-level error shown
I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.
0
0
48
1d
Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
Replies
0
Boosts
0
Views
1.6k
Activity
Jun ’26
From an Uber driver to a solo app founder, and losing it all overnight
Hi everyone, I want to share what the last year has been like, partly to be heard, and partly because I think other solo developers should know this can happen. Two years ago, I was driving Uber in New Zealand. Somewhere during those long shifts, talking to passengers and thinking about the same idea every single day, I decided to build my own ride-hailing platform. I had no background in coding. None. I just started. I hosted my own server. I learned to build a backend. Then a frontend. Then a whole driver app and a whole rider app. My daily routine was this: I'd drive with my MacBook sitting on the dash of my Prius. When rides were quiet, I'd pull over to the side of the road and code. I drove close to 70,000 km around New Zealand while building these apps. I gave up a large part of my time with my family, and there are moments with my baby girl that I won't get back. My family supported me the whole way, and they were proud of me. After nine months, I had four apps built. The Android versions went live and have been running with no issues, no complaints, and no flags. Then I built the iOS versions too, got them through TestFlight and into production. The first time they were live, I felt something I'd never felt before—that I'd actually made something. I showed them to friends, family, and even my Uber passengers. That feeling of accomplishment was everything. I had two apps: A driver app for drivers. A rider app that riders use to hail taxis. We had live tracking and every feature that Uber had. The only thing I assume I did wrong (since I was inexperienced) was that I gave login credentials to the Apple review team so they could access my driver app. So far, so good. I wanted them to experience the full flow of the app, so I decided to dispatch demo (dummy) offers so they could see the complete journey. A new offer would appear whenever they tapped Go Online, repeating every two or three minutes. My intention was for them to see the incoming offer and go through the different stages of the app—receiving an offer, accepting it, driving to the destination, ending the trip, seeing the reward card, fare, and so on. They would never have seen all of this if I hadn't created a dummy offer. This mechanism was activated only for the Apple reviewer credentials. No one else would ever experience it. I think they assumed I was giving fake offers or misrepresenting the app. A human reviewer, understanding the intent, would hopefully have recognised what I was trying to demonstrate. At the very least, I wish they had flagged it and given me a chance to explain instead of terminating my account overnight. Based on this, I recreated the exact timeline from my backend logs. Here's exactly what happened: Time (NZ) 15:03:47 — Logged in — ✅ 200 15:03–15:04 — Browsed earnings, job history, past trip #1164, payouts, and Stripe status — ✅ All fine 15:04:23 — Tapped Go Online — ✅ 15:04:23 — Backend seeded a fake ride offer (#1038) — Offer appears 15:04:27 — Rejected the offer (after 4 seconds) — ✅ 15:06:00 — Last seen timestamp — Last successful moment 15:06:10 — A second Apple login (17.185.64.86) accessed the same account — First session disconnected 15:06:12–15:07:47 — Reviewer's live connection failed 7 times ("session_token mismatch" → 403) — ❌ Broken 15:06:13 — Tried to go offline — ❌ 401 15:06–15:12 — Received a new fake offer approximately every 2 minutes; attempted to reject them but received 400 errors — ❌ ~15:13 — Reviewer left — Nothing completed Then one day, I got a notice from Apple. My Developer Program membership was terminated under Section 3.2(f). All my apps were pulled from the App Store overnight. Here's the part I want other solo founders to understand, because it's the part that still keeps me up: There was no warning. No email first. No "this looks wrong, can you explain or fix it?" Just termination, and everything was gone in one moment. I filed an appeal through the official channel. It came back as a final denial, and they said there would be no further appeals on the account. From my own server logs, I could see that between the termination and the denial, no reviewer ever opened the app again. The decision was made from their records, not from a fresh look. So there was genuinely nothing I could have shown them—no fix, no explanation—that would have been seen. I'm not writing this to argue that Apple has no right to protect its platform. It does. But for a one-person team, a Section 3.2(f) termination means your entire business can disappear overnight, with no warning and no practical way back. I don't think many solo developers realise how final and how fast that is until it happens to them. So I wanted to ask the community a few honest questions: Has anyone here been through a Section 3.2(f) account termination? What happened next? Is there genuinely any path forward once an appeal is marked final—a separate entity, a legal channel, or anything else? And a broader question: do you think there should be a warning, or a short window to fix things, before a lifetime ban, especially for solo developers whose whole livelihood is on the line? This has been one of the hardest stretches of my life. I put everything into this. If even a few people read it and it saves them from the same fall, or if someone genuinely knows a path forward, that would mean a lot. Thank you for reading.
Replies
10
Boosts
0
Views
569
Activity
9m
Guideline 5.1.3(ii) — does encrypted, per-user private CloudKit storage count as "storing personal health information in iCloud"?
Guideline 5.1.3(ii) says apps "may not store personal health information in iCloud." Does this apply to any use of a private, per-user CloudKit database for health-related data, or is it specifically about unencrypted/shared storage, or data sourced from HealthKit? If a health app end-to-end encrypts sensitive fields so that even Apple's infrastructure can't read them, and the data never leaves the individual user's own iCloud account, does that change how 5.1.3(ii) applies — or is the guideline a blanket restriction regardless of encryption? Has anyone gotten reviewer feedback (approval or rejection) that clarifies how this is actually enforced in practice? Thanks in advance!
Replies
0
Boosts
0
Views
5
Activity
1h
TestFlight: "Could not install . The requested app is not available or doesn't exist."
Hi everyone, We've been stuck on this issue for several days and would really appreciate any guidance from anyone who has encountered this before. Issue Our app uploads successfully to App Store Connect, appears in TestFlight, and the build status is Ready for Internal Testing. However, every internal tester receives the following error when trying to install the app through TestFlight: Could not install . The requested app is not available or doesn't exist. Environment Apple Developer Program: Individual Distribution: Internal TestFlight Framework: React Native (Expo SDK) Build Service: Expo EAS Build Submission: Expo EAS Submit Platform: iOS What we've already verified The app builds successfully. The IPA is signed successfully. Build upload to App Store Connect succeeds. Build processing completes successfully. The build is assigned to an Internal Testing group. Internal testers have accepted the invitation. The bundle identifier is correct. Distribution certificate and provisioning profile are valid. We generated fresh builds and submitted them again. We recreated the App Store Connect app and submitted a new build. We also regenerated signing credentials where applicable. The issue persists across multiple builds. Additional Information During eas build, Apple successfully authenticates, registers the bundle identifier, creates the distribution certificate and provisioning profile, and the build completes without errors. eas submit also completes successfully, and the build appears in TestFlight. The failure only occurs when attempting to install the app from the TestFlight app. Error Could not install . The requested app is not available or doesn't exist. Has anyone experienced this issue recently? Is this likely a TestFlight/App Store Connect backend issue, or is there any App Store Connect configuration that we may have overlooked? And this is our active case id for the support: 102930164003 Any suggestions would be greatly appreciated. Thank you!
Replies
4
Boosts
2
Views
297
Activity
1h
Please update Expo Go
I’m using Expo to develop apps and the Expo Go app currently supports SDK 54. I want to be able to use SDK 56 and incorporate Liquid Glass into my apps. Can you please approve to update Expo Go so that way developers can gain access to test their apps in SDK 56?
Replies
0
Boosts
0
Views
8
Activity
1h
Nothing Works
App Store Connect does not work. These forums do not work. Xcode does not work. Mac OS 26 navigation bars do not work. It's getting a little frustrating. App Store Connect: "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." How? I added a new app build (are "builds" and "versions" the same, I thought they were different, but why would I create a new version of my product?) and submitted it for review. It did not take the "Ready for Review" subscription items with it. They're stuck in a separate draft review. There is no control anywhere to "add an app version." Useless error, pathetic UI, designed by people who have never used this product themselves before, clearly. These forums: Try searching for "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." Get a 403 Forbidden error. Fun. Very useful. Xcode does not work. Spent a good part of my day debugging why Xcode will automatically mask Mac OS 12 icons when there is no Mac app icon specified in an asset collection in a Catalyst context, but will not mask the icon when there is a Mac icon specified. There's no messaging, no warnings, no errors, no nothing. It just does random things. The entire Catalyst idea is nice in theory but there are gotchas like these everywhere. Should you build for iOS, Mac, or iOS + Mac? The answer is "Good luck." Mac OS 26 navigation bars do not work. I'm getting black text on black backgrounds, white text on white backgrounds, sometimes, depending on whether a view loads. Seems like another Apple bug. Support is useless as always, and my record on these forums so far is that no one answers any of my questions. So I'm not sure why I bother. But maybe something I've written will help someone.
Replies
3
Boosts
0
Views
39
Activity
1h
App Delay: macOS stuck 'Processing' for over 10 days
NB Dev Support ticket has been open for 9 days 102922985821 We are experiencing significant roadblock as macOS app are stuck 'Processing' after uploading. Current 10 days stuck. It's now affecting our release roadmap, and this is even before we have to wait for the usual extended TestFlight and Production review times that exist for macOS (compared to iOS). The .pkg app is uploaded via Transporter. Transporter reports it has uploaded ok, but in App Store Connect shows it is stuck 'Processing'. Subsequent upload has the same effect. Two previous builds for this build number were rejected (Invalid Binary = signing) but have been fixed - we shouldn't have to bump the build number to free the slot to try again... Note there were a flurry of these issues in Jan 2026, but also at least one other ticket now: https://developer.apple.com/forums/thread/818208 Anyone else seeing this, or been able to resolve? Cheers!
Replies
2
Boosts
1
Views
382
Activity
4h
6 Days Waiting in Review - Is this normal?
Hi, I am reaching out because I submitted my build for distribution on Sunday, July 12th, and it still shows that its waiting for review. I received an email saying it typically takes between 24-48 hours. This is my first distribution build, so I understand if it takes longer; however, I just want to make sure there is not anything missing on my end.
Replies
1
Boosts
0
Views
98
Activity
5h
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.
Replies
19
Boosts
1
Views
1.6k
Activity
5h
App Stuck in "Waiting for Review" for Over 3 Weeks After Re-Submission
Hello, My app was reviewed and rejected on June 26, 2026 (3:48 PM). I fixed every issue mentioned by the App Review team and submitted a new build. After about one week, the app was still stuck in "Waiting for Review" and had never moved to "In Review." Thinking there might have been an issue with the submission itself, I canceled it and submitted it again. Submission ID: 0e03f336-27f3-42d0-9d15-a0df4e8ac77a Unfortunately, even after re-submitting, the app is still in "Waiting for Review", and I haven't received any communication explaining the delay. Has anyone experienced a similar situation? If so, how did you get the review process moving again? Any guidance would be greatly appreciated. Thank you.
Replies
1
Boosts
0
Views
41
Activity
5h
App Review stuck in "Waiting for Review" for over 72 hours after replying to a rejection – Is anyone else experiencing this?
Hello everyone, I'm looking for some advice because I'm not sure if this is normal or if there is currently a delay with App Review. Here is my situation: My app was initially rejected under Guideline 5.6. The issue was fixed immediately. The fix only required changing my Firebase Remote Config (no code changes or new binary were necessary). I replied to the App Review message explaining the fix and resubmitted the same version for review. Since then, the app has been stuck in "Waiting for Review" for more than 72 hours. I have already: Requested an expedited review. Contacted Apple Developer Support. Received no response so far. My questions are: Is anyone else currently experiencing unusually long "Waiting for Review" times? Does replying to a rejection with the same build place the submission in a different review queue? Would submitting a new build (with a higher build number) help, or would that simply restart the waiting time? Is there anything else I can do to get the review moving? For those who have experienced this before: How long did your review stay in "Waiting for Review"? What ultimately resolved the situation? Any advice or recent experiences would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
45
Activity
8h
company/entity name as part of submission
I am trying to understand what's required when you have an app connect account and what the business name has to be. Mine currently has ,Inc. American Express simply says "American Express" but if you look into their registration with New York, they are "American Express Company" both on DUNS and with the state of New York. Help me understand what our options are here and where Apple really gets this information.
Replies
0
Boosts
0
Views
28
Activity
8h
Facing issue while submitting First app with subscriptions
I'm submitting my first app version along with my first auto-renewable subscription group, and running into an issue. My app version (1.0) submits for review fine on its own — no problems there. But I also need to submit my subscription group for the first time, and Apple requires the first subscription group to be submitted together with an app version. I've created two subscriptions inside one subscription group. For both subscriptions I've completed: Product ID and duration Subscription pricing App Store localization (display name + description) An App Review screenshot (uploaded under Review Information) On the subscription group's "Prepare for Submission" page, when I try to add it to a submission, I get this warning: "Unable to Submit for Review New subscription groups must be submitted with an auto-renewable subscription from within that group. To submit your items for review, add an app version for the selected platform." The "Submit for Review" button stays greyed out. Even though both subscriptions inside the group show "Prepare for Submission" status (not yet "Ready to Submit"), and I don't see where to add the app version to this same submission so they go together. Has anyone run into this? What's the exact sequence to get a subscription group and its subscriptions to actually become submittable alongside a first app version? Is there a step I'm missing on either the subscription pages or the app version page? Any advice appreciated.
Replies
0
Boosts
0
Views
25
Activity
8h
Long delay in my First App Publishing
Hi, I want to know is it normal to expect time of more then 5 days in Waiting for Review for my iOS App to be avaiable on Apple App store ? I sent my new App first release a week back for Review and I still see its status as Waiting for Review in my Connect. There are no mails even raised to flag any issue in my uploaded release. So I want to know should I contact the Support or continue waiting ? Thanks in advance .
Replies
0
Boosts
0
Views
13
Activity
8h
subscription stuck in "Prepare for submission" state
I have an app update that is completely ready for submission. This update incorporates a subscription for new functionality. I'm unable to submit as the subscription is stuck in the "Prepare for submission" state instead of going to "Ready to submit" and I'm unable to include it with my app. After doing some research, I found that the banking information on my developer account is broken. I tried to update and fix this information. However, I get an error saying that it is unable to find "Bank of America". I suspect this is causing everything else to be stuck in the "Prepare for submission" state. Does anyone know how to work around this issue or can someone at Apple give me an ETA as to when things will be fixed. This issue is delaying my release. - Ken
Replies
0
Boosts
0
Views
73
Activity
18h
App unable to load all requested Subscriptions and IAPs
I have two subscription in the same group and the same level 1. One is a monthly one and the other a yearly one. I also have an IAP for Lifetime Unlock. When my app requests for these it only loads Monthly. Debugging reveals that the ASC doesn't return the yearly subscription and the lifetime IAP. When I added a StoreKit config to the app, it correctly show the Yearly subscription as well and the view loads it appropriately. But the storekit config doesn't load IAP. I have checked things several tiles in ASC and in code. What can I do to fix this?
Replies
0
Boosts
0
Views
74
Activity
18h
First IAP never included in submission group — Draft Submission only shows app binary
I have a live app with a fully-configured non-consumable IAP that has never been reviewed by Apple, despite three attempts across app versions 1.1, 1.2, and 1.3 (all approved and released). Setup: IAP status: Ready to Submit Type: Non-Consumable, $3.99 USD Metadata complete: reference name, price, availability set to all countries, English (U.S.) localization, review screenshot uploaded Product ID matches exactly between my Swift code and App Store Connect Workflow followed (per Apple's documented instructions): Create the IAP with all required metadata On the app version page, attach the IAP to the "In-App Purchases and Subscriptions" section Save the version page Click "Add for Review" Observed behavior: The Draft Submission modal opens and shows only "iOS App [version]" as an item. The IAP does not appear as a second item, and there is no visible affordance (button, +, menu) to add it. Submitting the version proceeds normally, the app version is approved and released, but the IAP remains at "Ready to Submit" status permanently. Impact: Users hitting the app's paywall receive "Product not found. Please try again later." from StoreKit.Product.products(for:) because the IAP has never been made available in Apple's public product catalog. I have an open standard support case (#102935323676) filed July 7 with follow-up July 9. No substantive response after 5 business days. I've now submitted version 1.4 with reviewer notes explaining the situation and requesting the reviewer include the IAP alongside. Has anyone else encountered this? Is there a workflow step I'm missing that adds the IAP to the submission group? Is there a way to force the IAP into a submission group after the fact? Thanks in advance for any guidance.
Replies
1
Boosts
0
Views
164
Activity
22h
Account-level TestFlight failure after app transfer
Account-level TestFlight failure after app transfer. All apps (including brand-new, non-transferred app) fail with "The requested app is not available or doesn't exist" (Team JYHS43K259) Since receiving several apps via App Transfer, no app on my team can be installed through TestFlight. Every install attempt fails with: "Could not install [App Name]. The requested app is not available or doesn't exist." Critically, this affects not only the transferred apps but also a brand-new app created directly on this account with no transfer history. This indicates an account-level distribution problem rather than an app-record issue. Account details Account holder: BULENT TEKBAS Team ID: JYHS43K259 Account type: Individual Support case: 102936985904 — open for 5+ business days with no substantive response Affected apps Uyku Sesleri — Bundle ID: com.octo8.uykusesleri — Apple ID: 6759616379 — transferred to this account on June 13, 2026 Bekçilik Sınavı 2026 — Bundle ID: com.alhn7.bekciliksinavi2026 — Apple ID: 6756800265 — transferred July 1, 2026 VitaminD — Bundle ID: com.octo8.vitamind — Apple ID: 6768099487 — transferred July 9, 2026 Arete — Bundle ID: com.octo8.arete — created natively on this account, never transferred, currently TestFlight-only All four apps exhibit the identical install failure. Symptoms Builds upload, process, and reach "Testing" status normally Builds are visible in the TestFlight app with an Install button Tapping Install immediately fails with "The requested app is not available or doesn't exist" Reproduced on iPhone 16 Pro running iOS 26 and iOS 27 Internal testing, external testing, and public links all fail identically Already verified / attempted Paid and Free Applications Agreements: Active; banking and tax information complete Pricing and Availability: available in all territories; no app is Removed from Sale Created new versions in "Prepare for Submission" state App Privacy details published; export compliance resolved on all builds Trader status / DSA declaration completed Deleted and reinstalled TestFlight; signed out of Media & Purchases; restarted device; signed back in; accepted freshly generated invitations Removed all testers and re-invited them; generated new public links Uploaded multiple new builds with incremented build numbers — all process successfully, all fail to install Why this appears to be account-level Arete (com.octo8.arete) is a new app with a new bundle ID, created, signed, and uploaded entirely under Team JYHS43K259, with no connection to any previous team. It fails identically to the three transferred apps. The only common factor across all four apps is the team itself. Request Could someone from Apple please check whether Team JYHS43K259 is in a held or degraded distribution state following the recent app transfers? Case 102936985904 has been unanswered for over five business days, and this is blocking updates to live apps with active subscribers. I can provide sysdiagnose logs, build IDs, or any additional information immediately.
Replies
0
Boosts
0
Views
86
Activity
1d
Auto-renewable subscription fails to submit — generic "errors with one or more of your items" / "unexpected error," but no field-level error shown
I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.
Replies
0
Boosts
0
Views
62
Activity
1d
Update stuck in "Waiting for Review" for 10 days — no Resolution Center message, banking/agreements current
Hi App Review, An update to an app that's already live on the App Store has been in "Waiting for Review" for 10 days with no status change, and I wanted to check whether it's proceeding normally or whether anything is required from my side. Submission ID: b4e5d54c-de30-4003-9f3c-232e366d01c4 Version: 1.1.0 (build 7), an update to a live app (1.0.0 currently in production) Submitted: 16 June 2026, 22:10 Current status: Waiting for Review (has not moved to In Review) I've already checked the usual things my end: there's no message in Resolution Center, no "action required" banner on the app or version page, the build shows as valid and is correctly attached to the version, export compliance/encryption is answered, and Agreements, Tax, and Banking are all current. I also contacted Developer Support via the contact form on 23 June [add: case #102923511308 if you have one] but haven't had a reply yet. Could you confirm whether the review is proceeding normally, or let me know if there's anything I need to do? Happy to provide any further detail. Thanks.
Replies
1
Boosts
0
Views
299
Activity
1d
Auto-renewable subscription fails to submit — generic "errors with one or more of your items" / "unexpected error," but no field-level error shown
I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.
Replies
0
Boosts
0
Views
48
Activity
1d