-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
sqlite3 not working with android_new #1053
Comments
I am already using Please let me know any other details are required for the resolution. |
And you need to replace it with Your requirements should be: |
That doesn't work either. By using python2, I was succesfuly able to create apk. However, I got runtime error while importing sqlite3. For this specific issue, I created a small app for testing sqlite3 - https://pastebin.com/spZqk6pb as per app, it will only import sqlite3 when we click on button. On clicking we get following traceback output after using
It works on Ubuntu when i run "python2 main.py" |
Could you post your buildozer.spec file? Or at least relevant parts of it? |
buildozer.spec - https://pastebin.com/UqvcKhuJ *updated with correct link |
Try actively whitelisting files required for sqlite3 in your buildozer.spec, like so: That, along with adding sqlite3 to the requirements and running |
I am successfully able to import sqlite3 after performing the above 2 steps. Thanks it works now. |
sqlite3 is currently working well in the master branch. |
@ngala commented on Fri Jan 13 2017
Before raising the issue, I have tried to refer any old issues with similar problems. Making attempts to work out solutions.
The Kivy App is running fine on the setup(Ubuntu 15.04 VM). The app was basic and did not have any other python libraries. I could successfully create an APK file and the App worked same on Android(Nexus 5x, Nougat 7.1.1) as it did on Ubuntu.
Now when I tried to import sqlite3, it worked fine on Ubuntu but it crashed on the phone. I was getting
no module named sqlite3
in my logcat.On some digging, I referred to kivy/kivy#705
I removed the blacklisted files referring to sqlite3(including both sqlite3/* and lib-dynload/_sqlite3.so) from blacklist.txt and also installed libsqlite3-dev package. The error changed slightly...
no module named _sqlite3
Apparently solution in that issue was partially applicable to new toolchain.
I went a step further and deleted .buildozer folder completely so that it would download and install packages in case they are broken.
but that did not resolve the issue...now it is getting compiler error
here's the complete file for buildozer debug output (http://pastebin.com/ANuYTu8R) and config.log(http://pastebin.com/maWgbBpw)
The apps created without sqlite3 are still working fine on both Ubuntu and Android.
@ngala commented on Tue Feb 28 2017
Hi...any update in this?
@tito commented on Mon May 15 2017
I think that's an issue with python-for-android directly. The recipe build order put sqlite3 after compiling Python, but it should been done before. I'm moving it.
The text was updated successfully, but these errors were encountered: