Closed adbenitez closed 4 weeks ago
So, this means that, since we're including the binary blob now, we just can't publish any more F-Droid versions until either:
good point, some of the jars have the .java files but others are compiled .class, so this is not the way to go to solve the problem with fdroid!?
we will have to go the migration route :(
implementation 'com.amulyakhare:com.amulyakhare.textdrawable:1.0.1'
with implementation 'com.github.amulyakhare:TextDrawable:558677ea31'
seems to work (i.e. getting it from JitPack.io instead of jcenter)mavenCentral()
to build.gradle, idk.
- with
implementation 'com.github.amulyakhare:TextDrawable:558677ea31'
seems to work (i.e. getting it from JitPack.io instead of jcenter)
this is a rather fragile solution, tried forking the repo and currently jitpack.io doesn't manage to build the repo anymore (see https://jitpack.io/#deltachat/TextDrawable) but for now we can go with that one until it breaks again, anyway I will keep the fork around in the org just in case it gets deleted etc.
To test the changes in this pull request, install this apk: 📦 app-preview.apk
@r10s did something to lower minSdk to 19, that is the minimum supported by com.journeyapps:zxing-android-embedded
cc @link2xt
To test the changes in this pull request, install this apk: 📦 app-preview.apk
close #1791
Migration plan:
com.google.android.exoplayer:exoplayer-core/ui
to recent versioncom.journeyapps:zxing-android-embedded
to more recent version ⚠️REQUIRES MinSdk 19+'mobi.upod:time-duration-picker
relinker
to avoidde.cketti.safecontentresolver:safe-content-resolver-v14
depending on old relinker version