Following up on my own post, the test I ran was not thorough enough,
and the following rules are the ones actually required to make WebView
callbacks work properly:
--
-keep public class com.trans_code.android.JavascriptCallback
-keep public class * implements
I've recently started using the WebView Android / Javascript interface
in my projects (and I think it's pretty cool; article here:
http://developer.android.com/resources/articles/using-webviews.html).
The problem is that when obfuscation is turned on, the callbacks from
Javascript to my Android
On Sun, Nov 7, 2010 at 10:41 PM, Stephen Jungels sjung...@gmail.com wrote:
I've recently started using the WebView Android / Javascript interface
in my projects (and I think it's pretty cool; article here:
http://developer.android.com/resources/articles/using-webviews.html).
The problem is
Thanks, I followed up on that idea by creating a placeholder
interface; I am limiting this to the problem of WebView callbacks so I
call it JavascriptCallback.
If I follow the convention of implementing this interface wherever
appropriate, the following Proguard rules work:
-
4 matches
Mail list logo
