Announcements
Hello everyone! We are aware and investigating some issues with payments right now. Click this link for more info.

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Songs containing extended latin or japanese characters no longer appear in Local Files

Solved!

Songs containing extended latin or japanese characters no longer appear in Local Files

Suddenly some of my local song became unolayable. When I started the local files search again it scanned only few of them. I checked what songs were in Licam Files so I could get a better picture of whaf is causing this. I found out that some of my folders use extended latin characters like é or č. I renamed all the folders so there aren't any of those characters and now the songs thag were in those folders came up in the Local Files. Unfortunately the same goes for the songs. What is causing this? I don't want to rename all of my songs so they can appear in spotify and why did it work before? This issues started recently, I don't know what went wrong. 

Plan

Premium

Country

Slovakia

 

Device

Lenovo Legion Y520

Operating System

Windows 10

 

My Question or Issue

 

Reply

Accepted Solutions
Marked as solution

Hey @ZyLacx

 

Thanks for reaching out about this in the Community.

 

We’re aware of an Ongoing Issue causing the behavior that you describe and the team in charge is currently looking into it.

 

In this case, we’d recommend adding your +Vote to the Ongoing Issue. You can also subscribe to it by clicking the three-dot menu next to the title and we’ll keep you updated with any relevant updates there.

 

We'll be right here if you need us again.

View solution in original post

1 Reply
Marked as solution

Hey @ZyLacx

 

Thanks for reaching out about this in the Community.

 

We’re aware of an Ongoing Issue causing the behavior that you describe and the team in charge is currently looking into it.

 

In this case, we’d recommend adding your +Vote to the Ongoing Issue. You can also subscribe to it by clicking the three-dot menu next to the title and we’ll keep you updated with any relevant updates there.

 

We'll be right here if you need us again.

Suggested posts