Lots of changes version 1.4.2 build 50

[setherd]

Changelog: 1.4.2+46 → 1.4.2+50

• Added Microsoft OneDrive library support, including OAuth, folder browsing, sync, downloads, covers, token refresh, and iOS redirect setup.
• Added multi-filter browsing for Calibre libraries: users can combine up to five tag/author filters, plus series, language, format, search, and sort.
• Improved cover reliability with typed cover states, clearer placeholders, retry behavior, structured logs, and better Calibre Server has_cover handling.
• Bulk downloads now save covers best-effort without failing the ebook download if cover fetching fails.
• Fixed library setup failure handling so errors stop the spinner and surface to the user.
• Improved Dropbox first-setup behavior by forcing an initial sync after adding a Dropbox library.
• Improved Project Gutenberg diagnostics and error messaging for DNS/VPN/iCloud Private Relay/content-filter failures.
• Hardened Google Drive, Dropbox, and OneDrive auth errors with clearer messages for fast WebAuth failures.
• Improved download recovery: existing downloaded books can be rediscovered if the manifest is missing or still uses legacy keys.
• Added tests for download manifest recovery and legacy manifest migration.
• Upgraded Downloads screen with grid/list/compact views matching the main library view picker.
• Downloads now shows cached book covers in grid/list views and uses a compact letter avatar in compact view.
• Updated the in-app User Guide for OneDrive, WebDAV/Calibre Server, bulk-cover behavior, five-filter limit, and mobile export behavior.

[PeterT]

I'm curious as to why you love keeping the version number constant and just increasing a build number? I've not seen this practice on any other application.

[Incanus]

Hello:

The previously reported bug has been resolved.

After the app update, previously downloaded e-books appear so for the individual e-book view.

Much obliged,

[setherd]

Originally Posted by PeterT

I'm curious as to why you love keeping the version number constant and just increasing a build number? I've not seen this practice on any other application.

It annoys me as well. If I bump the version number, Apple takes three to four days to approve the release. But if I only change the build number, they approve it in a few minutes. I'm really hoping the next version will be the full normal release and I will bump the version number maybe to 1. 5 or something