arl invalid or expired error

[denys-lysiuk]

Bug Description

Cannot launch the app neither with the email/password set in secrets, nor the arl. "arl invalid or expired" error is shown in both cases. The same arl works fine when using Deezer through Lyrion Media Server plugin on the same machine.

Steps to Reproduce

1. Launch the app with "pleezer -s".
2. Observe error message.

Logs

denys@raspberrypi:~ $ pleezer --name "BasX" -s /home/denys/secrets.toml -vv
[2024-11-25T12:57:57Z DEBUG pleezer] Command Args {
        secrets_file: "/home/denys/secrets.toml",
        name: Some(
            "BasX",
        ),
        device: None,
        no_interruptions: false,
        hook: None,
        quiet: false,
        verbose: 2,
        eavesdrop: false,
    }
[2024-11-25T12:57:57Z INFO  pleezer] starting pleezer/0.2.0; release; en
[2024-11-25T12:57:57Z INFO  pleezer] using arl from secrets file
[2024-11-25T12:57:57Z TRACE pleezer] device uuid: 02b65b79-f09d-5686-ae9a-e26874337ba2
[2024-11-25T12:57:57Z TRACE pleezer] user agent: pleezer/0.2.0 (Rust; linux/12; like Desktop; en)
[2024-11-25T12:57:57Z TRACE pleezer] client id: 473013585
[2024-11-25T12:57:57Z DEBUG pleezer::player] no bf_secret specified, fetching one from the web player
[2024-11-25T12:57:58Z TRACE pleezer::config] bootstrapping from https://e-cdn-files.dzcdn.net/cache/js/app-web.c10e656b5b37510df88f.js
[2024-11-25T12:57:58Z INFO  pleezer::player] audio output device: default on ALSA
[2024-11-25T12:57:58Z TRACE pleezer::remote] remote version: 2000
[2024-11-25T12:57:58Z ERROR pleezer] Permission denied { arl invalid or expired }

Operating System

Raspberry Pi OS 12

pleezer version

0.2.0

Rust version (if building from source)

1.82.0

Hardware specifications

Raspberry Pi 5 4GB

Deezer client specifications

10.25.1.1 - iOS 18.1.1

Additional Context

No response

Due Diligence

• I am using the latest version of pleezer
• I have searched the issues for similar reports
• I have included a full verbose log from launch to the issue, not just an excerpt
• I confirm that this is an issue with pleezer, not with my system configuration or other software
• I confirm that this is not a security issue, which should be reported privately
• I have read and understood the Contributing guidelines

[roderickvd]

Hey, thanks a lot for giving it a spin and letting me know. I'd be interested in seeing the HTTP response to our query, maybe it's returning something different for you than for me, causing it to fail deserialization.

Are you able to provide me with a copy of the HTTP responses e.g. by feeding it through a proxy? Otherwise I can whip up out a small branch that prints out the response to see.

[denys-lysiuk]

Are you able to provide me with a copy of the HTTP responses e.g. by feeding it through a proxy?

I don't know how to do that unfortunately.

[roderickvd]

Can you try #34? It won't fix it, but will aid debugging by spitting out the raw response (be sure to use -vv for trace logging).

Also could you share some anonymised version of your secrets.toml? Just replace the real values with fictional characters, but let me know if there are any special characters that I should know about.

[denys-lysiuk]

logs.zip
Stripped some characters from tokens and keys. No 'extraordinary' special characters as far as I'm aware.

[roderickvd]

Perfect, this should be enough to fix it for you and others, I'll let you know.
I removed your file for privacy.