Secure PDF Viewer app version 32 released

GrapheneOS

Secure PDF Viewer app version 32 released:

https://github.com/GrapheneOS/PdfViewer/releases/tag/32

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.

ItsHarper

GrapheneOS Oh thank god, this sounds amazing. Not having swiping was very unfortunate.

koocmit

GrapheneOS Thank you for the update. Hopefully search is the next frontier to be explored.

heykanspor

Thanks for the update!

It would be nice if zooming out stopped at the original page size.

Zooming in to see details should work normally, but when zooming back out the page should only return to the size it had when the PDF was opened. It should not become smaller than the screen with empty space around it.

ItsHarper

Swiping does indeed work nicely 💛

dracula

Thank you for the swiping page change. Huge improvement.

Byku

replace jump-to-page dialog to use simple text input

YEEEEEEESSS!!!

Misanthropic1

When can we expect the update to show up in the GOS app store? I know I can install it from GitHub, but I like using the app store for system app update.

Novaliss

Misanthropic1 it is already in the AppStore app. You need to change the 'Release channel' for the desired app to 'Beta', or 'Alpha'.

spring-onion

Misanthropic1 The apps also have their own release channels. You can change it per app in the app store, tap on the one you're after then tap on the 3 dots at the top right. It's currently in the beta channel.

Novaliss

Misanthropic1 can install it from GitHub

No, since it comes with the OS it must be updated by App Store.

federigo

On one of my phone I don't have GrapheneOS, but I use Secure PDF Viewer via Google Play store. I received this update (v. 32), but I also had an update a few days before. Even thou I realise the last update was pushed a year ago. Can someone confirm that it was legit? Was there an update just before this one? Maybe recompiled targeting a different Sdk? I recevied the v32 update yesterday and the other one should have been around the 7th or 8th of July.

Novaliss

federigo you mean this one? https://imgur.com/a/KujfSEX

It is legit, and can be installed on most Android phones. And like you see in the picture, even be installed in parallel with the built-in on a GrapheneOS device.

GrapheneOS

federigo federigo Play Store releases of our apps use the standard approach with app bundles and Play Signing which is the only choice for a newly updated app and strongly pushed by Google for existing apps. Google Play Store generates and signs the APKs. They use split APKs and/or specialized APKs for devices which can be changed over time if they optimize it more. If you want to get the APKs generated and signed by us then you should install it via our App Store instead.

federigo

Novaliss

Thanks for the reply. No, what I meant is that I had SPDFViewer installed via GPS on this non-GrapheneOS mobile phone. It received 2 updates: one was v31 (but I already had v31, hence my question), and one is the latest v32.

I was wondering if before v32 a v31 with a different internal version was pushed to (or by) the GPS. Sometimes it happens if a different SDK version is targeted, but I wanted to make sure. Looking at the changelog the only release I should have gotten on that phone would be v32 and not another v31 intermediate version.

federigo

GrapheneOS Thanks for the reply. On this particular phone I unfortunately have to stick to the GPS version.

What are you saying is that even thou no v31.something was released at the time, probabily the GPS own optimization generated a new APK and pushed to the device indipendent on you releasing a new version?
And it's just a coincidence that this happened a few days before v32 was pushed.

Am I understanding this right?

Thanks.

GrapheneOS

federigo federigo It's likely from them optimizing APKs to reduce storage usage. It would be nearly impossible for them to update Java/Kotlin dependencies due to how apps are compiled and it could introduce major bugs to apps even if they only did it for bug fix releases. It's highly unlikely that they'd ever attempt to update libraries in apps. They do detect outdated libraries in rare cases and warn developers about it but they don't normally do it even for important library security updates, only in rare cases.

federigo

I also found that these kind of updates could be triggered by Google updating the Android Support Libraries. Could be it?

federigo

GrapheneOS Thanks again. So, the bottomline is: if I trust Google, the update I received should be ok. i.e. you consider "normal" the possibility that even thou you didn't release any new version, there could be an updated apk in the Google Play Store from time to time. Correct? I shouldn't be worried if this happens: it's normal procedure for apps using Google Play App Signing (with the actual apk signature managed by Google).

Again, the premise is that I trust Google on this specific device.

GrapheneOS

federigo It's normal and doesn't indicate anything concerning. We also use their feature based on app bundles to ship a tiny split APK they generate which notify users an update is available. We only use it because the Play Store is so bad at shipping people the app updates or notifying them without it. It's likely partly due to people disabling app updates and then not noticing them for a long time, if at all. We didn't use this for version 31 until today though so that wasn't the cause of the app update you got to 31.

TheFlap

Amazing! Now a feature to get the topbar to the bottom of the screen and making zooming out stop at the original size, then it's basically the perfect PDF Reader.