@advplyr commented on GitHub (Nov 5, 2024):
I thought with the db migration users had to set up a new connection and we went through that process of asking users to set up a new connection
@nichwall commented on GitHub (Nov 5, 2024):
I think a number of people just didn't do it because we added the "old user ID check" to the app, so yes a lot of people signed out/in, but other…
@mikiher commented on GitHub (Nov 5, 2024):
OK, so can we just state here clearly what are the resolution steps, based on the discussion above, for the benefit of the bug's reporters?
@mikiher commented on GitHub (Nov 5, 2024):
The server still allows connecting with old user ids.
Is there a good reason for allowing that after v2.13.0?
@advplyr commented on GitHub (Nov 5, 2024):
I'm hoping to push the mobile app release this afternoon. Maybe I can see about adding in a message notifying users with old IDs to set up a new…
@Pwnz74 commented on GitHub (Nov 28, 2024):
I got server version: 2.17 redownload did not worked for me after removal of local item. It did not even work on 2.16. Use using root both App and server.
@nichwall commented on GitHub (Nov 28, 2024):
I got server version: 2.17 redownload did not worked for me after removal of local item. It did not even work on 2.16. Use using root both App…
@vb0 commented on GitHub (Nov 4, 2024):
I have just one account overall, that is also "Account Type: root". (also I had only one user, and the same, ever since I installed it -early 2023- BTW…
@nichwall commented on GitHub (Nov 4, 2024):
Some discussion over here as well https://github.com/advplyr/audiobookshelf-app/issues/1320
Do you know when the last time you signed in to the…
@vb0 commented on GitHub (Nov 4, 2024):
Good idea, I actually logged in again not a long time ago (this issue was there both before and after), but I didn't reinstall/wipe storage for the app.…
@mikiher commented on GitHub (Nov 5, 2024):
OK, here's my analysis of what's happening:
The book was downloaded to local storage with an oldUserId (probably a long time ago?). The oldUserId…
@mikiher commented on GitHub (Nov 5, 2024):
So for those who want a quick resolution without the technical details:
After upgrading to server release > v2.13.0, delete the book from local…
@advplyr commented on GitHub (Nov 5, 2024):
Ah yeah I removed the old user id in v2.13.0. It's been almost 18 months since we stopped using the old user id and I didn't think about old downloads. …
@nichwall commented on GitHub (Nov 5, 2024):
I think the distinction is how the user signs in as well, because there have been a few people who have mentioned "redownloading did not fix it", but…
@advplyr commented on GitHub (Nov 5, 2024):
You're right, that is a bit more problematic. The saved connection on the device also stores the user id which could be an old user id if set up before…
@nichwall commented on GitHub (Nov 5, 2024):
The steps I have told people to do (in several GH issues and on Discord since it happened originally with the database migration, and some in more…
@FreedomBen commented on GitHub (Oct 18, 2024):
Ok, confirmed that the bug was introduced in 2.13.0. It is not present in 2.12.3.
And damn, there's a lot of changes between the two... I'll…
@mikiher commented on GitHub (Nov 4, 2024):
There were certainly many changes around the user model in 2.13.0.
Are you still observing the issue with the latest server version (2.16.2)? Also,…
@vb0 commented on GitHub (Nov 4, 2024):
This bug is happening to me since a while too. Can reproduce on the latest server and app, at least as far as they get automatically updated: 2.16.2 with…
@mikiher commented on GitHub (Nov 4, 2024):
Thanks for the details. And are you logged in as root or some other user?