printpagestopdf / cb_app

printpagestopdf

This Project contains the necessary source for the Firefox AddOn "Print pages to Pdf". Because of strange differences with one guy from the Mozilla (AMO) Team new releases and Bugfixes of the AddOn couldn't be released.

This AddOn Version (0.5.0.5) was working fine up to Firefox Version 44.* and stopped working from FF 45 on.

Everybody who wants to go with Mozilla AMO Team to fix the problem for FF 45 and release the Addon feel free to use and change this source

The Addon is using the (modified) open Source library wkhtmltopdf that is based on QT 4.85

Directories:

printpagestopdf - The source of the Firefox Addon including a binary version of wkhtmltopdf DLL (wkhtmltox0.dll)

wkhtmltopdf_012_mod - The modifications of wkhtmltopdf.dll Version 12 (see project how to build)

qt_48_mod - The modifications of QT 4.85 to build the modified wkhtmltopdf0.dll above

Not longer available

cb_app's Issues

Proprietary dependency: GMS

I've just performed a scan on your APK as you've opened an inclusion request with F-Droid. Looks there's a little show-stopper here. This is what the scanner results look like:

Libraries detected:
-------------------
* Android PackageManager (/android/content/pm): Utility, Apache-2.0
* Android Support v4 (/android/support/v4): Development Framework, Apache-2.0
* AndroidX Activity (/androidx/activity): Utility, Apache-2.0
* Android Jetpack Annotations (/androidx/annotation): Utility, Apache-2.0
* Browser (/androidx/browser): Utility, Apache-2.0
* Androidx Core (/androidx/core): Utility, Apache-2.0
* AndroidX Fragment (/androidx/fragment): UI Component, Apache-2.0
* Lifecycle (/androidx/lifecycle): Utility, Apache-2.0
* Loader (/androidx/loader): Utility, Apache-2.0
* Android Activity Saved State (/androidx/savedstate): Utility, Apache-2.0
* AndroidX Security (/androidx/security): Utility, Apache-2.0
* Android Jetpack VersionedParcelable (/androidx/versionedparcelable): Utility, Apache-2.0
* Jetpack WindowManager Library (/androidx/window): Utility, Apache-2.0
* Flutter Geolocator Plugin (/com/baseflow/geolocator): Utility, MIT
* Google Mobile Services (/com/google/android/gms): Development Framework, Proprietary; NonFreeComp
* Tink (/com/google/crypto/tink): Utility, Apache-2.0
* Flutter (/io/flutter): Development Framework, BSD-3-Clause
* url_launcher (/io/flutter/plugins/urllauncher): Utility, BSD-3-Clause
* Kotlin (/kotlin): Utility, Apache-2.0
* kotlinx.coroutines (/kotlinx/coroutines): Utility, Apache-2.0

Offending libs:
---------------
* Google Mobile Services (/com/google/android/gms): NonFreeComp

1 offenders.

Dangerous flags:
----------------
* usesCleartextTraffic

Permissions:
------------
* android.permission.INTERNET
* android.permission.ACCESS_NETWORK_STATE
* android.permission.ACCESS_FINE_LOCATION
* android.permission.ACCESS_COARSE_LOCATION
* com.theripper.cb_app.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION

SigningBlock blobs:
-------------------
0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)

See the GMS (Google Mobile Services)? Those are a show-stopper for F-Droid. The most likely culprit having dragged that in: Flutter Geolocator Plugin. Some pointers for help can be found in the corresponding section of my snippet under Flutter and Geolocation.

Further, I see your app declares usesCleartextTraffic. Does it really rely on any unencrypted network connections (i.e. http:// instead of https://)? If not, you may want to remove that flag from your declaration in AndroidManifest.xml.

Oh, and if you wonder about that DEPENDENCY_INFO_BLOCK, that can be avoided with a small modification to your build.gradle:

android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs.
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles.
        includeInBundle = false
    }
}

For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains.