Proguard mess Javascript Interface functions when targeting SDK in Android Manifest above 17

Question

I have a custom Webview in my android project as shown below:

public class MyWebView extends WebView {

    public MyWebView(Context context) {
        super(context);
    }

   public class JsObject {

        @JavascriptInterface
        public void show() {
            //...
        }

        @JavascriptInterface
        public void hide() {
            //....
        }
}

that includes a JavascriptInterface which I use to communicate from the JavaScript side to the Android side.

In the AndroidManifest I had the following

<uses-sdk
    android:minSdkVersion="8"
    android:targetSdkVersion="16" />

In the project I used proguard which declared:

-keepattributes JavascriptInterface

-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

and everything was working fine.

However when i changed my AndroidManifest to android:targetSdkVersion=18 or 19 and test on devices with 18 and above, proguard seems to somehow mess the JavaScript methods which are not accessible anymore.

If I put back to 16 or anything less than 17 everything works fine. Additionally this happens only with proguard. If I don't use proguard everything works fine even with android:targetSdkVersion=18 or 19. Can anyone help to make it work when targeting in the manifest Android > 17?

The @JavascriptInterface was introduced in SDK level 17. You would receive compilation errors that the annotation cannot be resolved, and by removing it, Proguard would not locate any matches and remove all methods as well. Are you sure the last paragraph accurately describes your problem? — Paul Lammertsma
– Paul Lammertsma, Commented Jan 21, 2014 at 13:59
Paul thank you for your reply. Yes I am aware of the introduction of @JavascriptInterface in SDK level 17. I have been using that approach for months and everything was working fine. Only this change android:targetSdkVersion=18 or 19 in the manifest just mess with proguard and javascript interfaces on run time. Proguard compiles fine in all cases, no reported errors or warnings! — andreasv
– andreasv, Commented Jan 21, 2014 at 14:07
@andreasv I have this exact same problem with my javascript interface. The compiled app works fine on below api level 17 devices but not on jelly bean and above. Also I included appbrain sdk in my app and it also gives the warning to check proguard configs. It's as if javascript is off over whole application. Without proguard it works fine. I've spent my whole day and tried each and every solution suggessted on stackoverflow and none of them worked. Have you solved this issue? please help guys! — lightsaber
– lightsaber, Commented Mar 2, 2014 at 12:28
@andreasv I already have -keepattribues Annotation. But I found the solution, I am using some library which has methods which are not annotated with JavascriptInterface. So now the issue is solved. Thanks! — lightsaber
– lightsaber, Commented Mar 4, 2014 at 10:29

Community · Accepted Answer · 2017-05-23 10:29:14Z

19

I copy my answer from this topic for you: https://stackoverflow.com/a/19994873/1735499

And, if you are using Proguard, remember to add this

-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

-keepattributes JavascriptInterface
-keep public class com.mypackage.MyClass$MyJavaScriptInterface
-keep public class * implements com.mypackage.MyClass$MyJavaScriptInterface
-keepclassmembers class com.mypackage.MyClass$MyJavaScriptInterface { 
    <methods>; 
}

If it's still not OK, add this

-keepattributes *Annotation*

Note: your MyJavaScriptInterface must be Public class

Ref#: Android Proguard Javascript Interface Fail

Br,

Frank

edited May 23, 2017 at 10:29

CommunityBot

11 silver badge

answered Feb 11, 2014 at 4:15

Frank Nguyen

6,6633 gold badges41 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Heath Borders Over a year ago

You need -keepattributes *JavascriptInterface* if you're using obfuscation. proguard.sourceforge.net/manual/usage.html#obfuscationoptions

Alexandre G · Accepted Answer · 2015-05-21 02:17:16Z

6

These 4 lines are usually enough - and no need to make the interface public.

-keepattributes JavascriptInterface
-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

answered May 21, 2015 at 2:17

Alexandre G

1,7131 gold badge21 silver badges33 bronze badges

Comments

yrt · Accepted Answer · 2015-05-29 10:01:38Z

2

In my case, just :

-keepclassmembers class com.mypackage.MyJavaScriptInterface {
  public *;
}

-keepattributes *Annotation*

was enough !

answered May 29, 2015 at 10:01

yrt

211 bronze badge

1 Comment

Snainer Over a year ago

true ! no need nothing more, confirmed

Collectives™ on Stack Overflow

Proguard mess Javascript Interface functions when targeting SDK in Android Manifest above 17

3 Answers 3

1 Comment

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related