• I’ve got an idea, how can I share it with the CookBook team?

  Quick answer: Head to our Ideas & Suggestions page to submit your idea or vote on existing requests. We review the board regularly and use your votes to shape our roadmap. Where to share your ideas Public roadmap – Peek at what we’re working on right now and what’s coming next. Ideas & Suggestions page – Browse, up-vote, or post a brand-new idea. Updates (https://roadmap.coFew readers

• My recipe didn’t import (or some data is missing)

  Quick answer: CookBook’s importer now combines AI vision + structured-data parsing, so it can read most recipe websites, even when they skip industry-standard markup. If parts of the recipe are still missing, the page may be image-only or locked behind paywalls/scripts our AI can’t reach. You can always copy-paste the text or scan a screenshot. Why imports sometimes fail - even with AI Text locked inside images When all the ingredients and instructions are baked into a JPFew readers

• Enable Service Workers for CookBook

  Fix the “Unsupported browser” error (enable Service Workers) If Chrome or Firefox shows: “Unsupported: This browser does not appear to be supported. Please ensure you have a modern browser … and have Service Workers enabled.” do the following: Chrome Type chrome://flags/enable-service-worker in the address bar. Enable Service Worker. Relaunch Chrome and sign in again at app.cookbookmanager.com. Firefox Type about:config in the address bar andFew readers

• Android: “Whoops, a licence error occurred”

  Quick answer: Google Play’s Integrity check couldn’t confirm that your copy of CookBook is untampered and installed on a Play-Protect-certified device. Follow the checklist below. Why this message appears CookBook relies on Google Play’s built-in Integrity Protection before it connects to our servers. The check confirms: The app was downloaded from Google Play. Its code hasn’t been modified or tampered with. The device passes Google’s core security tests (i.e. is not aFew readers

• Why doesn’t CookBook open on iOS 15 anymore?

  Quick answer: The latest CookBook update needs iOS 16.4 or later. Key components we rely on no longer work on iOS 15, and there’s no way to keep an older build running. If your iPhone or iPad can update to iOS 16 or newer, install the update and CookBook will open normally. If your device can’t move past iOS 15, you can still access everything at app.cookbookmanager.com Why we can’t support iOS 15 any longer Essential libraries that power CookBook have dropped iOS 15 compaFew readers

• Can’t login to CookBook? Troubleshooting steps

  Quick answer: Use the same method you used when you first created your account.• If you originally entered an email + password, tap Log in with email.• If you originally chose Continue with Apple or Continue with Google, tap that same button.Once you’re back in, you can link additional sign-in options under Manage & update account. 1. Confirm how you first signed up Before July 2025 you could only create an account with email + password. After July 2025Few readers

• App won't open on iPhone running iOS 26

  Some users are experiencing an issue when upgrading their iPhone to iOS 26. To resolve this issue: Delete the CookBook app Turn your device off Turn your device back on Reinstall CookBook directly from the App Store Don't worry, your recipes are stored safely on our CookBook cloud, so will be there for you when you log back in again. If you're still experiencing issues, please reach out to us team@cookbookmanagFew readers

• How do I contact the CookBook team?

  Quick answer: Tap Submit a request on this page (or email team@cookbookmanager.com) and send us your question, idea, or bug report - big or small. We read every message and will reply as soon as we can. 💌 We’d love to hear from you! Whether you’ve run into a hiccup, have a brilliant feature idea, or just want to tell us how CookBook fits into your kitchen routine, drop us a note. Your feedback shapes our roadmap and helps us squash pesky bugs faster. What to includeFew readers

• I found a bug or problem, how do I report it?

  Quick answer: Tap Submit a request on this page, describe the issue in detail, and attach any screenshots or videos. The more information you give us, the faster we can squash the pesky bug! What to include in your report 1. Device details Make & model (e.g. iPhone 16, Samsung Galaxy S25). OS version (e.g. iOS 26, Android 15, macOS 15, browser version for Web App). 2. Clear description of the problem What you expected to happen vs. what actually happened.Few readers

• My cooking timers aren’t going off

  Quick answer: If a timer finishes and you don’t hear or see anything, walk through the checklist below. In nearly every case the phone is silenced, Do Not Disturb is active, or the alert is being captured by another device (Apple Watch, Mac, etc.). Timer-notification checklist Volume Make sure the Ringer/Media volume is above zero. Timers use the ringer channel on iOS and the media channel on most Android devices. Silent / Ring switch (iPhone) Flip the side sFew readers

• How do I turn haptic feedback off?

  Quick answer: Haptics (those tiny “buzzes” when you tick off ingredients or shopping-list items) follow your phone’s system settings. Turn off system haptics in your iPhone or Android settings and CookBook will stay silent, too. Apple iPhone or iPad Open Settings → Sounds & Haptics. Scroll down and switch System Haptics to Off. Once disabled, you won’t feel vibrations for CookBook actions, or any other system taps until you turn the toggle back on. AndFew readers

• Does CookBook work with Alexa or Google Home Hub?

  Quick answer: Not yet. CookBook doesn’t currently integrate with Amazon Alexa or Google Home Hub, but it is on our future roadmap. What you can do today Built-in voice guidance: The CookBook mobile apps already read recipe steps aloud. Screen wake-lock: Your device screen stays on while you cook, so you don’t have to keep unlocking it.Few readers