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
I'm using the ktx library. Since I want to handle each type of permission denied event separately, I was trying to convert the callback API to coroutine and call every kind of permission request sequentially. Then I found that after the first coroutine executed and the request dialog was showed, the next coroutine will be inactive, and could not to resume, thus the future coroutines could not be execute.
I also found that when all the permissions was granted, the coroutine sequence could execute correctly. The only difference between the two cases is whether or not a permission request dialog pops up.
Expected
Permission request coroutine could run correctly.
Actual
After a permission request dialog was showed, the next coroutine will be inactive.
Environment
permissionsdispatcher-ktx:1.0.1
The text was updated successfully, but these errors were encountered:
Overview
I'm using the ktx library. Since I want to handle each type of permission denied event separately, I was trying to convert the callback API to coroutine and call every kind of permission request sequentially. Then I found that after the first coroutine executed and the request dialog was showed, the next coroutine will be inactive, and could not to resume, thus the future coroutines could not be execute.
I also found that when all the permissions was granted, the coroutine sequence could execute correctly. The only difference between the two cases is whether or not a permission request dialog pops up.
Expected
Permission request coroutine could run correctly.
Actual
After a permission request dialog was showed, the next coroutine will be inactive.
Environment
permissionsdispatcher-ktx:1.0.1
The text was updated successfully, but these errors were encountered: