SQLite does not block `BEGIN IMMEDIATE TRANSACTION` from multiple JS contexts
See original GitHub issueSummary
SQLite does not block BEGIN IMMEDIATE TRANSACTION
from multiple JS contexts. This causes an attempt to start a transaction inside a transaction when using the same (even different) WebSQL.Database instances.
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
iOS and Android
SDK Version (managed workflow only)
40 and 42
Environment
Expo CLI 4.7.3 environment info: System: OS: Windows 10 10.0.19043 Binaries: Node: 12.18.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE Yarn: 1.22.10 - ~\scoop\apps\nvm\current\nodejs\nodejs\yarn.CMD npm: 6.14.4 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD IDEs: Android Studio: Version 4.2.0.0 AI-202.7660.26.42.7486908 npmPackages: expo: ^40.0.0 => 40.0.1 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz => 0.63.2 react-native-web: ^0.16.3 => 0.16.3 Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top GitHub Comments
I think this is more of a problem on Expo Go when it reloads it may not close the WebSQL (since it does not expose the close()) method so we can’t do a useEffect return to close.
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.