Could not sign in to Google, keep looping back to the sign-in page

Issue description:

I could not proceed to login with Google.

Select Primary Source > Google Drive > Sign-in with Google > choose account > Continue (allow Symfonium permission) > being loopback to the Sign-in with Google page.

Logs:

Upload description: Could not login to Google

Additional information:

 

 

Reproduction steps:

 
Select Primary Source > Google Drive > Sign-in with Google > choose account > Continue (allow Symfonium permission) > being loopback to the Sign-in with Google page.
 

Media provider:

Google Drive

Screenshots:

     

You did not upload logs so hard to tell anything.

Check Error 404 when trying to authenticate to a cloud provider

It happened when I first installed the app, so I could not get the log. I also upload a video clip through the upload page and pasted the description here, but it doesn’t show up here.

Let me try to come up with something to show you.

I have seen the video but this does not help :wink: Read the link I gave you first.

Then add the local device with no directory to then add google drive with logs if the interface does not automatically offers to enable them.

1 Like

I have uploaded some forms of log from the app. Hope that you could see it.

I’ve also used the steps in the link, but the problem still persists.

Hum google refuse the token but does not give a message. Is this a special account or something ?

Mine is a Premium 2tb account, subscribe directly with Google. Not too sure if this is a special account tho…

Try with another browser ?

Tried again with Google Chrome and have uploaded the log. Yesterday, I tried with a different device as well (Google Pixel 5). All with the same problem :’(

Honestly no idea Google does not return a message so it’s hard to know what fails :frowning: Are you using a VPN or proxy or adblock or anything that could intercept ?

Tried, and logged again with the default OnePlus browser, and disabled the adblock features from Vivaldi and Oneplus browser, but no success. It is so weird :smiling_face_with_tear:

I am having the same issue. These are the things I did. I don’t know if any of these could be causing the issue but I’m just trying to think of everything I did before the login issue occured.

Made a backup of the app config (everything. Media provider, UI config, playlists etc)
I factory reset my phone.
Reinstalled the app
Loaded the backup
Google drive failed to sync
Removed the media provider connections loaded from backup
Tried adding google drive again
Login goes back to the app without connecting to Google Drive

I tried to login with another google account. The connection works for that account somehow. I checked the 3rd party connections in that account and I can see that Symfonium has made a connection. That doesn’t happen with my 2TB main account. I don’t know what happened to the connection previously made to this 2TB account that I have my music in.

Edit - Typos

I found a temporary work around. This is really stupid.

As I mentioned in my previous reply, my 2nd account works to connect to Symfonium. So, I shared my MUSIC folder from the Pro account to my 2nd account and I could add that shared folder to be scanned as a library in the app.

I wonder what broke the connection to the main account though.

1 Like

I need to try this and will report soon. Thank you for the suggestion.

Edit: It ducking works!! There is definitely something weird with the 2tb account.

Again what kind of accounts are those ? If it’s work / school accounts, admins often disable third party access that can cause this.

It’s a normal google account but subscribe to the 2tb upgrade directly with Google.

Ok was able to reproduce with a friends accounts, strange it did not occur with mine (It’s 2tb but free for 1 year with the pixel).

Will be fixed in next release.

2 Likes

Thank you for your attention to the matter!

Hello there, I am glad I found this thread because the exact same thing is happening to my 2TB normal account. I hope it can be fixed.

mr. Tolrig has confirmed that a fixed will be deployed in the next update, so don’t you worry!