Tidal SDK for Android Login problem

[ForMiSoft]

I'm trying to login to Tidal in my Android application using Tidal SDK for Android. After receiving this loginUrl from initializeLogin():

https://login.tidal.com/authorize?redirect_uri=&scope=playlist.read&client_id=<MY-CLIENT-ID>&code_challenge_method=S256&code_challenge=<CHALLENGE-CODE>&lang=en_US&appMode=android

I opened the loginUrl in the WebView and instead of the login page it shows this and the response status is 400 (Bad Request):

Please help me to solve this problem. What am I doing wrong?

[aliaksei-taliuk]

@ForMiSoft hi! thanks for reaching out to us. I forwarded your request to the people who are responsible for Auth SDK.
Will keep you posted.

[ForMiSoft]

I changed the redirectUri from https://formisoft.cz to https://formisoft.cz/test on the developer portal and in my code and it's still the same. So it wasn't the culprit. I would guess that there is a problem either with the finalizing login on the server side or with the credentialsProvider.isUserLoggedIn() function. Because I don't know what those functions internally do, it's hard to say which one isn't working properly.

Can you log out the requests and the responses and post that here?

Of course, what filter should I use?

[ForMiSoft]

Wouldn't it be easier if you tried putting my project credentials in the auth demo app?

[michpohl]

I found out there actually is a bug - so you should keep using https://formisoft.cz/test as your redirectUri. There is an error when handling the address if there is no path after the domain name.

Make sure to completely wipe the data and do a re-sync in Android Studio just in case it before testing.

Regarding sending us credentials, I will first have to find out if I am legally allowed to do that 😄

So for the time being, the easiest is if a) you fork the repo yourself and insert the credentials or b) turn on logging. This can be done by following this:

1. Add these dependencies to your app:

    implementation("org.slf4j:slf4j-api:2.0.12")
    implementation("com.github.tony19:logback-android:3.0.0")

2. Ad a logback.xml with the following contents to your assets folder

<configuration
    xmlns="https://tony19.github.io/logback-android/xml"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="https://tony19.github.io/logback-android/xml https://cdn.jsdelivr.net/gh/tony19/logback-android/logback.xsd"
>
    <appender name="logcat" class="ch.qos.logback.classic.android.LogcatAppender">
        <tagEncoder>
            <pattern>%logger{12}</pattern>
        </tagEncoder>
        <encoder>
            <pattern>[%thread] %-5level %logger{36}: %msg%n</pattern>
        </encoder>
    </appender>

    <root level="TRACE">
        <appender-ref ref="logcat" />
    </root>
</configuration>

3. Add this parameter when creating your AuthConfig:

 logLevel = NetworkLogLevel.BODY,

Then, if you filter for tidal.com, you should get some meaningful logs that help us understand the issue.

[ForMiSoft]

Regarding sending us credentials, I will first have to find out if I am legally allowed to do that 😄

It's not such a big deal, I would delete that project afterwards and create a new one. And I'm pretty sure that any credentials would do the same. You can just create a new project, set is as Android one and enable its scope for playlists.read. Then you could debug it much easier than using this github proxy.

Meanwhile, I'll try the b) option.

[ForMiSoft]

I added you as a collaborator to my repository.

[ForMiSoft]

I can't send the log here, because it contains the credentials. Should I send it to your email?

[michpohl]

I added you as a collaborator to my repository.

This was a good idea. I'll have a look in a bit.

[michpohl]

Here's your problem:
In ExtendedWebClient you changed this function:

private fun hasRedirectUri(uri: Uri): Boolean {
        return if (uri.toString().startsWith("")) {
            onRedirectUriReceived(uri)
            true
        } else {
            false
        }
    }
    ```
Now this one is called with every url the webview tries to load, therefore this check needs to verify if the one passed in is your `RedirectUri`. With your change this will call `onredirectUriReceived` on every address you pass in, and since it loads others before the relevant one your login process fails as the code behind `finalizeLogin` only understands the correct uri.
So if instead you check for `https://formisoft.cz/test` in here your login succeeds.

[ForMiSoft]

Thank you very much for your help. 👍

[michpohl]

Absolutely, you're welcome. Please keep in mind that there is an issue with the redirectUri needing a path (will be fixed in the next minor version, but until then, keep the /test or something similar in your uri) 😄

[ForMiSoft]

I closed that thread a bit prematurely. In the end it's not logged in. But now I have another problem because the developer's portal is broken and I can't edit my projects. Dne út 15. 10. 2024 16:13 uživatel Michael Pohl ***@***.***> napsal:

…

Absolutely, you're welcome. Please keep in mind that there is an issue with the redirectUri needing a path (will be fixed in the next minor version, but until then, keep the /test or something similar in your uri) 😄 — Reply to this email directly, view it on GitHub <#103 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6FTCTFVI64YMVGZ4OAKXN3Z3UPH5AVCNFSM6AAAAABPTDVRUOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJUHA2TMMQ> . You are receiving this because you modified the open/close state.Message ID: ***@***.*** .com>