Proguard Parser Exception <mapbox-android-plugin-locationlayer>

[Chrylo]

When using the following setup and integrating the dependency com.mapbox.mapboxsdk:mapbox-android-plugin-locationlayer:0.5.3, I always get the following error:

ProGuard configuration parser error: \.gradle\caches\transforms-1\files-1.1\mapbox-android-plugin-locationlayer-0.5.3.aar\bff82016c498500d5e92322d3f3579a3\proguard.txt line 11:21 no viable alternative at input ','

When looking into the proguard file, 11:21 stands out:

-keepclassmembernames,allowobfuscation interface *

buildTypes {
        release {
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        debug {
            minifyEnabled true
            useProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
            applicationIdSuffix '.debug'
        }
    }

[cammace]

Could you provide your projects ProGuard configuration, perhaps there's a merging conflict? The line it's referring to is an exact copy of the Retrofit team's README file and our continuous integration runs a check to ensure no basic issues occur such as the one you describe above.

mapbox-plugins-android/circle.yml

Lines 43 to 45 in 9c208bd

	- run:
	name: Build release to test ProGuard rules
	command: ./gradlew app:assembleRelease

[Chrylo]

Hey again, with proguard enabled (debug mode) I can succesfully build the app. It seems that minifyEnabled = true without proguard being enabled does not support allowobfuscation or includedescriptorclasses .

See the following realm issue. So the Realm team had the same issue. Their solution was to remove the not supported keywords for build in shrinking. Could you consider, doing the same? :)

To answer your question anyway. You can reproduce it with an empty (defualt) proguard file + my debug configuration. See Google Documentation.

Thank you!

[cammace]

Awesome @Chrylo, thanks for looking into the issue and finding the same problem Realm was having. I opened #549 to remove the option.