On either Thursday February 6th or Friday February 7th iOS version 2025.1.3 was released in the Apple apps store.
It wasn’t until this morning on Monday February 10th that the releases section in GitHub was updated with version 2025.1.3.
Why was there such a delay from when it was available in the App Store to when you as Bitwarden updated GitHub?
The same thing happened on Android with the authenticator app (2025.1.0) - that update came via Google PlayStore on Feb 10, but the last release on GitHub is still 2024.12.0 (last checked on Feb 11).
Though, the password manager app version 2025.1.2 (Android) was released on GitHub today, and didn’t arrive on the PlayStore for me yet. (PS: arrived now in the PlayStore…)
Seems like the mobile apps (always? sometimes?) get sent to the stores first - and that’s different with the browser extensions, where always the GitHub release is first.
PS: I added the version numbers and corrected some inaccuracies…
Then, you can’t count on the latest app store’s version being the same as the same version on GH, do you think?
You would think that the workflow would be that once the mobile app passes all validations after being compiled it would be pushed to the GitHub releases section as well as their respective App Store.
For mobile: not always, as it seems… Though I think, when something arrives on the mobile platforms, it usually doesn’t take that long until it “get’s official” on GitHub as well. 
(PS: Here again: I added the version numbers and corrected some inaccuracies in my previous post…)
GitHub is supposed to be the one place of truth for the apps. So logically speaking, the release should hit GitHub first in the workflow then the mobile app stores for review.
Unless Bitwarden purposely did the opposite because they didn’t want people getting notifications for GitHub saying there is a new release but the mobile app stores hadn’t approved them yet and people saying why does one say there’s a new version while the other doesn’t.
But in the end, you are always going to have a discrepancy between the GitHub and the app stores for a couple hours to a couple days.To me, it logically makes sense to have GitHub updated first and then the app stores.
Sidenote: I added “and Android” to the title.
Generally, I think people who look at GH often say this, so it wouldn’t be surprising if this is one of the goals.
I suppose if you use GH Actions to build your products, hold the final products, and then publish them on GH/push each for review in the stores (somewhat inconsistently?), you might get the results that we see. Some stores get the same packages/binaries, and inconsistent publication dates.