Skip to content

Book sync still having issue #53

Description

@EZas123

I saw the update for the book sync issues and tried to sync new books today. It started great then the app requested to connect to flowe hotspot even though both x3 and iphon are on same WiFi network and it failed to sync.

  • Also noticed the calendar is showing "tomorrow" and not the current days events after the update.

Activity

  1. andrewjiang commented on Sep 16, 2026

    @andrewjiang
    Owner

    0.7.3 contains changes aimed at the Wi-Fi failure reported here. The iPhone now keeps looking for the reader while its Wi-Fi server starts. Cancel and cleanup after a network change have also been repaired. Being on the same Wi-Fi network does not by itself confirm that the app has reached the reader; failed contact can trigger the hotspot fallback.

    Home Wi-Fi transfers passed bench testing, but we have not reproduced your exact failure. The final Cancel change still needs a device check.

    Update order: install firmware 0.7.3 RC1 first, then update the iPhone app to 0.7.3 (234) when TestFlight offers it. Build 234 has been assigned to the external tester group and is waiting for Apple’s beta review; it is not yet available to external testers.

    Please retry on home Wi-Fi after both updates are installed. If it fails, use Settings → Help → Send diagnostics and include the app build, reader version, and whether the hotspot prompt appeared before or during the book transfer.

    The separate Tomorrow instead of today calendar report is still open. The sync changes do not establish that it is fixed.

  2. EZas123 commented on Sep 16, 2026

    @EZas123
    Author

    Sent iPhone diagnostic through test flight. Still failing

  3. andrewjiang commented on Sep 16, 2026

    @andrewjiang
    Owner

    Thanks for sending the TestFlight diagnostics. Keeping this open; your report says sync still fails.

    Please confirm the iPhone app version/build, the reader version in Settings → About, and roughly when you submitted the feedback so we can match it to the report. iPhone 0.7.3 (234) and firmware 0.7.3 are now available. If your reader already has RC1, it has the same firmware. Flowe 0.7.3 has the links.

    The calendar showing Tomorrow instead of today also remains unresolved.

  4. andrewjiang commented on Sep 16, 2026

    @andrewjiang
    Owner

    Hey @EZas123 can you try again on the latest release?

    (and sorry for the long automated response above -- appreciate you sharing the issue!)

  5. andrewjiang commented on Sep 16, 2026

    @andrewjiang
    Owner

    I found the two TestFlight reports from today and read the attached diagnostic screenshot. Both reports are from 0.7.3 (234), so you do not need to confirm the app build again.

    The screenshot shows two attempts that enter Connecting after six seconds and fail about 77 seconds later. The error and missing hotspot prompt match a code path where the phone has not received the reader’s hotspot details before sync starts.

    I have a local fix that requests those details while Bluetooth is still available, retries a missed reply, and avoids starting a Wi-Fi session with no fallback details. The regression test passes. This is not yet in TestFlight, and the screenshot alone does not prove it explains every part of your failure.

    Please still share the reader version from Settings → About. If possible, attach the exported flowe-diagnostic.txt itself rather than a screenshot; the screenshot shows only the short summary. This issue remains open.

  6. andrewjiang commented on Sep 18, 2026

    @andrewjiang
    Owner

    Firmware 0.7.4 and iPhone 0.7.4 (238) are out. Links and order are at https://www.flowe.ink/releases/0.7#try. The iPhone build is with internal testers now and reaches the public group after Apple's review.

    To be clear about what it does and does not do: the fix for the phone starting a sync without the reader's hotspot details, which your diagnostic pointed at, is not in this release yet. What 0.7.4 stops is the repeat: after one failed sync the app used to start another on every reconnect, so the reader kept asking for the hotspot. That loop is gone.

    When you have 0.7.4 on both, could you try one sync and send a diagnostic from Settings, Help? That tells me whether the first attempt still misses the hotspot details.

    I have not forgotten the calendar showing tomorrow's events. That is a separate bug and I will report back on it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions