u/Greedy-Discussion-53

After spending way too long researching why no-code apps get rejected on the App Store, I found some patterns that kept coming up — especially for Adalo, FlutterFlow, and Bubble founders.

Here's what actually causes rejections (not the obvious stuff):

1. Privacy policy linked in the wrong place

Most founders add it to App Store Connect but forget to make it accessible from inside the app. Apple checks both. A button in your Settings screen pointing to your policy URL is all you need.

2. App Review Notes left blank

This field in App Store Connect is where you give the reviewer demo credentials and explain how to test your app. Over 40% of Guideline 2.1 rejections happen because the reviewer simply couldn't access the app. Most founders have never heard of this field.

3. Bubble WebView wrapper risk

If you're using Natively or BDK Native to wrap a Bubble app, you're at risk of Guideline 4.2 rejection (Minimum Functionality). Apple has been cracking down on WebView wrappers harder in 2025-26.

4. No Restore Purchases button

If your app has any IAP or subscriptions, Apple requires a visible Restore Purchases button. Reviewers check for this specifically. Missing it = rejection.

5. The Data Safety form (Google Play)

Most no-code platforms bundle Firebase/Crashlytics by default. You have to declare that data in Google's Data Safety form — not just your own app's data. Most founders only declare their own data and miss the SDK data entirely.

6. Age rating mismatch

If your app has any form of chat or user interaction, you cannot rate it 4+. Both stores will reject this automatically.

7. Screenshots showing unbuilt features

Reviewers open your app and compare it to your screenshots. If you show a feature that doesn't exist yet — rejection.

8. New Google Play accounts need 12 testers for 14 days

Before you can publish to production on a new Google Play account, you need to complete closed testing with 20 real testers for 14 consecutive days. Most first-time founders discover this gate only after they think they're ready to launch.

----------

I built a free checker that scans for all of these (and more) before you submit: Check Comment

Hope this saves someone a rejection cycle.

After spending way too long researching why no-code apps get rejected on the App Store, I found some patterns that kept coming up — especially for Adalo, FlutterFlow, and Bubble founders.

Here's what actually causes rejections (not the obvious stuff):

1. Privacy policy linked in the wrong place

Most founders add it to App Store Connect but forget to make it accessible from \\\*inside\\\* the app. Apple checks both. A button in your Settings screen pointing to your policy URL is all you need.

2. App Review Notes left blank

This field in App Store Connect is where you give the reviewer demo credentials and explain how to test your app. Over 40% of Guideline 2.1 rejections happen because the reviewer simply couldn't access the app. Most founders have never heard of this field.

3. Bubble WebView wrapper risk

If you're using Natively or BDK Native to wrap a Bubble app, you're at risk of Guideline 4.2 rejection (Minimum Functionality). Apple has been cracking down on WebView wrappers harder in 2025-26.

4. No Restore Purchases button

If your app has any IAP or subscriptions, Apple requires a visible Restore Purchases button. Reviewers check for this specifically. Missing it = rejection.

5. The Data Safety form (Google Play)

Most no-code platforms bundle Firebase/Crashlytics by default. You have to declare that data in Google's Data Safety form — not just your own app's data. Most founders only declare their own data and miss the SDK data entirely.

6. Age rating mismatch

If your app has any form of chat or user interaction, you cannot rate it 4+. Both stores will reject this automatically.

7. Screenshots showing unbuilt features

Reviewers open your app and compare it to your screenshots. If you show a feature that doesn't exist yet — rejection.

8. New Google Play accounts need 20 testers for 14 days

Before you can publish to production on a new Google Play account, you need to complete closed testing with 20 real testers for 14 consecutive days. Most first-time founders discover this gate only after they think they're ready to launch.

----------

I built a free checker that scans for all of these (and more) before you submit: Check Comment

It covers Apple App Store and Google Play, takes about 13 minutes, and also generates your App Review Notes automatically. Free to use — there's also a $19 fix guide if you want the step-by-step instructions for each issue.

Hope this saves someone a rejection cycle.

After spending way too long researching why no-code apps get rejected on the App Store, I found some patterns that kept coming up — especially for Adalo, FlutterFlow, and Bubble founders.

Here's what actually causes rejections (not the obvious stuff):

1. Privacy policy linked in the wrong place

Most founders add it to App Store Connect but forget to make it accessible from \\\*inside\\\* the app. Apple checks both. A button in your Settings screen pointing to your policy URL is all you need.

2. App Review Notes left blank

This field in App Store Connect is where you give the reviewer demo credentials and explain how to test your app. Over 40% of Guideline 2.1 rejections happen because the reviewer simply couldn't access the app. Most founders have never heard of this field.

3. Bubble WebView wrapper risk

If you're using Natively or BDK Native to wrap a Bubble app, you're at risk of Guideline 4.2 rejection (Minimum Functionality). Apple has been cracking down on WebView wrappers harder in 2025-26.

4. No Restore Purchases button

If your app has any IAP or subscriptions, Apple requires a visible Restore Purchases button. Reviewers check for this specifically. Missing it = rejection.

5. The Data Safety form (Google Play)

Most no-code platforms bundle Firebase/Crashlytics by default. You have to declare that data in Google's Data Safety form — not just your own app's data. Most founders only declare their own data and miss the SDK data entirely.

6. Age rating mismatch

If your app has any form of chat or user interaction, you cannot rate it 4+. Both stores will reject this automatically.

7. Screenshots showing unbuilt features

Reviewers open your app and compare it to your screenshots. If you show a feature that doesn't exist yet — rejection.

8. New Google Play accounts need 20 testers for 14 days

Before you can publish to production on a new Google Play account, you need to complete closed testing with 20 real testers for 14 consecutive days. Most first-time founders discover this gate only after they think they're ready to launch.

----------

I built a free checker that scans for all of these (and more) before you submit: Check Comment

It covers Apple App Store and Google Play, takes about 13 minutes, and also generates your App Review Notes automatically. Free to use — there's also a $19 fix guide if you want the step-by-step instructions for each issue.

Hope this saves someone a rejection cycle.