Help with Risoni on iPhone

Quick recovery

My recipes look missing

Check the selected kitchen and clear any search or filter. Local kitchen and shared kitchens are separate. If recipes are still missing, stop and report the problem before restoring a backup, reinstalling or deleting anything.

An import is incomplete or rejected

Compare the preview with the original: ingredients or steps may already be missing from the source. Review warnings before saving. For an HTML encoding error, save a UTF-8 copy from the original app and retry. For an oversized image, choose a smaller copy. Keep the original file.

Paste link cannot read a page

Check that the address is HTTPS and from a supported publisher. For another site or a signed-in page, try the available Safari capture action and review the result. Pasting text you can access is another option. Risoni does not bypass subscriptions or retrieve a social video.

A shopping amount looks wrong

Open the item's From… source or Edit item → Recipe sources. Compare the original ingredient with the planned servings. Correct the shopping amount or omit the item; the recipe stays unchanged.

Reminders shows nothing new

Check the selected writable list and the added/already-present message. Risoni may skip an existing item. If Reminders access is unavailable, continue using Risoni's Shopping list and report the message. Purchased checks do not synchronize between the two apps.

A timer is overdue or did not alert me

Reopen cooking to check its saved deadline. Audible alerts while the iPhone is locked, or Risoni is closed or in the background, are not verified. Use a separate system or kitchen timer when you need a reliable alert.

Beta limits

• Availability: iPhone 0.1 (6) is Testing for the existing private group. Check TestFlight for the update; individual notification receipt and installation are not confirmed. New invitations require approval. See the release notes.
• Sharing: live updates between two Apple Accounts are unverified. Wait for the coordinator to confirm sharing is enabled, then test with disposable data.
• Imports and backups: keep original exports. Paprika 4 cookbook organization and full backup/restore checks are not established. A kitchen backup includes recipes, photos and import history, but excludes plans, shopping, cooking sessions and sharing access. Restore is limited to the same kitchen.
• Apple integrations: Siri and App Intents entry points are disabled in beta 0.1 (6). Real Reminders delivery, signed-in subscriber Safari capture, widgets and Live Activities remain unverified. Follow the visible controls described in this guide.
• Accessibility: some large-text paths have been tried, but complete VoiceOver, Voice Control, keyboard and contrast support is not yet established. Report the specific control you cannot reach or read.
• Device coverage: the screenshots do not establish support for every iPhone or iOS version. Your invitation will name supported devices.

Report a problem

Use the private contact supplied with your approved invitation. If you installed Risoni through TestFlight, you can also use the feedback steps below. Do not post private recipes or account details to this public help site.

Feedback for a TestFlight installation

1. Open TestFlight and select Risoni.
2. Tap Send Beta Feedback and choose whether to include a screenshot. Review it for private content first.
3. Describe the problem and submit. If TestFlight offers a crash-report prompt after a crash, add what you were doing there.

Screenshot and crash-feedback options depend on the tester group's settings, and the final release's feedback route still needs checking. If an option is unavailable, use the private contact from your invitation. Apple also receives feedback sent through TestFlight. These steps apply only to TestFlight installations.

What to include

1. Your setup: iPhone model, iOS version and Risoni version/build. TestFlight lists the installed beta version. If you cannot find it, say so.
2. What you tried: two or three numbered actions and whether you used Local kitchen or a test shared kitchen.
3. Expected and actual result: what you thought would happen and what you saw. Include the exact error wording.
4. Repeatability: whether it happened once or every time, and whether reopening changed it.
5. Optional screenshot: hide names, account addresses and personal recipe content. A made-up example is best.

For example: “iPhone. In Local kitchen, I planned Test Soup for Friday, opened Shopping and changed Amount to 2. Save item stayed dim. Reopening did not help.”

Never include passwords, verification codes, invitation links or your recipe database. If you suspect lost or changed data, stop editing the item, preserve the original export and report it. Repeated restores or reinstalling are not a first step.