Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageFirst: read the rejection like a reviewer
Ten minutes of triage save days of guessing.
Find the guideline number
Apple names the guideline (for example 4.2, 2.1, 5.1.1) in Resolution Center; Google names the policy (for example Minimum functionality, User Data) in the Policy status page. The number tells you whether the fix is in your web app, in the WebViewGold settings or in the store listing.
Map it to your Base44 project
Most rejections of Base44 apps fall into five buckets: not app-like enough (4.2 / minimum functionality), something did not load (2.1 / broken functionality), privacy paperwork (5.1.1 / Data safety, account deletion), login rules (4.8 Sign in with Apple, blocked Google login) and payments (3.1.1 / Play Billing).
Reproduce what the reviewer saw
Open the Base44 app in airplane mode, on an iPad, with a fresh account, with the demo login you gave them. Run the free readiness check on your URL. Attach screenshots of what they attached.
Fix, then reply, then resubmit
Change the web app (instant) or the native setting (new build), write a short factual reply naming what changed, and submit the new build. Second reviews are usually faster than the first.
App Store guidelines that hit Base44 apps
Apple reviews the behavior of the app, not the tool that built it. These are the guidelines behind most rejections of Base44 apps, with the fix for each.
- 4.2
Minimum Functionality
The app must offer more than a repackaged website. Responsive layout, native navigation and at least one native capability (push notifications, offline screen, native sharing, biometric login) make the difference. WebViewGold switches these on with one setting each.
- 2.1
App Completeness
No placeholder content, no dead links, no crashes. If content sits behind a login, provide a demo account in the App Review notes.
- 5.1.1
Privacy
A public privacy policy URL is mandatory. Apps that let users create accounts must also let them delete the account inside the app.
- 4.8
Login Services
If the app uses Google, Facebook or another third-party or social login for the user's account, it must also offer an equivalent login that limits data to name and email, lets users keep their email private and does not track them for advertising. Sign in with Apple is the safe way to meet this. An app that only uses its own email/password login is not affected.
- 3.1.1
In-App Purchase
Digital goods and subscriptions sold inside the app must use Apple's In-App Purchase. Physical goods and real-world services can keep Stripe or PayPal.
- 2.3
Accurate Metadata
Screenshots, description and app name must match what the app does. Do not mention other platforms or "beta" in the listing.
Google Play policies that hit Base44 apps
Google's review is more automated and more paperwork-driven. The policies below cover most rejections of Base44 apps.
- Minimum functionality
Spam and minimum functionality policy
Google rejects apps that only wrap a website without the website owner's permission or that offer no real functionality. Wrapping your own product with added native features is fine.
- Data safety
User Data policy
Every app needs a privacy policy URL and a completed Data safety form that lists what the app and its SDKs collect.
- Account deletion
User Data policy
Apps that let users create accounts must offer account deletion inside the app and via a web link you provide in the Play Console.
- Testing requirement
Personal developer accounts
Personal accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can request production access.
- Target API level
Target API requirements
New apps must target a recent Android version. WebViewGold updates keep the template current; just build with the latest version.
- Payments
Google Play Billing
Digital goods and subscriptions sold in the app generally must use Google Play Billing (WebViewGold supports RevenueCat). Physical goods and services may use other payment methods.
Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!
What is specific to Base44 projects
Because Base44 apps usually run on React front end generated by Base44 with Base44's own built-in database, authentication and integrations, with Base44 built-in authentication (email and password, Google, Microsoft, Facebook and Apple login) and Stripe integration, these are the points we see in support for Base44 rejections.
- Base44 apps often require login before any content is visible. Apple reviewers need a demo account: enter test credentials in the App Review notes, or allow guest browsing.
- Google login is blocked inside plain WebViews; WebViewGold's Social Login Helper fixes this without changes to your Base44 app.
- If you turn on Google, Microsoft or Facebook login, Apple Guideline 4.8 requires an equivalent login option that limits data to name and email, lets users keep their email private and does not track them. Your own email/password login does not reliably meet that bar, so also enable Apple login in the Base44 authentication settings (WebViewGold detects Sign in with Apple automatically). An app with only Base44's email login and no social login is not affected.
- Apps with user accounts must offer account deletion in-app (Apple 5.1.1, Google Play policy). Add a Delete account action in your Base44 settings page.
- Add a privacy policy page in Base44 and link it from the app footer; both stores require its URL.
- Made with Base44: Disable the Base44 branding in the app settings if your plan allows it, so no link to another platform sits inside your store app.
Let Base44 fix the web-app side
Paste the rejection text together with this prompt into Base44; it applies the changes reviewers typically ask for.
Prompt to paste into Base44
The app built from this project was rejected by the app store review. Here is the rejection text: [PASTE REJECTION TEXT]. The app runs inside the WebViewGold native WebView wrapper (iOS and Android). 1. Explain in one paragraph which guideline or policy is cited and what the reviewer saw. 2. Apply every fix that belongs in the web app: responsive layout from 320px, 44px tap targets, safe-area padding on fixed bars, /privacy and /terms pages, a Delete account action with confirmation, friendly error and retry states, no external promotional links or "download our app" banners, no placeholder content, a demo account seeded for reviewers. 3. If the fix is native (push notifications, offline screen, Sign in with Apple provider, in-app purchases via RevenueCat), tell me exactly what to enable in the WebViewGold configuration and what to change in the backend. 4. Draft a short, factual reply to the reviewer that lists what changed.
Reply template for the reviewer
Short, factual, specific. Reviewers read hundreds of these a day.
Resolution Center / Policy status reply
Thank you for the review. We have addressed the points raised: 1. [Guideline/policy number]: [what was wrong] → [what changed, where to find it in the app, e.g. Settings → Delete account]. 2. Native functionality: the app provides push notifications for [use case], an offline mode with retry, and [Face ID login / native sharing / QR scanning], none of which are available on the website. 3. Demo account: [email] / [password]. The main features are reachable from the home screen after login. A new build ([version]) with these changes has been uploaded. Please let us know if anything else is needed.
Frequently asked questions
Does Apple or Google reject apps because they were built with Base44?
No. Neither store sees or cares about the builder. Rejections are about behavior (app-like UI, native features), completeness, privacy paperwork, login rules and payments. Fix those and the Base44 origin is irrelevant.
How many times can I resubmit?
As often as needed. Each submission is reviewed again, usually faster than the first one. Repeated identical submissions without changes are the only thing that annoys reviewers.
Should I reply or just resubmit?
Both: reply with a short list of what changed (or, politely, what the reviewer missed), then submit the new build. A reply without a new build rarely changes the outcome unless the rejection was a misunderstanding.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Cloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.