# Troubleshooting | Symptom | Cause | Fix | | --- | --- | --- | | Blank screen inside Cherry, "refused to connect" in the console | Your page forbids framing | Send `Content-Security-Policy: frame-ancestors 'self' https://chat.cherry.fun https://cherry.fun https://*.cherry.fun` and remove `X-Frame-Options` | | The app never becomes ready | The SDK is not loaded on the page Cherry opens, or the provider is not mounted | Mount `CherryMiniAppProvider` at the root of the page at your listed URL | | The app opens on its login screen inside Cherry | It ignores the launch token | Sign in from `launchToken` when inside Cherry; keep your login only outside it | | Backend rejects every token | Wrong audience or issuer, or clock skew | `audience` is your app ID, `issuer` is `https://chat.cherry.fun`; allow a few seconds of leeway | | Signed in, then logged out on the next request | Your session lives in a cookie, which browsers drop in frames | Keep the session in memory and send it in an `Authorization` header | | `POLICY_DENIED` with `TX_LIMIT` or `DAILY_LIMIT` | Above your trust tier's limits | Offer a smaller amount, or verify to lift the limits | | `POLICY_DENIED` with `FORBIDDEN_INSTRUCTION` | The transaction uses something your tier cannot (approvals, authority changes, durable nonces, subscriptions) | Remove it from the transaction | | Wallet requests do nothing on mobile | The page navigated to another origin | Keep the app on its listed origin; open other sites as external links | | The "Framing" check fails but the app loads in your browser | The header is missing on the exact URL you listed, often behind a redirect | Check the response headers of the final URL after redirects | | The Terms check warns about the operator | Your Terms or Privacy Policy do not name your legal entity | Add the operator's legal name to both documents | | Domain proof fails | `https:///.well-known/cherry-app.json` is missing, redirects, is not JSON or names another app | Serve `{ "appId": "YOUR_APP_ID" }` there over https with a 200, on the app URL's origin and every allowed origin | | Publishing refused: the origin is used by another listed app | One origin belongs to one listed app | Use an origin of your own. If the domain is yours, serve the domain proof file on it: it takes the origin over from a listing that never proved it | | Users lose their account after switching wallets | Your backend keys users by `sub`, the wallet | Key users by `cherry_id ?? sub` from `verifyLaunchToken(token, { appId })` | ## Automated test results Every result in the [automated test](https://portal.cherry.fun/docs/mini-apps/listing.md#automated-test) names its fix. The common causes: | Result | Cause | Fix | | --- | --- | --- | | `frame_loads` fails on `frame-ancestors` or `X-Frame-Options` | Your page forbids framing, often only on the final URL after a redirect or only on HTML served by a CDN rule | Send `Content-Security-Policy: frame-ancestors 'self' https://chat.cherry.fun https://cherry.fun https://*.cherry.fun` on every HTML response and remove `X-Frame-Options` | | `frame_loads` fails with HTTP 403 or 503 | A bot challenge (Cloudflare, Vercel) or a login wall answers the test's browser | Let the listed URL load without a challenge, at least inside a frame | | `frame_loads` fails on a redirect to another origin | The listed URL sends the browser elsewhere, so Cherry cannot talk to the page | List the final URL as your app URL | | `handshake` fails with no `cherry:ready` | The SDK is not on the page at your listed URL, `init()` waits for a click, or the app crashes before it runs | Call `await cherry.init()` (or mount `CherryMiniAppProvider`) as the page starts, and check the console lines in the result | | `handshake` fails on an untrusted origin | Your code narrowed the SDK's trusted origins, or the page runs on an origin missing from Allowed origins | Keep the SDK defaults; serve the app from its listed origin | | `signed_in` fails although sign-in works in your browser | Your session lives in a cookie, which a phone drops inside a frame, or the app waits for a button | Sign in from the launch token on load and keep the session in memory, sent in an `Authorization` header | | `signed_in` fails with your backend answering 401 to a valid token | Wrong `audience` or `issuer`, or no clock leeway | `audience` is your app ID, `issuer` is `https://chat.cherry.fun`, keys from `https://chat.cherry.fun/.well-known/jwks.json`, a few seconds of leeway | | `no_connect_prompt` fails | A **Connect wallet** or **Select wallet** button is visible inside Cherry, or the app signs a message to log in | Hide wallet buttons when `isInsideCherry()` is true and use the launch token as the login; register `CherryWalletAdapter` with `autoConnect` | | `backend_verifies_token` fails: "accepts tokens for another app" | Your backend checks the signature but not which app the token is for (`aud` or `app_id`), or decodes the token without verifying it | Verify with your app ID: `verifyLaunchToken(token, { appId })`, or jose `jwtVerify` with `audience` set to it | | `backend_verifies_token` fails: "accepts expired tokens" | Expiry is not checked, or your backend caches a session past the token's life without checking it once | Keep the expiry check on and answer 401 | | `backend_verifies_token` skipped: "No backend detected" | The app never sent the launch token to a server of its own | Nothing to fix for a static app. If your server acts on who the user is, send it the launch token and verify it there | Still stuck? Ask in the [Cherry developer group](https://t.me/cherrydotfun).