ChatGPT & Codex
A rejection is a to-do list written by a reviewer. Apple names the guideline, Google names the policy, and both describe what they saw. Codex is good at turning that into code changes, as long as you tell it which fixes belong in the web app and which belong in the WebViewGold project. Here is the triage routine we use in support.
From $109 one-time per platform, or let our team do it all from $698.
Most rejections list two or three points. Treat each one separately.
Each point is one of four kinds: WEB (your code), NATIVE (WebViewGold configuration or a native feature), METADATA (listing, screenshots, privacy answers, review notes) or CONTENT (what the app is about). Codex can fix the first kind, instruct you on the second and third, and only you can decide the fourth.
Use the triage prompt below in the repository. Include the full message and any screenshots the reviewer attached (describe them if you cannot attach images). Codex maps each point to files and routes and implements the web fixes.
A web fix is live as soon as you deploy, but check it in the actual app build with the reviewer's eyes: airplane mode, the demo account, every tab. TestFlight and Google's internal testing track exist for this.
Enable or configure the WebViewGold feature (push provider, offline screen, Sign in with Apple capability, RevenueCat keys), rebuild, upload. Fix screenshots, the description, the App Privacy answers or the Data safety form in the console.
Reply in Resolution Center (Apple) or appeal / resubmit in the Play Console with a factual list of changes, then submit the new build. Follow-up reviews are usually faster than the first one.
Below is a rejection message from App Review (or Google Play) for the native app version of this web app. The native app is a WebViewGold wrapper that loads our production URL; the wrapper handles push notifications, the offline screen, social login helpers and in-app purchases natively, and everything else is this codebase. For each point in the rejection: 1) quote the guideline or policy; 2) say what the reviewer most likely saw in our app, with specific files and routes; 3) classify the fix as WEB (this repo), NATIVE (wrapper configuration) or METADATA (store listing); 4) implement WEB fixes now; 5) for NATIVE and METADATA fixes, write exact instructions for me. Finish with a draft reply to the reviewer that states what changed, in plain factual language, without apologies and without arguing. Rejection message: [PASTE HERE]
| Guideline | What the reviewer saw | Fix | Where |
|---|---|---|---|
| Apple 4.2 Minimum functionality | A website in a frame: desktop layout, no native behavior | Push notifications, offline screen, share sheet or Face ID; hide website-only UI; describe the native features in the review notes | NATIVE + WEB + METADATA |
| Apple 2.1 Completeness | Blank screen, broken login, placeholder text, dead links | Error states, working demo account, remove placeholders, HTTPS everywhere | WEB + METADATA |
| Apple 5.1.1 Data collection | No privacy URL or no account deletion | /privacy route, Delete account in settings with server-side deletion | WEB + METADATA |
| Apple 4.8 Login services | Google login without Sign in with Apple | Add the Apple provider and button; WebViewGold handles the flow | WEB |
| Apple 3.1.1 In-app purchase | Stripe checkout for a subscription or credits inside the app | Route digital goods through revenuecat://purchase?… in the native app; keep Stripe on the web | WEB + NATIVE |
| Apple 2.3 Accurate metadata | Website screenshots, "beta", features that do not exist | Screenshots from the built app, honest description | METADATA |
| Apple 2.5.1 / unused permissions | Camera or location usage strings for features the app does not have | Remove unused permission texts in the WebViewGold project | NATIVE |
| Apple 4.0 Design | Content under the notch or home indicator, tiny buttons | Safe-area insets, 44 px targets | WEB |
| Apple 1.2 / Google UGC and AI content | Chat or community without report and block | Report action, block option, moderation, contact in the policy | WEB |
| Google Data safety mismatch | Form says no data collected, app sends analytics or push tokens | Correct the form to match the code | METADATA |
WebViewGold has allowed us the shortest and most efficient time-to-market ever possible from among all the other app platforms we have ever tried during the past 5 years. I don’t know why I hadn’t discovered you sooner, but I am really, really glad I did. Currently nearing 6000 app downloads on both iOS App Store & Google Play Store without any problem!
Layout, legal pages, account deletion, error states, Sign in with Apple button, routing purchases through the bridge, report buttons. Live on the next deploy, no new build needed unless the reviewer wants to see a new version number.
Enable push, offline screen, RevenueCat keys, Social Login Helper triggers, permission strings, icon and name. Change the value, rebuild, upload. The Cloud Builder does the rebuild in the browser.
Screenshots, description, keywords, privacy URL, App Privacy and Data safety answers, review notes, demo account. No build needed; edit and resubmit the same binary when nothing else changed.
Gambling, medical claims, copyrighted material, impersonation. Codex cannot code around these. Decide whether to change the product or the scope before resubmitting.
Keep it to what changed and where the reviewer can see it. A reply that works looks like this: "Thank you for the review. We addressed the points as follows. Guideline 4.2: the app now sends push notifications for order updates (OneSignal), shows a native offline screen and offers Face ID login for the account area; website elements such as the footer and cookie banner are hidden in the app. Guideline 5.1.1: account deletion is available under Settings → Account → Delete account and removes all user data. The demo account remains [email protected] / Demo1234. Build 1.0.1 (3) contains these changes." Nothing else: no explanation of your business model, no mention of other apps that got through.
If you believe the reviewer missed something (for example a feature behind the login they did not use), say where it is and attach a screenshot. Politeness and precision beat volume. A reusable version is in the Resolution Center reply template; the Google equivalent is the Play Console appeal template.
Yes, because the fixes touch routes, settings screens and server functions. Run it in the repository (CLI or IDE) or as a cloud task on the GitHub repo rather than pasting snippets into ChatGPT.
Check that the reviewer could see them: the permission prompt must appear in their session, and the review notes must say what the notifications are for. Add a second visible native feature (offline screen, share sheet, Face ID) and hide website-only elements inside the app.
Policy rejections show in the Play Console under Policy status with an appeal option; for most issues you simply upload a corrected release. Use the console message to describe what changed.
As often as needed; each submission is reviewed again. If you have been rejected three times for the same guideline, read the dedicated guide on what to do next before submitting again.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$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 page$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 demo$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.
App Store & Google Play approval guarantee – or your money back within 14 days
Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.
