Closed NavaceSystem closed 1 week ago
I think this is fixed in Replicache 15. We started releasing this and didn't complete it. I can't remember why. Can you take a look?
@NavaceSystem This does seem to work in react native on Replicache 15, but Replicache seems to continue to try and sync once the DB is destroyed. Calling replicache.close() before destroying the DB results in breaking destroyAllDatabases, so I think we're kind of stuck until this one gets figured out
@1kDustin do you have a reproduction or test case that shows what you're seeing? Thanks!
Oops, this was fixed.
We are trying to use replicache in react-native using the experimentalCreateKVStore with https://github.com/Braden1996/react-native-replicache binding. Everything works fine except for the the
dropAllDatabases
anddropDatabase
calls. It seems to be ignoring the binding and doing its default "web" stuff. I've traced the minified Replicache code to debug this and below are 2 errors that made me reach this conclusion:dropAllDatabases
, it errors out on this line in replicachereturn navigator.userAgent.includes("Firefox")
. It obviously has some FF specific logic but this code shouldn't be running at all. When theexperimentalKVStore
is present it should be calling itsdestroy
function.indexedDB.deleteDatabase(t)
. Again IDB is a web specific thing, it shouldn't be running this code at all.