Doesn't work locally #146

Activity

2. axljones commented on Oct 6, 2023

   

   axljones

   on Oct 6, 2023

   Author

   More actions

   Recently tested using docker on my local, I wasn't able to reproduce this issue with Firefox 115.3.0esr (64-bit). Just writing to provide additional information, PR for docker usage: #148

   Did you go through with the import?
   Did you run this on a server with a publicly reachable ip address?
4. axljones commented on Oct 6, 2023

   

   axljones

   on Oct 6, 2023

   Last edited by axljones

   Author

   More actions

   I ran it on my local PC, using;

   `docker build . -t exportify

   docker run -p 3000:3000 exportify`

   And then went to http://localhost:3000/ on my browser. Then I exported a couple of playlists, the data was correct

   The dockerfile didn't exist when I tried last time.

   I've tried it again and get the same issue. Could you give me the redirect URI you get ?

   Especially the value of the redirect_uri parameter.

   I'm running the docker image on a local server, not my actual PC.
6. axljones commented on Oct 7, 2023

   

   axljones

   on Oct 7, 2023

   Author

   More actions

   It's in the form of

   https://accounts.spotify.com/en/authorize?client_id=[clientid]&redirect_uri=http%3A%2F%2Flocalhost%3A3000%2F&scope=playlist-read-private%20playlist-read-collaborative%20user-library-read&response_type=token&show_dialog=false

   Maybe spotify makes an exception for localhost when handling these requests, but not for the IP address of a local server, if you are using an IP address in the local network?

   Yes, that is exactly what i was thinking originally. I tried using localhost but it didn't work because i didn't specify the port. It worked with your redirect_uri. I then got a new redirect url with a token so i replaced the localhost with my ip. It now loads but seems stuck in a loop. I'll keep this issue updated

   http://localhost:3000/exportify#access_token=[access_token]&token_type=Bearer&expires_in=3600

   
7. awsms commented on Nov 7, 2023

   

   awsms

   on Nov 7, 2023

   Last edited by awsms

   More actions

   both selfhost methods (docker & running it directly with yarn) did not work for me. the service hosted on github.io doesn't work either though :(
   using ungoogled-chromium 119.0.6045.105
8. watsonbox commented on Feb 18, 2024

   

   watsonbox

   on Feb 18, 2024

   Owner

   More actions

   Converting this to a discussion in case it evolved. I can only guess that there must be something unusual about your browser or extensions causing this issue, since that local redirect URI is valid for the app and works for others.
9. Repository owner locked and limited conversation to collaborators on Feb 18, 2024
10. watsonbox

    converted this issue into a discussion #152 on Feb 18, 2024