# Google Play Broken Functionality rejection

> Google Play rejected the app for Broken Functionality — a crash, freeze or blank screen? How to find the cause in Play Console and resubmit.

**Broken Functionality — Broken Functionality: it crashed or didn’t load.** Google’s review saw the app crash, freeze or open on a blank screen. Wrapped apps usually fail on a web build that doesn’t load on the device, API calls that only work from your domain, or a login that fails on a fresh install.

- Google Play · Broken Functionality. Broken Functionality: it crashed or didn’t load.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/google-play-broken-functionality
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

Google’s review saw the app crash, freeze or open on a blank screen. Wrapped apps usually fail on a web build that doesn’t load on the device, API calls that only work from your domain, or a login that fails on a fresh install.

## Why reviewers send it

Google’s review and pre-launch report install the app on real devices. A crash on startup, a freeze, or a web build that never loads breaks the Broken Functionality policy, whatever the listing promises.

## The message Google Play sends

```
Issue found: Violation of Broken Functionality policy

We found that your app doesn’t load properly or crashes on startup. Apps that crash, force close, freeze, or otherwise function abnormally are not allowed on Google Play.
```

The exact wording changes from one review to the next; the policy name is what to look for.

## How to fix it

1. Check Android vitals and the pre-launch report in Play Console for the crash and the device.
2. Install the build from internal testing on a real device and sign up as a new user.
3. Use full https:// URLs, and allow the app’s origin (https://localhost) in your backend’s CORS settings.
4. Upload a fixed build with a higher version code and resubmit.

If the crash comes from the build itself, paste the log into the [build error explainer](https://capwr.app/free-tools/build-error-explainer).

## Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

```
Make sure the app never shows a blank screen: use full https:// URLs for every API call, show a visible error with a retry button when a request fails, and remove any placeholder content.
```

## What to tell Google Play

Replace the [brackets] with what you actually changed:

```
We fixed the issue on [screen / device] in version [x]: [cause]. We tested a fresh install on [devices].
```

## Got a different message?

Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other Google Play rejections

- [Google Play webview and minimum functionality](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-webview-minimum-functionality)
- [Google Play invalid privacy policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-invalid-privacy-policy)
- [Google Play Data safety section inaccurate](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-data-safety-inaccurate)
- [Google Play missing login credentials](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-missing-login-credentials)
- [Google Play account deletion requirement](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-account-deletion)
- [Google Play photo and video permissions policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-photo-video-permissions)
- [Google Play Payments policy: use Play Billing](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-payments-policy)
- [Google Play Metadata policy violation](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-metadata-policy)
- [Google Play production access refused](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied)

## Fixed it? Ship the new build to Google Play

CapWrapp builds and signs the Android app from your GitHub repo, bumps the version code, and uploads it to Google Play — then promotes it to production when you are ready.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)