Forkin Cooking
Forkin CookingFood works better when you understand it.
Install help · Android

Seeing ‘Unsafe app blocked’ when installing Forkin Cooking?

Short version: it’s a Chrome/Google quirk with progressive web apps, not a real security problem with our site. Here are two ways to get past it in under a minute.

What’s actually happening

Forkin Cooking is a website, not a normal Android app. When you tap “Install app”, Chrome quietly asks Google to build a little wrapper (called a WebAPK) from our web manifest and install that on your phone. Google’s Play Protect has started flagging some of those older wrappers as “built for an older version of Android” — even when the website itself is up to date. We can’t change how Google builds the wrapper. What you’re seeing is that warning, not a problem with the website.

Fix 1 · fastest (10 seconds)

Tap ‘More details’ → ‘Install anyway’

  1. On the “Unsafe app blocked” pop-up, tap More details.
  2. Scroll down. Tap Install anyway.
  3. Done — the app icon lands on your home screen as usual.

You’re not overriding a real security check on the website — you’re telling Play Protect you trust this specific install.

Fix 2 · if you’d rather not bypass Play Protect

Use ‘Add to Home Screen’ instead

  1. Open forkincooking.com in Chrome (not Facebook, not Instagram — full Chrome).
  2. Tap the ⋮ menu (top right).
  3. Tap Add to Home Screen — not “Install app”.
  4. Confirm. You’ll get a home-screen icon that opens the site full-screen, no wrapper, no Play Protect check.

Same site, same saved recipes, same login. Just skips the WebAPK step entirely.

Send this to someone

Copy-and-paste message

If a friend’s hitting the same warning, send them this. It links back to this page.

That "Unsafe app blocked" warning is a Chrome quirk, not a real security issue — Forkin Cooking is a website, not a normal app from the Play Store. Two options:

1. Tap "More details" then "Install anyway" on the block screen, or
2. Open forkincooking.com in Chrome, tap the ⋮ menu, and choose "Add to Home Screen".

Full explanation: https://forkincooking.com/install-help
Why we can’t just fix it on our end

Google’s servers build the WebAPK wrapper, not ours. We don’t control which Android target SDK it uses or when it gets rebuilt. We’ve cleaned up our web manifest so future installs give Google the best possible signal, but there’s no button on our side that forces Play Protect to un-flag an existing install. The two fixes above are genuinely the shortest working paths.

← Back to Forkin Cooking