Originally created by @gh0sti on GitHub (Feb 1, 2023).
I'd figure you would want to keep the version number updates and consistent throughout the app. I'm on 0.9.61 and the app settings says the previous build.
Audiobookshelf Version: 0.9.61
Android App?
iOS App?
iOS Issue
iOS Version: 16.3
iPhone model:13 Pro Max
Originally created by @gh0sti on GitHub (Feb 1, 2023).

I'd figure you would want to keep the version number updates and consistent throughout the app. I'm on 0.9.61 and the app settings says the previous build.
Audiobookshelf Version: 0.9.61
- [ ] Android App?
- [x] iOS App?
#### iOS Issue
iOS Version: 16.3
iPhone model:13 Pro Max
adam
added the bug label 2026-04-24 23:21:15 +02:00
I wonder if it's easier to make version number a variable that can be updated and a string calls out for that variable throughout the app where you want version numbers to be shown. Would that make it easier to keep the version number consistant throughout the app?
@gh0sti commented on GitHub (Feb 1, 2023):
I wonder if it's easier to make version number a variable that can be updated and a string calls out for that variable throughout the app where you want version numbers to be shown. Would that make it easier to keep the version number consistant throughout the app?
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 @gh0sti on GitHub (Feb 1, 2023).
I'd figure you would want to keep the version number updates and consistent throughout the app. I'm on 0.9.61 and the app settings says the previous build.
Audiobookshelf Version: 0.9.61
iOS Issue
iOS Version: 16.3
iPhone model:13 Pro Max
@gh0sti commented on GitHub (Feb 1, 2023):
I wonder if it's easier to make version number a variable that can be updated and a string calls out for that variable throughout the app where you want version numbers to be shown. Would that make it easier to keep the version number consistant throughout the app?
@advplyr commented on GitHub (Feb 1, 2023):
Yeah I just forgot to re-generate the frontend after updating the version number.
@advplyr commented on GitHub (Feb 23, 2023):
Fixed in v0.9.62-beta