Originally created by @ljlongwing on GitHub (Sep 13, 2024).
What was the Problem?
I log onto my server and always download the books locally while listening so that I'm not reliant on connection to the server, the download typically works well. But recently I've been getting red ! marks on the image, with a note that states "Media is linked to this server but was downloaded by a different user. Progress will only be synced to the user that downloaded it." I only connect with one user, so it's entirely not possible to be a different user
Steps to Reproduce the Issue
I'm not getting this all the time, but frequent, so I'm not sure about reproduction steps
What was Expected?
it would be nice if it recognized that I'm me and I'm the one that downloaded the book
Phone Model
Samsung Galaxy S22+
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
No response
Originally created by @ljlongwing on GitHub (Sep 13, 2024).
### What was the Problem?
I log onto my server and always download the books locally while listening so that I'm not reliant on connection to the server, the download typically works well. But recently I've been getting red ! marks on the image, with a note that states "Media is linked to this server but was downloaded by a different user. Progress will only be synced to the user that downloaded it." I only connect with one user, so it's entirely not possible to be a different user
### Steps to Reproduce the Issue
I'm not getting this all the time, but frequent, so I'm not sure about reproduction steps
### What was Expected?
it would be nice if it recognized that I'm me and I'm the one that downloaded the book
### Phone Model
Samsung Galaxy S22+
### Phone OS
Android 14
### Audiobookshelf App Version
Android App - 0.9.76
### Installation Source
Google Play Store
### Additional Notes
_No response_
adam
added the bugandroid labels 2026-04-24 23:46:30 +02:00
There have been a few reports of this in Discord. Did you update your server after downloading the books?
Does resetting the app data and logging back in to the server fix it?
@nichwall commented on GitHub (Sep 13, 2024):
There have been a few reports of this in Discord. Did you update your server after downloading the books?
Does resetting the app data and logging back in to the server fix it?
Yes, I keep my server updated, and this happens regularly, while I might have the books on my phone for awhile, so it's entirely probable that the server has been upgraded between downloads.
So, resetting the app caused it to not know about my downloads folder, which of course made it not know the book was already downloaded....re-adding my download folder doesn't seem to have made it aware that the book was already in the folder either....thus, the only option I saw, was to tell the client to again download the file....which of course puts the client and the server on the same note regarding who downloaded it....so, while this 'fixed' the issue with this book, I have several other books already downloaded as well, which my client no longer recognizes as downloaded....so....I don't feel this 'reset the client' thing is a fix for the problem....just causing more issues
@ljlongwing commented on GitHub (Sep 13, 2024):
Yes, I keep my server updated, and this happens regularly, while I might have the books on my phone for awhile, so it's entirely probable that the server has been upgraded between downloads.
So, resetting the app caused it to not know about my downloads folder, which of course made it not know the book was already downloaded....re-adding my download folder doesn't seem to have made it aware that the book was already in the folder either....thus, the only option I saw, was to tell the client to again download the file....which of course puts the client and the server on the same note regarding who downloaded it....so, while this 'fixed' the issue with this book, I have several other books already downloaded as well, which my client no longer recognizes as downloaded....so....I don't feel this 'reset the client' thing is a fix for the problem....just causing more issues
I don't see how this could happen. We'll first need to be able to reproduce the issue so if you can figure out a way to reproduce it that would be helpful
@advplyr commented on GitHub (Sep 16, 2024):
I don't see how this could happen. We'll first need to be able to reproduce the issue so if you can figure out a way to reproduce it that would be helpful
I'm having this issue as well. Media was downloaded on the same network as the server, with the same user being logged into the app the whole time. Most recent version is installed on both phone and server.
@brand421 commented on GitHub (Sep 28, 2024):
I'm having this issue as well. Media was downloaded on the same network as the server, with the same user being logged into the app the whole time. Most recent version is installed on both phone and server.
I was seeing this as well with version 2.15.0 of the server and v0.9.76-beta of the android app. I force stopped the app and cleared the app storage. Logging back in to everything seems to have made the error go away.
@jnsimon commented on GitHub (Oct 17, 2024):
I was seeing this as well with version 2.15.0 of the server and v0.9.76-beta of the android app. I force stopped the app and cleared the app storage. Logging back in to everything seems to have made the error go away.
First off, awesome work on this project, this is one of my most used apps and it's more polished than some commercial options.
I've been having this issue for some time now over multiple updates to the droid app and server. I've been making due, just dropped over to check on possible fixes after another server update hadn't fixed it.
I killed and cleared storage as @jnsimon commented, and for now it seems to work (only been 10 minutes or so really). But honestly it's not a fix I would want to tell my mom or wife they'd have to do as it does delete all client side data - and even through the audiobook files are in a separate folder it won't detect the media is already downloaded so I had to manually clean and re-download all the books my kids are I are in the middle of.
Fingers crossed it's a one time fix and this doesn't come back.
Thank you all again again for an amazing project!
@meyeaard commented on GitHub (Oct 30, 2024):
First off, awesome work on this project, this is one of my most used apps and it's more polished than some commercial options.
I've been having this issue for some time now over multiple updates to the droid app and server. I've been making due, just dropped over to check on possible fixes after another server update hadn't fixed it.
I killed and cleared storage as @jnsimon commented, and for now it seems to work (only been 10 minutes or so really). But honestly it's not a fix I would want to tell my mom or wife they'd have to do as it does delete all client side data - and even through the audiobook files are in a separate folder it won't detect the media is already downloaded so I had to manually clean and re-download all the books my kids are I are in the middle of.
Fingers crossed it's a one time fix and this doesn't come back.
Thank you all again again for an amazing project!
Same. Updated to version v2.15.0. It was not before. I am not aware any changes that I made. Redownload of the audiobook did not helped it.
@Pwnz74 commented on GitHub (Nov 1, 2024):
Same. Updated to version v2.15.0. It was not before. I am not aware any changes that I made. Redownload of the audiobook did not helped it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ljlongwing on GitHub (Sep 13, 2024).
What was the Problem?
I log onto my server and always download the books locally while listening so that I'm not reliant on connection to the server, the download typically works well. But recently I've been getting red ! marks on the image, with a note that states "Media is linked to this server but was downloaded by a different user. Progress will only be synced to the user that downloaded it." I only connect with one user, so it's entirely not possible to be a different user
Steps to Reproduce the Issue
I'm not getting this all the time, but frequent, so I'm not sure about reproduction steps
What was Expected?
it would be nice if it recognized that I'm me and I'm the one that downloaded the book
Phone Model
Samsung Galaxy S22+
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
No response
@nichwall commented on GitHub (Sep 13, 2024):
There have been a few reports of this in Discord. Did you update your server after downloading the books?
Does resetting the app data and logging back in to the server fix it?
@ljlongwing commented on GitHub (Sep 13, 2024):
Yes, I keep my server updated, and this happens regularly, while I might have the books on my phone for awhile, so it's entirely probable that the server has been upgraded between downloads.
So, resetting the app caused it to not know about my downloads folder, which of course made it not know the book was already downloaded....re-adding my download folder doesn't seem to have made it aware that the book was already in the folder either....thus, the only option I saw, was to tell the client to again download the file....which of course puts the client and the server on the same note regarding who downloaded it....so, while this 'fixed' the issue with this book, I have several other books already downloaded as well, which my client no longer recognizes as downloaded....so....I don't feel this 'reset the client' thing is a fix for the problem....just causing more issues
@advplyr commented on GitHub (Sep 16, 2024):
I don't see how this could happen. We'll first need to be able to reproduce the issue so if you can figure out a way to reproduce it that would be helpful
@brand421 commented on GitHub (Sep 28, 2024):
I'm having this issue as well. Media was downloaded on the same network as the server, with the same user being logged into the app the whole time. Most recent version is installed on both phone and server.
@floatiepen commented on GitHub (Oct 1, 2024):
I'm also getting this message
@jsk01 commented on GitHub (Oct 11, 2024):
Same after upgrading server to latest version.
@jnsimon commented on GitHub (Oct 17, 2024):
I was seeing this as well with version 2.15.0 of the server and v0.9.76-beta of the android app. I force stopped the app and cleared the app storage. Logging back in to everything seems to have made the error go away.
@meyeaard commented on GitHub (Oct 30, 2024):
First off, awesome work on this project, this is one of my most used apps and it's more polished than some commercial options.
I've been having this issue for some time now over multiple updates to the droid app and server. I've been making due, just dropped over to check on possible fixes after another server update hadn't fixed it.
I killed and cleared storage as @jnsimon commented, and for now it seems to work (only been 10 minutes or so really). But honestly it's not a fix I would want to tell my mom or wife they'd have to do as it does delete all client side data - and even through the audiobook files are in a separate folder it won't detect the media is already downloaded so I had to manually clean and re-download all the books my kids are I are in the middle of.
Fingers crossed it's a one time fix and this doesn't come back.
Thank you all again again for an amazing project!
@neingeist commented on GitHub (Nov 1, 2024):
I also encountered this (Pixel 8 on Android 14)
@Pwnz74 commented on GitHub (Nov 1, 2024):
Same. Updated to version v2.15.0. It was not before. I am not aware any changes that I made. Redownload of the audiobook did not helped it.