App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

Clarification on the Definition of "Drug Dosage Calculators" in Guideline 1.4.2
Hello, I am looking for a better understanding of Guideline 1.4.2, which states that "Drug dosage calculators" must be developed by drug manufacturers, hospitals, universities, or other approved entities. My main question is: What is Apple’s exact definition of a "Drug Dosage Calculator"? - Does the term exclusively refer to apps that calculate dosage (dose, interval, and treatment duration)? - Are apps that do not make clinical decisions, but only display bibliographic references based on user-entered data, also considered Drug Dosage Calculators? - If an app only performs basic mathematical operations on a dose value entered by the user, without suggesting medications or treatments, does it still fall under this restriction? I would like to better understand how Apple differentiates a medical support app (which only presents data) from a dosage calculator (which makes clinical decisions). I appreciate any insights from the community!
4
0
366
4w
AppTransaction.originalAppVersion returns "1.0" in App Review environment — not the actual build number
Hi, I'm using AppTransaction.originalAppVersion to detect whether a user originally purchased the app under the old paid model, so I can automatically unlock the app for them as a courtesy when migrating to freemium. Background On iOS, originalAppVersion returns CFBundleVersion (the build number). When I transitioned the app from paid (v1.x) to freemium (v2.0), I defined a numeric threshold for CFBundleVersion to distinguish legacy purchasers from new users: Build number below the threshold → v1.x purchase → auto-unlock Build number at or above the threshold → v2.0+ install → requires IAP In Production, originalAppVersion correctly returns the actual build number, and the comparison works as intended. Detection logic (simplified) // Determine environment via receipt URL func detectStoreEnvironment() -> String { if let url = Bundle.main.appStoreReceiptURL, url.lastPathComponent == "sandboxReceipt" { return "Sandbox" } return "Production" } // Legacy check using numeric comparison static func isLegacyPaidUser(version: String, threshold: String) -> Bool { guard !version.isEmpty else { return false } return version.compare(threshold, options: .numeric) == .orderedAscending } // In checkLegacyPurchase(): let version = appTransaction.originalAppVersion let isLegacy = isLegacyPaidUser(version: version, threshold: legacyBuildNumberThreshold) let env = detectStoreEnvironment() let shouldAutoUnlock = isLegacy && env != "Sandbox" The problem I know that in the Sandbox environment, originalAppVersion always returns "1.0" — this is mentioned in the AppTransaction documentation. My code already suppresses the auto-unlock for Sandbox (env != "Sandbox"). However, it appears that the App Review environment also returns "1.0" for originalAppVersion. Because the receipt URL path component is "receipt" (not "sandboxReceipt"), my environment detection classifies it as "Production" — so the Sandbox suppression doesn't apply. The reviewer is incorrectly identified as a legacy paid user and the app is unlocked without a purchase. This caused our v2.0 submission to be rejected under Guideline 2.1a. Questions Is it documented that the App Review environment returns "1.0" for AppTransaction.originalAppVersion, similar to Sandbox? Is there a reliable way to detect the App Review environment specifically — separate from both Sandbox and Production? For example, does the receipt URL differ, or is there another API? Is using originalAppVersion for legacy paid-user detection a supported pattern? If so, what is the recommended approach to handle the App Review case? Any guidance would be greatly appreciated. Thank you.
0
0
103
4w
App Store Review
I have a new app which has been submitted for review, and has been rejected.. The tester unable to see subscription settings.. He/she has not looked very far, they are in the app settings tab, and that was noted in the app submission. The likely issue is that this is an iPhone app, and specifically not for iPad.. Yet the reviewer used an iPad to test! This is the third consecutive rejection for administrative issues which have nothing to do with the app itself, and which, if the reviewers were to look properly, are not actually issues at all. This feels as though the reviewers are trying to get through as many reviews as possible in the shortest time possible, and not taking the time to examine an app submission properly. They are undermining months of hard work with a 30 second scan.
1
0
80
4w
Click "Update Review", or wait for Resolution Center reply?
My app (Markets: Global Trading 24/7, version 1.0.6, App ID 6756673679) was rejected on April 20 for Guideline 1.2. Apple's rejection message offered the option to demonstrate compliance via a screen recording, which we provided in Resolution Center the same day. The submission has remained in Rejected status while we await a response. Do we need to click "Update Review" to surface this to App Review, or are we supposed to wait in "Rejected" status until we get a Resolution Center reply? Thank you.
1
0
113
4w
Mac App Store review policy for Apple Event temporary exception entitlements
I’m looking for some advice regarding the usage of temporary exception entitlements in Mac App Store apps. Specifically the Apple Event Temporary Exception to communicate with other third party applications (not first-party macOS system apps): The Best Practices for Submitting Scriptable and AppleScript Apps to the Mac App Store section is a bit vague (how to 'request' a temporary entitlement?) and I couldn't find it mentioned in the Review Guidelines. Before designing, implementing and testing functionality based on the Apple Event Temporary Exception I’d like to know if these entitlements would: A. Always be rejected on the Mac App Store B. Only accepted in highly specific use cases C. Accepted if there is a clear use case and sufficient argumentation For this particular use case I’d like to send Apple Events to Adobe Illustrator and QuarkXPress. The application helps the user with some design tasks in their documents. The app requests the currently open documents and accesses document content to process used design elements. This is optional functionality that the user must explicitly enable in the app. I’m aware that the com.apple.security.scripting-targets entitlement is preferred. (Side question: are these always allowed or can they also be rejected for third party app scripting?) However, many third party applications don’t offer any scripting access groups in their definition, including Adobe Illustrator and QuarkXPress in this case. So before spending a lot of time implementing this feature I’d like to have some indication whether it is unlikely that sending Apple Events to third party apps will be allowed on the Mac App Store. Thanks for any insights!
5
0
352
4w
My App stuck in "Waiting for Review" two week
Hello everyone, My app (ID: 6756186616) was submitted on Mar 15, 2026, and has been stuck in "Waiting for Review" status for over 17 days. I contacted Developer Support (case #20000111565861) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds two week. Any recent experiences with long queues? Thanks!
7
1
309
4w
Beta App Review stuck 3+ days
Hi all, I have a build in "Waiting for Beta App Review" that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incident, does re-uploading resolve it, or does the new build simply re-enter the same queue with the same delay? I have also submitted a support request via the Contact Us form, but wanted to check with the community in case others are seeing the same pattern this week. Thanks,
0
0
181
4w
Construction Draw App Stuck in Rejection Loop
My app is for a client that facilitates construction draws for construction companies. The app is stuck in a rejection loop for this reason: Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable Issue Description The app still provides loan services but does not meet all the requirements for apps providing these services. See below for additional information. These requirements give App Store users confidence that apps offering financial services are qualified to provide these services and will responsibly manage their data. Next Steps It would be appropriate to take the following steps to resolve this issue: The app facilitates loan or credit applications but you have not provided loan or business license documentation that demonstrates the app is authorized to provide these services. The client does not lend to consumers, nor individuals, and the client operates in states that do not require a lending license (including NMLS) to provide financing (such as construction draws) to construction companies. What documentation would app store review accept? I've tried written explanations in response to no avail.
1
0
185
4w
Seeking guidance on re-review timeline
Hello, I'm looking for guidance on a submission that appears to be awaiting re-review following my response to a "2.1 Information Needed" message. App: Markets: Global Trading 24/7 App ID: 6756673679 Version: 1.0.6 Timeline (all times ET): Apr 17, 10:45 AM: Submission entered "Waiting for Review" Apr 17, 9:25 PM: Moved to "In Review" Apr 17, 10:14 PM: Received "2.1 Information Needed" message regarding the OTP demo account flow Apr 17, 10:45 PM: Replied in Resolution Center clarifying the OTP behavior Apr 20, 9:10PM: Still awaiting response, and in "Waiting for Review" status The App Review FAQ notes that messages in Resolution Center are generally responded to within 24 hours. My reply has now been pending for approximately 3 full days, so I wanted to check in here in case it would be helpful to surface this. Our prior two updates to our published app were approved quickly, and the 2.1 message concerned the demo account OTP flow, which I responded to in detail in Resolution Center. If anyone from App Review is able to take a look, I would very much appreciate it. Happy to provide any additional information that would help. Thank you, Chuck Bradford Dexari Inc.
1
0
197
Apr ’26
Guideline 4.3(b) Spam rejection for unique niche dating app — Appeal upheld, seeking guidance
Hello, My app "Tall - App de rencontre" (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. "THE BAKERY": A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize quality over quantity. I also have an existing community of over 1,000 people across multiple WhatsApp groups TALL FRANCE, 10K Instagram followers, and 44K TikTok followers — all specifically for tall people looking to connect. This proves real demand for this niche. I also noticed that the app "Score Dating" is currently live on the App Store in the Lifestyle category. Score blocks users who do not have a credit score of 675 or above. My app uses the same concept — a mandatory gate based on a specific criteria (height instead of credit score). If Score is accepted, I believe Tall should be evaluated with the same standard. I have responded to every rejection with detailed explanations and visual evidence, but received the same copy-paste response each time. I have a Meet with Apple consultation scheduled to discuss this further. Has anyone successfully overcome a 4.3(b) rejection for a niche app with genuinely unique features? Any guidance from Apple or the community would be greatly appreciated. Thank you, Frankie Babet
2
0
207
Apr ’26
Stuck in „Waiting for review”
My apps are stucked in „Waiting for revlew” for 6-7 days. What is going on? It’s not only my problem, a lot of users have the same problem, there are many forums with that issue. It’s pretty unbelievable for me, that in 2026 we have to wait about week to approve or reject an app. Ridiculous. Take the example of Google Play…. Regards.
1
0
61
Apr ’26
App Stuck in ‘Waiting for Review’ for 48+ Hours After Resubmission
Hi everyone, I’m experiencing a delay with my app review process and wanted to check if this is normal or if anyone has faced something similar. App Name: Finna: Budget Tracker Here’s the timeline: Apr 13: Submitted → Waiting for Review → In Review → Rejected Apr 15: Fixed the issues and resubmitted → Waiting for Review (since then, ~48+ hours now) Current status is still “Waiting for Review”, and it hasn’t moved to “In Review” yet after resubmission. A few points: -> This is not a brand-new submission (it was previously reviewed and rejected once). -> I addressed all rejection points carefully before resubmitting. -> No major feature changes, just fixes based on Apple’s feedback. Questions: Is it normal for resubmitted apps to take longer than the first review? Does rejection history affect queue priority? Should I wait more or consider contacting Apple Developer Support? Would appreciate insights from anyone who has gone through similar delays recently. Thanks!
2
0
150
Apr ’26
Subscriptions Stuck in review
Hello! My subscriptions have been stuck in review for a while. I have been chasing my tail trying to get the sandbox purchases to work but the subscriptions are not returning after "sale". Is this because the subscriptions are still in review? Will the purchase ever return a product in the sandbox environment if the products are still in review? How do we get the subscriptions approved? I have submitted them with the app multiple times. The app is rejected because I can't complete it without the subscriptions but the subscriptions are never reviewed. Help!
0
0
91
Apr ’26
Curious about the shift from iOS developer to full time indie developer Ask Me Anything 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
2
0
124
Apr ’26
Clarification on the Definition of "Drug Dosage Calculators" in Guideline 1.4.2
Hello, I am looking for a better understanding of Guideline 1.4.2, which states that "Drug dosage calculators" must be developed by drug manufacturers, hospitals, universities, or other approved entities. My main question is: What is Apple’s exact definition of a "Drug Dosage Calculator"? - Does the term exclusively refer to apps that calculate dosage (dose, interval, and treatment duration)? - Are apps that do not make clinical decisions, but only display bibliographic references based on user-entered data, also considered Drug Dosage Calculators? - If an app only performs basic mathematical operations on a dose value entered by the user, without suggesting medications or treatments, does it still fall under this restriction? I would like to better understand how Apple differentiates a medical support app (which only presents data) from a dosage calculator (which makes clinical decisions). I appreciate any insights from the community!
Replies
4
Boosts
0
Views
366
Activity
4w
AppTransaction.originalAppVersion returns "1.0" in App Review environment — not the actual build number
Hi, I'm using AppTransaction.originalAppVersion to detect whether a user originally purchased the app under the old paid model, so I can automatically unlock the app for them as a courtesy when migrating to freemium. Background On iOS, originalAppVersion returns CFBundleVersion (the build number). When I transitioned the app from paid (v1.x) to freemium (v2.0), I defined a numeric threshold for CFBundleVersion to distinguish legacy purchasers from new users: Build number below the threshold → v1.x purchase → auto-unlock Build number at or above the threshold → v2.0+ install → requires IAP In Production, originalAppVersion correctly returns the actual build number, and the comparison works as intended. Detection logic (simplified) // Determine environment via receipt URL func detectStoreEnvironment() -> String { if let url = Bundle.main.appStoreReceiptURL, url.lastPathComponent == "sandboxReceipt" { return "Sandbox" } return "Production" } // Legacy check using numeric comparison static func isLegacyPaidUser(version: String, threshold: String) -> Bool { guard !version.isEmpty else { return false } return version.compare(threshold, options: .numeric) == .orderedAscending } // In checkLegacyPurchase(): let version = appTransaction.originalAppVersion let isLegacy = isLegacyPaidUser(version: version, threshold: legacyBuildNumberThreshold) let env = detectStoreEnvironment() let shouldAutoUnlock = isLegacy && env != "Sandbox" The problem I know that in the Sandbox environment, originalAppVersion always returns "1.0" — this is mentioned in the AppTransaction documentation. My code already suppresses the auto-unlock for Sandbox (env != "Sandbox"). However, it appears that the App Review environment also returns "1.0" for originalAppVersion. Because the receipt URL path component is "receipt" (not "sandboxReceipt"), my environment detection classifies it as "Production" — so the Sandbox suppression doesn't apply. The reviewer is incorrectly identified as a legacy paid user and the app is unlocked without a purchase. This caused our v2.0 submission to be rejected under Guideline 2.1a. Questions Is it documented that the App Review environment returns "1.0" for AppTransaction.originalAppVersion, similar to Sandbox? Is there a reliable way to detect the App Review environment specifically — separate from both Sandbox and Production? For example, does the receipt URL differ, or is there another API? Is using originalAppVersion for legacy paid-user detection a supported pattern? If so, what is the recommended approach to handle the App Review case? Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
103
Activity
4w
App Store Review
I have a new app which has been submitted for review, and has been rejected.. The tester unable to see subscription settings.. He/she has not looked very far, they are in the app settings tab, and that was noted in the app submission. The likely issue is that this is an iPhone app, and specifically not for iPad.. Yet the reviewer used an iPad to test! This is the third consecutive rejection for administrative issues which have nothing to do with the app itself, and which, if the reviewers were to look properly, are not actually issues at all. This feels as though the reviewers are trying to get through as many reviews as possible in the shortest time possible, and not taking the time to examine an app submission properly. They are undermining months of hard work with a 30 second scan.
Replies
1
Boosts
0
Views
80
Activity
4w
Click "Update Review", or wait for Resolution Center reply?
My app (Markets: Global Trading 24/7, version 1.0.6, App ID 6756673679) was rejected on April 20 for Guideline 1.2. Apple's rejection message offered the option to demonstrate compliance via a screen recording, which we provided in Resolution Center the same day. The submission has remained in Rejected status while we await a response. Do we need to click "Update Review" to surface this to App Review, or are we supposed to wait in "Rejected" status until we get a Resolution Center reply? Thank you.
Replies
1
Boosts
0
Views
113
Activity
4w
Mac App Store review policy for Apple Event temporary exception entitlements
I’m looking for some advice regarding the usage of temporary exception entitlements in Mac App Store apps. Specifically the Apple Event Temporary Exception to communicate with other third party applications (not first-party macOS system apps): The Best Practices for Submitting Scriptable and AppleScript Apps to the Mac App Store section is a bit vague (how to 'request' a temporary entitlement?) and I couldn't find it mentioned in the Review Guidelines. Before designing, implementing and testing functionality based on the Apple Event Temporary Exception I’d like to know if these entitlements would: A. Always be rejected on the Mac App Store B. Only accepted in highly specific use cases C. Accepted if there is a clear use case and sufficient argumentation For this particular use case I’d like to send Apple Events to Adobe Illustrator and QuarkXPress. The application helps the user with some design tasks in their documents. The app requests the currently open documents and accesses document content to process used design elements. This is optional functionality that the user must explicitly enable in the app. I’m aware that the com.apple.security.scripting-targets entitlement is preferred. (Side question: are these always allowed or can they also be rejected for third party app scripting?) However, many third party applications don’t offer any scripting access groups in their definition, including Adobe Illustrator and QuarkXPress in this case. So before spending a lot of time implementing this feature I’d like to have some indication whether it is unlikely that sending Apple Events to third party apps will be allowed on the Mac App Store. Thanks for any insights!
Replies
5
Boosts
0
Views
352
Activity
4w
My App stuck in "Waiting for Review" two week
Hello everyone, My app (ID: 6756186616) was submitted on Mar 15, 2026, and has been stuck in "Waiting for Review" status for over 17 days. I contacted Developer Support (case #20000111565861) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds two week. Any recent experiences with long queues? Thanks!
Replies
7
Boosts
1
Views
309
Activity
4w
App approved - In-app purchase is "Waiting for Review"
The new version of our app uses Advanced Commerce API via in-app purchase. The app itself was approved but the in-app purchase associated with the app version is still Waiting for Review. Is there anything else we can do? Any way to expedite the review of the in-app purchase itself?
Replies
1
Boosts
0
Views
56
Activity
4w
App stuck in Waiting for Review
Hi, This is my first time releasing an app to the store and it's been stuck in a "Waiting to review" state for about 5 days now. From what I gathered, most apps should be reviewed within a 48 hour period. I was just curious if there's something blocking it being sent to the In Review state. Thanks for any help you can provide.
Replies
1
Boosts
0
Views
60
Activity
4w
Beta App Review stuck 3+ days
Hi all, I have a build in "Waiting for Beta App Review" that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incident, does re-uploading resolve it, or does the new build simply re-enter the same queue with the same delay? I have also submitted a support request via the Contact Us form, but wanted to check with the community in case others are seeing the same pattern this week. Thanks,
Replies
0
Boosts
0
Views
181
Activity
4w
Construction Draw App Stuck in Rejection Loop
My app is for a client that facilitates construction draws for construction companies. The app is stuck in a rejection loop for this reason: Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable Issue Description The app still provides loan services but does not meet all the requirements for apps providing these services. See below for additional information. These requirements give App Store users confidence that apps offering financial services are qualified to provide these services and will responsibly manage their data. Next Steps It would be appropriate to take the following steps to resolve this issue: The app facilitates loan or credit applications but you have not provided loan or business license documentation that demonstrates the app is authorized to provide these services. The client does not lend to consumers, nor individuals, and the client operates in states that do not require a lending license (including NMLS) to provide financing (such as construction draws) to construction companies. What documentation would app store review accept? I've tried written explanations in response to no avail.
Replies
1
Boosts
0
Views
185
Activity
4w
Please Review my app
Hello, I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.
Replies
1
Boosts
0
Views
52
Activity
4w
Seeking guidance on re-review timeline
Hello, I'm looking for guidance on a submission that appears to be awaiting re-review following my response to a "2.1 Information Needed" message. App: Markets: Global Trading 24/7 App ID: 6756673679 Version: 1.0.6 Timeline (all times ET): Apr 17, 10:45 AM: Submission entered "Waiting for Review" Apr 17, 9:25 PM: Moved to "In Review" Apr 17, 10:14 PM: Received "2.1 Information Needed" message regarding the OTP demo account flow Apr 17, 10:45 PM: Replied in Resolution Center clarifying the OTP behavior Apr 20, 9:10PM: Still awaiting response, and in "Waiting for Review" status The App Review FAQ notes that messages in Resolution Center are generally responded to within 24 hours. My reply has now been pending for approximately 3 full days, so I wanted to check in here in case it would be helpful to surface this. Our prior two updates to our published app were approved quickly, and the 2.1 message concerned the demo account OTP flow, which I responded to in detail in Resolution Center. If anyone from App Review is able to take a look, I would very much appreciate it. Happy to provide any additional information that would help. Thank you, Chuck Bradford Dexari Inc.
Replies
1
Boosts
0
Views
197
Activity
Apr ’26
IAP in review while app has been approved
Hey my app subscriptions are currently in review whilst my app has been approved 2 times, i need this to be approved to start marketing it.
Replies
0
Boosts
0
Views
127
Activity
Apr ’26
Guideline 4.3(b) Spam rejection for unique niche dating app — Appeal upheld, seeking guidance
Hello, My app "Tall - App de rencontre" (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. "THE BAKERY": A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize quality over quantity. I also have an existing community of over 1,000 people across multiple WhatsApp groups TALL FRANCE, 10K Instagram followers, and 44K TikTok followers — all specifically for tall people looking to connect. This proves real demand for this niche. I also noticed that the app "Score Dating" is currently live on the App Store in the Lifestyle category. Score blocks users who do not have a credit score of 675 or above. My app uses the same concept — a mandatory gate based on a specific criteria (height instead of credit score). If Score is accepted, I believe Tall should be evaluated with the same standard. I have responded to every rejection with detailed explanations and visual evidence, but received the same copy-paste response each time. I have a Meet with Apple consultation scheduled to discuss this further. Has anyone successfully overcome a 4.3(b) rejection for a niche app with genuinely unique features? Any guidance from Apple or the community would be greatly appreciated. Thank you, Frankie Babet
Replies
2
Boosts
0
Views
207
Activity
Apr ’26
Stuck in „Waiting for review”
My apps are stucked in „Waiting for revlew” for 6-7 days. What is going on? It’s not only my problem, a lot of users have the same problem, there are many forums with that issue. It’s pretty unbelievable for me, that in 2026 we have to wait about week to approve or reject an app. Ridiculous. Take the example of Google Play…. Regards.
Replies
1
Boosts
0
Views
61
Activity
Apr ’26
Waiting for review
My app is waiting for review for more than 48 hrs since Wednesday at 5:57 PM. It has been rejected, and errors were fixed with an updated new build. Is this normal?
Replies
3
Boosts
0
Views
170
Activity
Apr ’26
App Stuck in ‘Waiting for Review’ for 48+ Hours After Resubmission
Hi everyone, I’m experiencing a delay with my app review process and wanted to check if this is normal or if anyone has faced something similar. App Name: Finna: Budget Tracker Here’s the timeline: Apr 13: Submitted → Waiting for Review → In Review → Rejected Apr 15: Fixed the issues and resubmitted → Waiting for Review (since then, ~48+ hours now) Current status is still “Waiting for Review”, and it hasn’t moved to “In Review” yet after resubmission. A few points: -> This is not a brand-new submission (it was previously reviewed and rejected once). -> I addressed all rejection points carefully before resubmitting. -> No major feature changes, just fixes based on Apple’s feedback. Questions: Is it normal for resubmitted apps to take longer than the first review? Does rejection history affect queue priority? Should I wait more or consider contacting Apple Developer Support? Would appreciate insights from anyone who has gone through similar delays recently. Thanks!
Replies
2
Boosts
0
Views
150
Activity
Apr ’26
Subscriptions Stuck in review
Hello! My subscriptions have been stuck in review for a while. I have been chasing my tail trying to get the sandbox purchases to work but the subscriptions are not returning after "sale". Is this because the subscriptions are still in review? Will the purchase ever return a product in the sandbox environment if the products are still in review? How do we get the subscriptions approved? I have submitted them with the app multiple times. The app is rejected because I can't complete it without the subscriptions but the subscriptions are never reviewed. Help!
Replies
0
Boosts
0
Views
91
Activity
Apr ’26
Curious about the shift from iOS developer to full time indie developer Ask Me Anything 🚀📱
Hey everyone 👋 I have 14 years of experience in iOS development, starting in my mid-teens and later working as a senior and lead developer with Fortune 50 companies. Around 1.5 years ago I began my indie journey as a side hustle, and for the past 3 months I have been building apps full time with a growing portfolio and increasing revenue 📈 I currently handle everything myself including development, ASO, and design, with marketing planned for later 🚀 I just shipped a major release last week and taking a relaxed week now, so feel free to ask anything about iOS development, indie life, ASO, monetization, or related topics 💬
Replies
2
Boosts
0
Views
124
Activity
Apr ’26
Please check my last app update
Hello, I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.
Replies
0
Boosts
0
Views
30
Activity
Apr ’26