Skip to main content

Crashes on Apple Watch

Currently, some users experience crashes on their Apple Watch after logging in to Structured Cloud sync. This is caused by an external service, and they are currently working on addressing the issue.

We appreciate your patience and apologize for the inconvenience.

Status: Completed6 comments

Log in to comment and vote

Comments6

  • Linnea

    Team•

    Dec 28, 2025

    Pinned

    Quick update:
    The external provider identified the issue and will publish an update in the upcoming days.

    We appreciate your patience. 😊

  • momanatorz

    •

    Jan 5

    My main app on iPhone is now freezing since the Watch update? The watch app crashes less often but still happens.

    I just got a new iPhone as well and the issue remains. Any known issue with text sizing or any other Glass customisation settings?

    The app freezes when scrolling and takes a few minutes to restart itself.

    • Linnea

      Team•

      Jan 6

      Hi 😊
      Sorry to hear about that. Did you check out this Help Center article already? For further assistance, please get in touch with: support@structured.app.

      • momanatorz

        •

        Jan 25

        Bringing this back up because it support is even too busy or I’m being ignored. There must be an issue with my account if no one else is getting this issue.

  • Nick Brown

    •

    Dec 17, 2025

    I’m someone suffering this currently. With iCloud Sync enabled, the sync never completes on iPhone. With Structured Cloud sync enabled, the sync completes rapidly on iPhone, but on WatchOS the app constantly closes. Every time I open it, it closes again. Please fix this asap it’s making the watch app entirely usable atm, and I consider it a critical bug.

    • Linnea

      Team•

      Dec 17, 2025

      Hi Nick 😊
      Thank you for sharing your experience. We again apologize for the inconvenience. Unfortunately, an external provider causes this issue. We’re in close contact with their development team and hope to get this fixed asap, so we can include it in our upcoming update this week.