actualbudget / actualbudget/actual
[Bug]: iOS/Safari client loses connection to server and it cannot be restored without removing all the local website data
- Langage dominant
- TypeScript
- Étoiles
- 28.7k
- Forks
- 3k
- Merge moyen
- 2 j 11 h
- PR mergées (30 j)
- 65
Description
### What happened?
I have Actual instance open in a Safari tab, and sometimes I work with it offline (*no internet connection*). When I get back online, usually the data syncs just fine, which is super convenient (*basically, eliminates a need to have a proper application for it*). However, sometimes the client (*that Safari*) "loses" the server, so it looks like this in settings (*`N/A` for server version*):
Trying to reload the page (*when I am online*) or/and restarting Safari does not resolve this, server is still offline and `N/A`. Trying to re-enter the same URL by clicking on `Change server URL` menu item fails with this error:
```
Server is not running at this URL
```
here's also a screenshot:
But server is most definitely running at this URL, because it was working before and it is still working in other browsers on my other devices at this exact same URL.
Only when I go to iOS settings and remove all website data for this host in Safari (*and restart Safari*), then I get the client working and connected to the server again (*with absolutely the same URL that was failing earlier on that screenshot above*).
Not sure if this is specific to iOS/Safari, but so far I noticed this problem only happening there.
It is also probably worth to mention that I use a self-signed certificate on the server, so I need to trust it on the initial page load in Safari. But then again, if that was a problem for the Actual frontend, it would have failed to connect to that server already on the initial load.
The Actual version is `v26.2.0`.
### How can we reproduce the issue?
1. Open Actual instance in Safari on iOS;
2. Disconnect from the internet;
3. Make some changes;
- or maybe just stay offline for some (*unknown period of*) time;
5. Get back online;
6. The server will be offline and server version will be `N/A`.
Unfortunately, these steps do not always reproduce the problem, I noticed it happening only once in a week or so.
### Where are you hosting Actual?
Docker
### What browsers are you seeing the problem on?
Safari
### Operating System
Mobile Device
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.