iPhone 1.1.6
Frewli iPhone 1.1.6 no longer contacts a backend or offers account sync. The earlier This device / Other device cloud-conflict workflow is not a current sync task. Keep the existing installation and check local saving before changing or erasing records.
1. Identify the version and the screen
The original guide at this URL described earlier cloud-capable source: Drink history, Sync conflict and whole-record choices between two versions. That is historical context, not a promise that those controls exist in the current iPhone release.
Current release information states that Frewli works entirely on the device, with no account, email sign-in or backend sync. See accounts after the offline update for the changed scope.
2. Keep the history already on the device
The offline update preserves existing on-device history. It does not prove that all records from an earlier cloud account were downloaded, and it does not delete previously uploaded server records.
If a record appears missing or inconsistent, keep the installation available and contact support with the version and the issue. Creating another drink or reinstalling is not a test of what happened to an earlier cloud version.
3. Check local saving without another entry
Read any saving or failure message on Today. A failed write needs its retry action and a later check; a changed visible total alone does not prove a successful stored write.
The current app’s You > On-device storage screen explains its storage model. It is not a cloud-merge screen and does not provide the earlier Keep this device or Use other device choice.
4. Treat older conflict choices as historical
In the earlier workflow, those buttons chose one complete version of one record; they did not add two volumes or merge individual fields. A displayed deleted version could keep a deletion. The page’s original publication date records that earlier guide, while this update explains the current version boundary.
Do not use that historical description as a guaranteed way to restore a deleted entry. For an older installation still showing a conflict, keep both visible details available and ask support before making an uncertain choice.
5. Separate local erase from historical cloud requests
The current local erasure workflow is permanent after confirmation. It is not a sync-conflict resolver or a replacement for checking a failed save. Apple Health and historical server records are outside its erasure scope.
Requests about previously uploaded records use the historical account-data support route. Upgrading or erasing this device does not by itself remove those records.
6. Keep optional Apple services separate
Apple Health and your paired Watch remain optional device integrations. They do not create a new Frewli backend account. Check the relevant Health or Watch connection rather than looking for the retired cloud-sync control.
Share only the version, screen and exact error needed for support. Keep sign-in codes and private records out of public screenshots.
Try it with Frewli
Keep your record on your device.
Track water, review your routine and use optional Apple Health, paired Apple Watch and local reminders. Every feature is free.
Download free for iPhonePrepared with AI assistance using Frewli’s release information and on-device controls, checked November 9, 2026. Earlier-release behavior is labelled separately. Contact Frewli support.