-
Notifications
You must be signed in to change notification settings - Fork 31
Which version of appcompat-v7 is used? #2
Comments
I can confirm, forcing v7:21.0.0 produces a working build. I will disable the fdroid build, and re-enable it tomorrow with the fixes applied, but it should be fixed at your end for the next version. |
I was looking into the issue, and yes, my AndroidStudio+Gradle are using 21.0.3. |
If I set the "targetSdkVersion" to 21 (it was 22) and force the version of "com.android.support:appcompat-v7" to 21.+ , is it OK for you ? The current files (so the flym files) are using the appcompatv7 from the repository "jcenter/bintray" ( https://bintray.com/lukar1203/maven/appcompat-v7/view) which is in v21.0.3 . |
The targetSdk shouldn't matter at all, but you can set it to 21 if you think that is more appropriated. Setting the appcompat-v7 to an actual version (or 21.+) will fix the issue. The repo you mentioned is a personal repo at bintray, it's not jcenter. jcenter is hosted on bintray, but not every repo at bintray is part of jcenter :). However, we at fdroid strip such thirdparty repositories and build the libraries hosted there from source. Appcompat is comming from the android support-repo (a local maven repository installed and managed by the android sdk). |
Force the appcompat-v7 library to version 21.*
Should be fixed, as in the build.gradle , the appcompat-v7 version is set to 21.+ |
Indeed, builds fine. Thanks for the quick response. |
Could you provide actual version details of the used appcompat-v7 version? You currently use
compile 'com.android.support:appcompat-v7:+'
which should get the newest version available. This breaks reproducible builds (since building at different times will use different versions) as well as normal builds if you depend on a specific feature. E.g. if the build host does not server the latest appcompat version you require, it still builds without errors, but might fail on run. Also if Google yet again decides to push incompatible (beta) updates, which was done in the preface of android-L, this might be a problem as well.The reason I am asking, because fdorid build crashes with
StackOverflow gives this solutions: https://stackoverflow.com/questions/29790070/upgraded-to-appcompat-v22-1-0-and-now-getting-illegalargumentexception-appcompa and https://stackoverflow.com/questions/29784124/java-lang-illegalargumentexception-appcompat-does-not-support-the-current-theme
The text was updated successfully, but these errors were encountered: