Râu Cao
Râu Cao
> Perhaps it would be best to merge the PR which contains all of the config and setup (with both test runners executed as part of unit tests) then we...
> I'd propose to disable IndexedDB usage for the affected versions until Apple has fixed the underlying issue. +1
It falls back to localStorage. However, this change would prevent people from accessing unsynced data, so I think it needs a major version change, as well as proper announcement/explanation for...
Not sure I know what you mean by "suspended state"? The iOS bugs are not in the library, or detectable by the library, unfortunately. Apple just failed their users spectacularly...
The way I understand this, the underlying issue is that the bug happens when iOS stops your app in the background. And on iOS there is simply no way to...
I didn't say the app is terminated. I said it is being stopped. But in any case, you cannot reload something in the background on iOS, and you cannot reload...
@galfert Perhaps you could explain why you proposed not using IndexedDB over e.g. `location.reload()` triggered e.g. by a visibility event?
How did this go, btw? Would be interested in solving this for other apps as well.
Still cool. Could you link to the code perhaps?
Before investigating this, just a note: This could be an edge case with the default caching strategy (caching is enabled with the `SEEN` strategy by default) and node.js usage, which...