I updated the build from Phonegap (Cordova) from 2.0 to 2.4, and everything worked fine in dev until I started testing the latest apk version. What I find after a lot of time wasted is that for some reason now when I run the build my proguard configuration disrupts the telephone assembly in some way, which means that when it starts, deviceready is never called. There seems to be no errors when creating, starting, and nothing as far as I can see it, but I assume that something is quietly failing in the js cord, since I am not getting compilation / log errors on the device.
As I said, this is ONLY when starting obfs Proguard during the build process. If I turn off Proguard everything works fine. I returned all my code back to 2.0 to be sure, and all this is good, so somewhere along the way there was a normal change that apparently has not been documented / or no one else hit (2.4 just came out a few weeks ago - at the time of writing February 26th, 2013).
My Proguard configuration contains the following data for the telephone plug (as well as some other standard configuration)
-keep public class * extends com.phonegap.api.Plugin -keep public class * extends org.apache.cordova.api.Plugin -keep public class org.apache.cordova.DroidGap -keep public class org.apache.cordova.** -keep public class org.apache.** -dontwarn android.webkit.* -dontwarn org.apache.**
and dex decompilation does not seem to throw any light - everything looks fine at first sight ...
Does anyone have any idea???
phil.fuse
source share