Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

App Store rejection

Guideline 2.3 (Accurate Metadata): fixing screenshots, names and descriptions after a rejection

Metadata rejections are the cheapest to fix: most of them need no new build. Apple wants the listing to show the real app, in an honest voice, without references to other platforms. Here is what reviewers flag in vibe-coded listings and how to redo yours in an hour.

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

What Guideline 2.3 covers

Section 2.3 is about the truthfulness of everything around the binary: screenshots, previews, name, subtitle, keywords, description, category, age rating and the "What's New" text. The principle is simple: a customer who reads the listing must get exactly the app that is described, and reviewers compare the two side by side.

Vibe coders rarely lie on purpose; the usual failure is speed: browser screenshots of the website, a ChatGPT description that promises features not yet enabled, a mention of the Android version, a name padded with keywords. Each has its own 2.3 sub-number.

The 2.3 sub-rules that show up in rejections

  • 2.3.3

    Screenshots show the app in use

    Screenshots must be captured from the app itself and show it being used, not the website, a splash screen, a login page or marketing artwork alone.

  • 2.3.7

    Unique name, honest keywords

    Choose a unique app name and accurate keywords. Do not pack the name, subtitle or keyword field with other apps' names, trademarks, pricing or generic terms.

  • 2.3.8

    Suitable, non-placeholder metadata

    Icons, screenshots and previews must be suitable for every audience, and reviewers cite this section when metadata still contains template or placeholder text.

  • 2.3.10

    Focus on the Apple platform

    Do not mention or show other mobile platforms in the app or the listing. "Also available on Android" and Android UI in screenshots are typical hits.

Typical mistakes in vibe-coded listings

Browser screenshots

A Safari or Chrome window with the website, sometimes with the address bar visible. Reviewers spot it instantly. Capture from the installed TestFlight build instead.

AI mockups

Beautiful generated screens showing a chat feature or a dark mode that does not exist in the app. Mockups are fine only if the screen exists and looks the same.

Platform mentions

"Available on Android too", a Google Play badge in the first screenshot, or "beta" and "early access" in the subtitle.

Stuffed name

"Taskly - Todo Notes Planner Calendar Habit" is a 2.3.7 rejection. Use the name alone, put the descriptor in the subtitle (30 characters) and the rest in the keyword field (100 characters).

Promises the app cannot keep

Descriptions that list push notifications, offline access or Face ID because the AI wrote them. Enable the feature in WebViewGold or remove the sentence.

I am very happy I bought this app! Extremely easy and great documentation. Was in contact with the customer service, they replied very quickly and very friendly. They solved my question within a day. 10/10 would recommend.

Nelis Geiger · CodeCanyon

Produce honest screenshots from the real app in twenty minutes

  1. Install the exact build

    Use the TestFlight build you submitted. Log in with the demo account so the screens have real-looking data, and switch off notifications and the clock clutter if you like.

  2. Capture on the sizes App Store Connect asks for

    The upload form lists the required iPhone (and, if your app runs on iPad, iPad) display sizes. Take the screenshots on those devices or simulators; do not scale a phone screenshot into an iPad slot.

  3. Lead with the core screen, not the login

    The first two screenshots should show what the app does. Login, onboarding and settings go last or not at all.

  4. Match name, icon and screenshots to the binary

    The App Store name should match the name on the device (Product Name and Bundle Display Name in the WebViewGold project, see app name and icon docs). The icon in App Store Connect must be the one in the build.

  5. Rewrite the description with only what exists

    Use the prompt below, then read it once on the installed app: every claim must be visible in a screen the reviewer can reach.

Prompt: rewrite your description so it passes 2.3

Prompt for ChatGPT, Claude or Gemini
Rewrite my App Store description. Rules: mention only features that exist in the current iOS build (list below). No mention of Android, Google Play, web browsers, beta, early access, coming soon, or the tool I built the app with. No superlatives like best or number one, no other apps' names, no trademarks I do not own, no prices except the exact in-app purchase prices I list. Plain, friendly, second person, max 2,500 characters, first sentence states what the app does. Also give me a 30-character subtitle and a comma-separated keyword list under 100 characters without repeating words from the name.

App name: [name]
What it does: [one paragraph]
Features in the iOS build: [list: e.g. push reminders, Face ID lock, offline screen, native share, Sign in with Apple]
In-app purchases: [names and prices, or none]

Frequently asked questions

Can I use screenshots with marketing text and a device frame?

Yes. The screenshot inside the frame must come from the app and show it in use; captions and backgrounds around it are fine.

I mentioned the Android version in the description. Is that really a rejection?

Yes, Guideline 2.3.10. Remove any reference to other mobile platforms from the listing, the screenshots and the app itself, including Google Play badges in your web footer when loaded in the app.

Do I need iPad screenshots?

Only if the app is set to run on iPad. If it is, App Store Connect requires iPad-sized screenshots of the real iPad layout; a stretched phone layout will be noticed. See the iPad guide for the layout side.

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.

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 page

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 demo

Full 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 WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your app?

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.