-
Notifications
You must be signed in to change notification settings - Fork 242
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
Issues with using threads on an iOS device #609
Comments
I'm having the same issue. Have you found a solution? |
I haven't experienced this specific problem, but I have worked around threading issues by having the main thread callback a simple function using the scheduler e.g.
|
I have a issue with ios application based on kivy, can you help for me . |
Looks like you are modifying a thread-unsafe The advice from StackOverflow is to only modify the UI from the main thread. Closing as Won't Fix: Working As Designed. |
Versions
Describe the bug
I have built an app that makes use of the Python threading module to sent POST requests to an API. The information returned then causes changes to the properties of certain widgets. The issue is that using threads sometimes results in parts of the UI being called from a background thread (i.e. not the main thread), which crashes the app. The Xcode logs throw out the following exception:
To Reproduce
Below is the code I use to make the requests:
The app makes no more than 5 asynchronous requests at one time, and is called from the function below:
Expected behavior
Unusually, there seems to be no obvious cause for this. Most of the time the threads work fine, but about one in every ten requests result in the program crashing.
Logs
Additional context
Quite a few Swift developers on StackOverflow have posted about this issue. But none so far have been Kivy related.
The text was updated successfully, but these errors were encountered: