Replies: 2 comments 1 reply
-
Looks like we forgot to port the dangerousUseHttpScheme setting after all. I guess that's mostly my fault... Would you mind opening a normal GitHub issue for this instead so the team can hopefully quickly follow up (I am out of office right now)? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Sure, will do.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone!
After upgrading to tauri 2 (referred to as new app below), I found that I'd "lost" all my app data, which was stored in IndexedDB. After some digging, it turns out that the IndexedDB path changed from
https_tauri.localhost_0.indexeddb.leveldb
tohttp_tauri.localhost_0.indexeddb.leveldb
. The oldhttps_tauri.localhost_0.indexeddb.leveldb
is still there, and the app before upgrading to tauri 2 (referred to as old app below) can see the data.To maintain backward compatibility, I need the new app to read/write dir
https_tauri.localhost_0.indexeddb.leveldb
. The question is, how? Another question is, renaminghttps_tauri.localhost_0.indexeddb.leveldb
(accessed by the old app) tohttp_tauri.localhost_0.indexeddb.leveldb
(accessed by the new app) doesn't make the new app see the data.This is Windows 11, the full paths of mentioned dirs are:
C:\Users\[username]\AppData\Local\com.example.app\EBWebView\Default\IndexedDB\http_tauri.localhost_0.indexeddb.leveldb
C:\Users\[username]\AppData\Local\com.example.app\EBWebView\Default\IndexedDB\https_tauri.localhost_0.indexeddb.leveldb
Beta Was this translation helpful? Give feedback.
All reactions