An old download
You downloaded WebViewGold months ago, configured it, and only now submit. Templates downloaded before the yearly deadline target the previous level. Updates are free; get the current version from where you bought it.
What the target API level is and why Google enforces it
Every Android app declares which Android version it was built and tested for, the target SDK. The system uses it to decide which modern behaviors apply to the app: runtime permission prompts, the notification permission, restrictions on background work, the photo picker, and so on. An app that targets an old version keeps old, less private behaviors. Google therefore requires that new apps and updates target a recent Android release, and it raises the bar once a year, usually in late summer, to the previous year's major release.
You notice it in one of two ways. Either Play Console refuses the upload or the release with a message that names the required level, or Google warns that your existing app will be hidden from users on newer devices if it is not updated. Both have the same fix: rebuild from a template that targets the current level.
Why your bundle was built too old
A copied project
You cloned the project of your last app to save time. The copy carries the old build.gradle with it.
An old toolchain
An outdated Android Studio or Gradle plugin can refuse to build with a newer target or silently use cached SDK components. Update the IDE and accept the SDK updates it proposes.
APK instead of App Bundle
Not an API level issue, but it appears in the same upload step: Play requires a signed .aab for new apps. WebViewGold builds App Bundles from Android Studio and in the Cloud Builder.
Fix it: update the template and rebuild
About thirty minutes in Android Studio. Keep the old project until the new build is live.
Download the current WebViewGold for Android
Updates are free for the lifetime of your license. Get the latest version and unzip it next to your existing project, not over it.
Carry over your configuration
Copy your values from the old Config.java into the new one (URL, package name, push IDs, feature flags), your strings.xml texts, the AdMob IDs if you use ads, the app icons in the mipmap folders, the splash graphics, and any edits you made in AndroidManifest.xml such as removed permissions or deep-link intent filters. A side-by-side diff of both Config.java files prevents forgotten flags.
Use the same signing key
Build the signed App Bundle with the same upload keystore you used before. With Play App Signing, Google holds the app signing key and only your upload key must match. A bundle signed with a new keystore is refused for an existing app.
Increase the version code
Play accepts a bundle only if its version code is higher than any previously uploaded one, including bundles on testing tracks.
Build and upload
Generate the signed bundle in Android Studio (Build menu), then upload the .aab to the track you want. The warning disappears if the target level now meets the requirement.
Test once on a device
Install the new build from the internal testing track and open your key screens. Newer target levels change how notifications, file access and back navigation behave; the updated template handles these, but a quick look costs nothing.
With a good optimized version of your web app you can have a stunning mobile app within a couple of minutes. Additionally to that the customer service is very nice and very helpful! I can just recommend WebViewGold :-)
Cloud Builder: always the current template
If you use the WebViewGold Cloud Builder, there is no template on your computer to go stale. Each build uses the current WebViewGold version, so the target API level is whatever Google currently requires. Open your project, keep your settings, rebuild, and upload to Play Console from the browser. This is also the easiest way to handle the yearly deadline for an app you have not touched in a while: a rebuild without changing anything in your web app.
The three SDK numbers in build.gradle
| What it means | What Google checks | |
|---|---|---|
targetSdk | The Android version your app is built and tested for; controls which modern behaviors apply | This one. It must meet the current requirement for new apps and updates |
compileSdk | The SDK the compiler uses; must be at least the target level | Indirectly: a too-low compile SDK prevents a higher target |
minSdk | The oldest Android version the app installs on | Not required by policy; it only decides which devices see the app |
Frequently asked questions
Which API level do I need right now?
Play Console tells you in the upload error and on the app dashboard. The requirement moves every year, so always build from the current WebViewGold template instead of relying on a number from an old forum post.
Will my existing users be affected while I rebuild?
No. The live version keeps working. The deadline affects the visibility of your app for new users on newer devices and your ability to publish updates.
Do I need to change anything in my web app?
No. The target API level is a property of the native shell. Your Lovable, Bolt or Replit app stays untouched; only the WebViewGold project is rebuilt.
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 pageCloud 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.