You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently came across the error "Could not determine type for" when performing a URL search. After some tests I found out that this is due to the language set by the user in the preferences: when it's not English, the sharing URL adds an ISO 639 code to it, so for example if set in spanish, it ends in the following: https://open.spotify.com/intl-es/track/2EGxVI3bgR6YEDtid76ZzZ?si=2a7eeb69f99946bc
Which does not work for searching and downloading because of the intl-es added to the URL.
This language code part needs to be manually erased for d-fi to take it into consideration and not throw such error. This being said, the following is correctly detected: https://open.spotify.com/track/2EGxVI3bgR6YEDtid76ZzZ?si=2a7eeb69f99946bc
Last part of the sharing URL string does not mind (from ? and on).
Will there be any possibility to change this in a next release so it works despite the chosen application language?
The text was updated successfully, but these errors were encountered:
Hello!
I recently came across the error "Could not determine type for" when performing a URL search. After some tests I found out that this is due to the language set by the user in the preferences: when it's not English, the sharing URL adds an ISO 639 code to it, so for example if set in spanish, it ends in the following:
https://open.spotify.com/intl-es/track/2EGxVI3bgR6YEDtid76ZzZ?si=2a7eeb69f99946bc
Which does not work for searching and downloading because of the intl-es added to the URL.
This language code part needs to be manually erased for d-fi to take it into consideration and not throw such error. This being said, the following is correctly detected:
https://open.spotify.com/track/2EGxVI3bgR6YEDtid76ZzZ?si=2a7eeb69f99946bc
Last part of the sharing URL string does not mind (from ? and on).
Will there be any possibility to change this in a next release so it works despite the chosen application language?
The text was updated successfully, but these errors were encountered: