Issues with your latest APK

[IzzySoft]

The updater at the IzzyOnDroid repo just reported multiple issues when pulling in your latest APK:

! repo/com.prostudio.urltopdfconverter_3.apk declares sensitive permission(s): android.permission.READ_EXTERNAL_STORAGE android.permission.MANAGE_EXTERNAL_STORAGE
! repo/com.prostudio.urltopdfconverter_3.apk: debuggable or testOnly set in AndroidManifest.xml
! com.prostudio.urltopdfconverter_3.apk (com.tawhid.webcapture) has no metadata!

OK, the last one means you've changed the packageName. That means it is an entirely new app, and direct updates to this version are not possible.

The first one means we'd have to add the mentioned permissions (with a short description what they are needed for) to your app's "green list" as otherwise they'd be shown as "warnings".

The one in the middle is the biggest problem here: apps for distribution must have NEITHER of the two set. Wondering how those come in, problem number 4 shows up:

Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
Signer #1 certificate SHA-256 digest: b411f6432b53509f36236b18bee35e5d81de6b6ec5db4f0061f5ee9fe4875259
Signer #1 certificate SHA-1 digest: e134beef19d6f5ea9d6a6ca6010641ace8c03eb6
Signer #1 certificate MD5 digest: 0e102ad1d91636119597a960d87b49a2
Signer #1 key algorithm: RSA
Signer #1 key size (bits): 2048

The APK is signed using a debug key. That's not intended for distribution; please always sign release APKs with a release key!

As for the IzzyOnDroid repo, there's a 5th problem now: APK size increased by almost factor 10 from less than 5 MB to almost 40 MB (per-app size limit here is 30 MB). What happened there? For one, compared with the previous release, I see a load of native library directories, each containing about 5 MB for pdfdium. For 6 architectures. Are there really any Android devices running on MIPS? Even x86 is rather rare (or almost non-existent, if we ignore emulators for a little). 2 armeabi dirs (armeabi, armeabi-v7a)? Any devices for the former? All those *.so files are stored uncompressed inside the APK, so each dropped unnecessary ABI would mean 5+ MB saved. An APK with just the 2 ARM ABIs would probably be around 15 MB. Per-ABI APKs most likely around 10 MB each or less.

Can we get those issues solved? Thanks in advance!