usage with tokio panics about gauth-rs HOT 5 CLOSED

@adnanjpg thank you pointing this out. Let me test the scenarios you mentioned and hopefully we can find a good solution. So far I've been using the the serv_account module in this project with tokio runtime https://github.com/makarski/mstream/blob/main/src/cmd/listener.rs#L24-L25. However, the dependency there is gauth = 0.4 that is using a version of reqwest before async was introduced.

Before the issue is fixed, a version 0.4 will do, as the changes introduced in 0.5 affect the desktop app auth - there i also updated the reqwest client that introduced the issue.

from gauth-rs.

Also always looking forward to have a PR opened

from gauth-rs.

as suggested in this stackoverflow answer, running the from_file function on a seperate thread fixes the issue

use std::thread;

#[tokio::main]
async fn main() {
    thread::spawn(|| {
        gauth::serv_account::ServiceAccount::from_file(
            "service-account-key.json",
            vec!["https://www.googleapis.com/auth/firebase.messaging"],
        );
    })
    .join()
    .expect("Thread panicked")
}

from gauth-rs.

after investigation, the actual reason for this error is the usage reqwest::blocking::Client, as that apparently interferes with the threads that tokio is supposed to manage.

converting all necessary to async actually fixes the problem.

however, using async functions breaks the tests, as per my research it appaears that an external async test library is required.

if you're interested, I can open a pr with the current work

from gauth-rs.

sure, here's the pr #26

from gauth-rs.