[GH-ISSUE #236] Futures are not Send #80

New issue

Closed

opened 2026-02-27 20:22:59 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 20:22:59 +03:00

Owner

Originally created by @kebabtent on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/236

Originally assigned to: @marioortizmanero on GitHub.

I am using the latest commit in the master branch. The futures produced by the client are not Send, meaning the client cannot be used inside a spawned task. Is there any way around it or are there plans to resolve it?

Minimal example:

#[tokio::main]
async fn main() {
    tokio::spawn(spotify());
}

async fn spotify() {
    let creds = rspotify::Credentials::from_env().unwrap();
    let mut spotify = rspotify::ClientCredsSpotify::new(creds);
    spotify.request_token().await.unwrap();
}

Originally created by @kebabtent on GitHub (Aug 6, 2021). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/236 Originally assigned to: @marioortizmanero on GitHub. I am using the latest commit in the master branch. The futures produced by the client are not `Send`, meaning the client cannot be used inside a spawned task. Is there any way around it or are there plans to resolve it? Minimal example: ```rust #[tokio::main] async fn main() { tokio::spawn(spotify()); } async fn spotify() { let creds = rspotify::Credentials::from_env().unwrap(); let mut spotify = rspotify::ClientCredsSpotify::new(creds); spotify.request_token().await.unwrap(); } ```

kerem

2026-02-27 20:22:59 +03:00

closed this issue
added the
help wanted

bug
labels

kerem commented

2026-02-27 20:23:00 +03:00

Author

Owner

@marioortizmanero commented on GitHub (Aug 7, 2021):

Hmm. The futures are Send if ureq is being used, but not for reqwest. I'll investigate more, but it doesn't seem to be async_trait's fault.

@marioortizmanero commented on GitHub (Aug 7, 2021): Hmm. The futures are `Send` if `ureq` is being used, but not for `reqwest`. I'll investigate more, but it doesn't seem to be `async_trait`'s fault.

kerem commented

2026-02-27 20:23:00 +03:00

Author

Owner

@marioortizmanero commented on GitHub (Aug 7, 2021):

Ok, this seems to be a side effect of using #[async_trait(?Send)] for the BaseClient trait. I used it at the beginning so that the function signatures would be simpler but it seems we do need Send.

@marioortizmanero commented on GitHub (Aug 7, 2021): Ok, this seems to be a side effect of using `#[async_trait(?Send)]` for the `BaseClient` trait. I used it at the beginning so that the function signatures would be simpler but it seems we do need `Send`.

kerem commented

2026-02-27 20:23:01 +03:00

Author

Owner

@marioortizmanero commented on GitHub (Aug 7, 2021):

This is fixed by #237

@marioortizmanero commented on GitHub (Aug 7, 2021): This is fixed by #237

kerem referenced this issue

2026-02-27 20:23:53 +03:00

[PR #80] [CLOSED] Implement async/await on all methods #231