Missing refresh_token param in request?

[RandomInsano]

I'm very new to low-level OAuth2, so it may be something I'm doing, but I've hit a bit of a problem running the examples:

thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: Parse(ExpectedFieldType("refresh_token", "string"))', src/libcore/result.rs:746

This is using the following example code:

    fn main() {
        let client = Client::<Installed>::new(
            String::from("beep"),
            String::from("boop"),
            Some(String::from("http://example.com/"))
        );

        let http_client = Default::default();
        let token = client.request_token(&http_client, "4/Dwu8lXSrdeT_Yy9xBVoNNVaNP8Xel7ikNoXXS6yixEo").unwrap();
        // Fails here ^
        println!("Request probably worked?");
        println!("{}", token.access_token());
    }

It's not overly clear from the examples what I should have put into request_token(), but it doesn't seem to matter here. Any data fails equally well. 😃

It seems to partially get through the authentication as I get this error if the code was already used:

thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: OAuth2(OAuth2Error { code: InvalidGrant, description: Some("Code was already redeemed."), uri: None })', src/libcore/result.rs:746

Thoughts? Anything I should test or change?

[RandomInsano]

After some digging, the problem seems to have been that I was mixing up flows a little bit. I think the "Installed" client shouldn't take a URL, and when running that flow, Google sends the auth token back with the initial request, which doesn't seem to get handled properly here.

Changing the client type to "Web" got things working, but I'm curious how to make this work properly with installed clients. It seems like it can't work given the examples and Google's control flow.

[causal-agent]

From my understanding, selecting "Web" or "Other" (installed) when creating a Google API client changes what sort of token Google gives you (expiring or refreshable, respectively), but the flow for obtaining one is the same. That is, the user is directed to an authorization URI, which prompts the user to authorize the application, and an authorization code is sent back to the application either through redirect or copy-paste from the urn:ietf:wg:oauth:2.0:oob URN.

If there is a flow that I missed, please point me to the Google API documentation for it.