Bug? Downloading an album only downloads the first track

[Steven Mackenzie]

I have bubbleupnp player 3.5.1.1 (arm64-v8a)

on a Samsung Note 10 with Android 11

I use Twonky Server 8.5.1 to serve .flac and .mp3 files

If I browse the Twonky media server to find an album, and use the 

"..." menu > Download 

option to download the album I will see a notification saying that multiple tracks are being downloaded (1/11, 2/11, ... etc). 

In the Library page I change to the local server and browse then I can see the new album folder, but inside there is only a single track (track 1) present.

I expected to see all of the tracks from the original album.

[Bubblesoft]

Weird issue. Cannot reproduce it on my SGS9 Android 10.

Can you send me (bubblesof...@gmail.com) a log file, downloading an album from Twonky that has this issue:

- launch the app
- go into More > Gear icon > Control
- Enable "logging to file" (at the end of the page).
- IMPORTANT: Exit the app (More > "X" bottom left icon)
- restart the app
- download an album from Twonky
- exit the app
- email me the files found on internal storage:

/Documents/com.bubblesoft.android.bubbleupnp_log.txt
/Documents/prev_com.bubblesoft.android.bubbleupnp_log.txt  (if present)

You can access them with a file manager app and share them to your email app for sending them.

IMPORTANT: Make sure to not restart BubbleUPnP until you have sent or saved the log file as it is overwritten on app startup.

[Steven Mackenzie]

Done.

Using the My Files app on my phone I can see that all the files that I expected were downloaded, but only the first track is shown in the Local Library of BubbleUPnP, even after a restart.

[Steven Mackenzie]

If I download all the files from an SMB share using the Samsung My Files app, and then copy them to the BubbleUPnP download folder, then they get correctly indexed and available via the BubbleUPnP app in the Library page. (Even though they are not available if they get downloaded to the same place using the BubbleUPnP app.

[Bubblesoft]

The cause of this issue has been identified and will be fixed in the next app update.

It only happens on Android 11.