You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous versions of Actual, it was possible on mobile to view the server/sync status button ("sync" or "server offline" depending on connection status) if the screen was wide enough. For example, one could rotate their phone to landscape orientation and the desktop UI would become available, including the server/sync status button.
Since at least Actual 25.1.0, this is no longer possible. As a result, users cannot determine if their budget is being successfully synced on mobile at all.
An indicator should be incorporated into the mobile UI rather than restoring the old workaround behavior.
How can we reproduce the issue?
Open Actual on Mobile Safari
Optional: make changes to data
Optional: pull to refresh
Attempt to determine sync status
Where are you hosting Actual?
Locally via Yarn
What browsers are you seeing the problem on?
Safari
Operating System
Mobile Device
The text was updated successfully, but these errors were encountered:
Verified issue does not already exist?
What happened?
In previous versions of Actual, it was possible on mobile to view the server/sync status button ("sync" or "server offline" depending on connection status) if the screen was wide enough. For example, one could rotate their phone to landscape orientation and the desktop UI would become available, including the server/sync status button.
Since at least Actual 25.1.0, this is no longer possible. As a result, users cannot determine if their budget is being successfully synced on mobile at all.
An indicator should be incorporated into the mobile UI rather than restoring the old workaround behavior.
How can we reproduce the issue?
Where are you hosting Actual?
Locally via Yarn
What browsers are you seeing the problem on?
Safari
Operating System
Mobile Device
The text was updated successfully, but these errors were encountered: