-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cordova build fails due to "com.android.support:support-v4" version #207
Comments
Same here. Simply adding the plugin in my ionic project without even importing nor using it.
I ran
|
Use this cordova plugin to fix this problem
|
I don't know what happened but i managed to build even though i didn't touch my project. I think this is some kind of compatibility-issue and not a real bug - i'm happily using the plugin without any error now! |
@roby65 That only solves half of the issue. Using that plugin keep crashes the app on launch. Only way to get it working is running via Android Studio. Proper way to solve this is seen on this answer on stack. Create a
|
I tried every suggestion to fix this but in the end simply updating ionic and cordova fixed it: You might also need to remove and add the Android platform again: |
cordova-android-support-gradle-release and build-extras.gradle conflicts with other plugins. Better not install this plugin. |
version 2.1.0 should now resolve this issue as you can optionally set a compatible android_support_version at installation time, e.g. |
Cordova build fails with exception:
:processDebugResourcesERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontVariationSettings ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:ttcIndex
This can be fixed in plugin.xml by upgrading
<framework src="com.android.support:support-v4:+" />
to a higher version like 27.0.1 or downgrading to 23.+.
Examples (tested):
<framework src="com.android.support:support-v4:27.0.1" />
or
<framework src="com.android.support:support-v4:23.+" />
The text was updated successfully, but these errors were encountered: