12 ms·
Webkit's website says: "[..] deleting all of a website’s script-writable storage after seven days of Safari use without user interaction on the site." It is no
by yohannparis 7y ago
Webkit's website says:
"[..] deleting all of a website’s script-writable storage after seven days of Safari use without user interaction on the site."
It is not clear that a user coming to your website before the 7 days, even offline, is exempt of it.
- bg0 7y agoYea, we actually don't use safari at all in our app. So this might not have an effect but it's pretty vague.
- lonelappde 7y agoIf you don't use Safari you can patch webkit to change the policy, right? Change 7 to 10000000
- tssva 7y agoApple only allows apps to use their webkit implementation.
- tomnipotent 7y agoEven for other browsers. Chrome, Edge, Opera etc. on iOS all use webkit under the hood.
- chrisfinazzo 7y agoYou could...but it's a change that the Webkit project would never accept and you would be forever diddling this value every time an update came along. Sisyphus says 'Hi!'
- vbezhenar 7y agoUser not coming to website 7 days can't be invalid use-case. Losing important data simply because someone went on vacation is unacceptable.
- im3w1l 7y agoSo store this data on the server.
- tssva 7y agoThe original comment referenced an app where the users are offline for weeks at a time. Storing data on a server is not really possible in this use case.
- matsemann 7y agoBut wouldn't that make it have less privacy? Now my webapp cannot be used offline and anonymously, user has to be logged in and tracked
- im3w1l 7y agoIt doesn't change the status quo. Important data wasn't put in cookies before, and it wont be after. It was always a recipe for data loss. Server side, or if you need privacy, have the user export to / import from a local file.
- felixfbecker 7y agoThis is also about IndexedDB. Imagine native apps had all their data wiped if you don't open them (with an active internet connection) every 7 days. Not just on an iPhone, but also on macOS.
- Grimm1 7y agoThis impacts an app I've built for reading academic papers but I imagine the work around here is to write to a file periodically and then load the file in if you don't detect indexedDB having the data you think it should. Obviously this has error cases all its own and makes it more difficult to manage but it doesn't seem like Apple is killing it to me, just making us jump through hoops and add extra complexity. Don't mistake me though this seems like an anti-competitive move from them to prevent people from circumventing the app store.