Can you also check the "Insights" page (accessible on the settings page) and see if Save Errors isn't 0.

• If it's 0, then there can be 2 things wrong:
  • The library we're using to find media files on your device isn't finding any.
  • The library we're using to find media files on your device do find them, but return a file uri of a different format.
• If it's not 0, then there might be something wrong with the metadata structure.
  • I found out in an error in Sentry (error reporting software) by accident (since we changed how remove logging in the production app - which didn't work) that we were sometimes getting a full date-time value in the "year" field in the metadata for some tracks and that was throwing an error since we attempt to convert it to a number.
  • There was a different error that I couldn't reproduce which was file path being parsed incorrectly (so that problem might be device based).

If you get 0, I can whip up a quick project to check what we use to find the media files finds and narrow down the issue from there.

Yes, in the Insights page the Save Errors isn't 0.

Can you try installing v1.0.3-rc.1. This is only available through the APK version of the app since app reviews takes forever (ie: If you have the Play Store version of the app installed, uninstall it).

This fixes the issue with the "year" field mentioned above if this happens to be the issue you're facing. Otherwise, we can get a better understanding of what's happening through the new "Save Errors" page that I've added that lists out the cause of why the track was rejected and we can go from there.

As per your suggestion, I installed version 1.0.3-rc.1 and the problem's still there ofcourse. Though, the new "Save Errors" page is displaying the location of every track and then maybe the reason, "[Error] null".

Exactly like the following,

file:///storage/emulated/0/Music/<track-name>.<extension(mp3 in my case)>
[Error] null

Did you "update" the APK installation you currently have or installed the the APK fresh? If you "update" the existing APK (ie: install the latest version while having a previous APK version installed), then use the "Rescan" feature in the "Library" page to generate the correct error messages since they don't exist for "existing" error entries.

If you did a fresh install and got this, then it's weird that there's no error message displayed when there should be. Then this might just end up being the case of it being a device issue (ie: maybe there's an API that your device doesn't support and that's causing some error).

A last resort is to send one of the files to [email protected] so I can debug it if by the off chance, it's a file problem (though I don't think it based on the earlier screenshots you sent).

Update: I never actually emailed the files to the email address provided by you and was using some other Music player till that. I decided to randomly install the v1.0.3 and reassure myself about this problem. I have downloaded some new music files in between the time I mentioned before and from a different source. Those new .mp3 files were actually showing up in the software. Yet, only the new ones.

So I come to the conclusion that the old files were the only problem. The common thing in the old files is that their bitrate is higher than the bitrate of the new ones.