-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Base: Failed to import "android" module. Could not remove android presplash. #1153
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
Comments
This is just a notification, it shouldn't actually cause anything to fail. The actual reason for the warning is that Kivy actually does |
The reason for concern is that our android service is now not starting. I thought this might be the reason, but let me eliminate the possible of the service breaking for other reasons... |
From https://python-for-android.readthedocs.io/en/latest/services/ Is there a way to add --service=myservice:/path/to/myservice.py argument to p4a via the buildozer.spec, or do we need to user the Service folder method? |
@the buildozer log is showing the following:
I see somewhere that that has been renamed to PythonService? This is building with the android_old. |
I think the I don't know what's up with your intent error. Is this just what happens when you run |
Yes, that's the command which produces this. I'll do some more digging and come back.... |
We are using SDL, but I can't seem to get the service working. As well as the conventional:
we also tried service creation as below. It does not throw an error in the app but still does not run:
Also, adding the below to the buildozer.spec file,
we still get the 'class not found error'
throws
How to get this working? This is getting quite critical for us as it's been over 2 weeks since we could put out a working build. Using the new toolchain is not an option as we get the libpythonxxx SDLError both our testing tablets. How to go forward? |
Did you have a working build before that and something broke? Or that is just when you started trying to use this functionality?
Is there definitely nothing in the log here? Would you be able to post it? Given how the android module is structured, I would have expected at least some kind of notification about what's going on.
This method will definitely only work with the sdl2 bootstrap, so that's at least an okay error. |
Trying
Now produces the following log and the error trap above is never reached:
Search for 'androidservice.py' to find the point where it tries to call the above code.
Now the error is different. Is "No JNI_OnLoad found" indicative of something? |
I am happy to report we found the issue. The service dies the moment it calls this code, but it works in the app
Not sure why as there is not message I could detect, but moving this outside the service makes it work again. Yay @inclement. Thanks |
This message to me looks like a regression even though it doesn't crash. I remember adding |
This occurs after removing the .buildozer folder, and using the latest master checkouts of buildozer and python-for-android. This occurs when trying to use the 'android_old' target (the 'android' gives us this error: #1142)
python-for-android: commit 2136e0f
buildozer: commit 3a93783aa8cbfb0605e4b46f977f8c9951c1a043
This means our python service does not start and our background downloads to not start.
This happens even if we add android to the requirements. From the buildozer.spec file.
I can see where this error is throw (kivy.base) but the only files containing that text in the .buildozer folder are pyc and pyo files.
Any ideas' on how to solve this? Or where one makes changes to alter this?
The text was updated successfully, but these errors were encountered: