Cant start service app
See original GitHub issueFrom @Fogapod on April 28, 2017 17:1
Versions
- Python: 2.7
- OS: android
- Kivy: master
Description
Service app raises android error right after starting. No exceptions, no kivy logs. Just do not start. Faced this problem only on android building with buildozer’s android_new
toolchain
Code
I get code from here: https://github.com/tshirtman/kivy_service_osc
(changed line 7 and 8 to from kivy import platform
)
Logs
Part of logcat where app fails to start service
Edit: removed apk.
Copied from original issue: kivy/kivy#5140
Issue Analytics
- State:
- Created 6 years ago
- Comments:26 (14 by maintainers)
Top Results From Across the Web
networking - Docker error: Cannot start service - Stack Overflow
I'm assuming you're using docker-compose and seeing this error. I'd recommend docker-compose up --force-recreate <name>.
Read more >Docker compose can not start. Service network not found after ...
The problem is when I restart the docker service. ... ARG ENTRY ENV my_env=$ENTRY WORKDIR C:\\foo2 ENTRYPOINT C:/foo2/app.exe %my_env%.
Read more >Resolve Docker Compose ERROR: Cannot start service app
A guide to resolve Docker Compose ERROR: Cannot start service app: OCI runtime create failed.
Read more >How to fix Docker error: 'Cannot start service .. network ...
First, check docker-compose. yml file for any network dependencies. Here in the example above you can see that we have an external network...
Read more >Deployment Errors - Appsmith
If you are trying to connect to an existing MongoDB and the containers failed to start it may be due to one of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems like the bug was introduced in https://github.com/kivy/python-for-android/pull/609 Basically the
pythonName
is not initialised within PythonActivity.java start_service(). To fix it we could either initialise it here, or check in start.c Java_org_kivy_android_PythonService_nativeStart() ifpython_name
is null and assign it a default value. I vote for the first option which is to assign it a default value in thePythonActivity.java
file. I’ll provide a pull request later.@AndreMiras strlen+71 and “fault addr 0x0” indicate a strlen on a null char pointer. If you compiled with sdl2 bootstrap, it’s located in https://github.com/kivy/python-for-android/blob/764b59ec1c97b413a7c5808da9f1168f0e4a5874/pythonforandroid/bootstraps/sdl2/build/src/main/java/org/kivy/android/PythonService.java#L134
The implementation is done at https://github.com/kivy/python-for-android/blob/764b59ec1c97b413a7c5808da9f1168f0e4a5874/pythonforandroid/bootstraps/sdl2/build/jni/src/start.c#L291
So one of theses are NULL, so passed NULL from the java i guess. If you have a environement you can play with, just log them in Java first to see which one is wrong, before going to nativeStart. It will help, and no need to recompile and debug the native part.