We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Im not sure if there currently is a way to do this.
But right now I think there is no way to use the android_wakelock::Guard across an await boundary because of its raw pointers stored in env.
android_wakelock::Guard
I would like to acquire the wakelock, run some async tokio code and only after this is done release the lock.
I don't see why the attached thread needs to be stored inside the guard? The Java API should be thread save.
So can't you just attach a new env on release?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Im not sure if there currently is a way to do this.
But right now I think there is no way to use the
android_wakelock::Guard
across an await boundary because of its raw pointers stored in env.I would like to acquire the wakelock, run some async tokio code and only after this is done release the lock.
I don't see why the attached thread needs to be stored inside the guard? The Java API should be thread save.
So can't you just attach a new env on release?
The text was updated successfully, but these errors were encountered: