-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nothing happen when call to executeSql #43
Comments
Please provide me enough information to reproduce it. |
Try change the name of database within ".db". { |
not work for me |
Did anyone ever figure this bug out? I'm hitting this exact same problem and it's super annoying. Works perfectly every single time on Android simulator, but never once works or fires either the success callback or the error callback on my physical android device. @B-Evans99 that issue is not the same. My db is configured and opened properly as the solution already described in the problem. Physical Android Device: Expo Client version = 2.28.8 (supports SDK 46, 47, 48 and I'm using 48 for development) Package.json
DbContext.js
As I said before, if I could share a reprocudable snack of this I would, but I have never been able to reproduce the issue on an android simulator, it always works perfectly. It is only specifically when dealing with a physical android device that none of the executesql callbacks get called at all, or db.transaction for that matter as far as I know. I've never seen logs for those either. I've tried making a Should I be using a different npm package for my sqlite queries? I just figured expo-sqlite would be the best option since I am using expo, but apparently it does not work on a physical device. Any help is appreciated, thanks! P.S. |
Sometime in Android device, txn.executeSql not return anything, ( even error or success functions are not triggering ) . this is my code.
The text was updated successfully, but these errors were encountered: