Current App Version (iOS)
Articles in this section
🚀 Getting Started
📥 Importing Recipes
- How to Import Recipes
- Import from a Website
- Import from Instagram
- Import from TikTok
- Import from Pinterest
- Import from YouTube
- Scan a Recipe from Photo
- Dictate a Recipe by Voice
- Import by Pasting Text
- Use the In-App Browser
- Write a Recipe from Scratch
- Review & Edit Before Saving
- Understanding Import Credits
📂 Managing Recipes
👨🍳 Cooking Mode
📅 Meal Planning
🛒 Grocery List
📤 Sharing & Export
💳 Billing & Subscription
⚙️ Account & Settings
ℹ️ About Cookonut
💡 Ideas & Feedback
Here’s how to check which version of Cookonut you’re running on your iPhone or iPad, and how to make sure you’re always up to date.
Check Your Current Version
- Open Cookonut
- Go to the More tab
- Tap About
- Your version number is shown at the top (e.g., “Version 1.2.3”)
Update Cookonut via the App Store
To manually check for updates:
- Open the App Store
- Tap your profile icon in the top right corner
- Scroll down to the list of available updates
- If Cookonut has an update, tap Update
If you don’t see Cookonut in the list, you’re already running the latest version.
View Release Notes
To see what changed in the latest version:
- Open the App Store
- Search for Cookonut or find it in your update list
- Scroll down to the What’s New section
Release notes describe new features, bug fixes, and improvements included in each version.
Enable Auto-Updates
The easiest way to stay current is to let your iPhone or iPad update apps automatically:
- Open the Settings app (the system Settings, not Cookonut)
- Tap App Store
- Under Automatic Downloads, turn on App Updates
With auto-updates on, new versions of Cookonut are downloaded and installed in the background — typically when your device is connected to Wi-Fi and charging.
Why Updating Matters
Each update may include:
- New features and improvements
- Bug fixes for issues reported by users
- Performance and stability enhancements
- Security updates
If you’re experiencing an issue with Cookonut, checking for an update is a good first step — the problem may already be fixed in a newer version.
Thanks for your feedback! We're glad it helped.