You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When extracting NumPy's tar archive from pypi.org (~65mb archive with ~7k files) I encountered the app constantly erroring with Android's not responding pop-up. The extraction succeeded however the app's UI was unresponsive during extraction thus Android decided to constantly prompt me to either kill the app or wait, choosing wait allowed the extraction to continue.
To Reproduce
Steps to reproduce the behaviour:
Attempt to extract a tar archive with a large amount of small files.
Witness Android panic due to the app's UI not being responsive.
Sit through countless app is not responding pop-ups having to click wait on every single one.
Expected behaviour
The app's UI should be responsive, or at least not trigger Android's built-in app not responding prompt.
Screenshots
Smartphone (please complete the following information):
Additional context
From my limited understanding of Android app development this shouldn't happen if the extraction function is called asynchronously so that the UI is able to update even while the extraction is running. Kotlin docs on asynchronous programming are here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When extracting NumPy's tar archive from pypi.org (~65mb archive with ~7k files) I encountered the app constantly erroring with Android's not responding pop-up. The extraction succeeded however the app's UI was unresponsive during extraction thus Android decided to constantly prompt me to either kill the app or wait, choosing wait allowed the extraction to continue.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
The app's UI should be responsive, or at least not trigger Android's built-in app not responding prompt.
Screenshots
Smartphone (please complete the following information):
Additional context
From my limited understanding of Android app development this shouldn't happen if the extraction function is called asynchronously so that the UI is able to update even while the extraction is running. Kotlin docs on asynchronous programming are here.
The text was updated successfully, but these errors were encountered: