Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Not Recording When Using Spotify Metadata
See original GitHub issueWhat is the bug ?
Everything works absolutely fine when using the LastFM API for metadata retrieval, however when I switch to using the Spotify API the tracks no longer record. I know the Spotify API credentials are correct as I’m using them in other applications with no problems. When using the Spotify API I get a redirect error INVALID_CLIENT: Invalid redirect URI but as I understand it that is related to my app redirect rather than anything on the Spytify end.
Screenshots
Example of rediirect error
Example showing trsck playing but not recording (previous recordings occured when LastFM API was selected)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Did you set the redirect URI in your Spotify API Application ? If not you can edit it in your application by clicking on edit settings
I think it is better discussed in #310 (which is actually my auto-bugreport) or a new Issue (?), because I tested it now. This happens with last.fm API as well, and with every track. I switched back to 1.7, where it works both with spotify and last.fm API. Maybe it has something to do with the fact that my music is located in a samba share?