Android Question List of pitfalls for obfuscated compilation?

[wimpie3]

My code works fine in debug and release mode. However, I get tons of errors in obfuscation mode (the errors occur while running the app). Is there a list of potential pitfalls? Things to check?

 

[Erel]

Yes. See the pitfalls section in the tutorial: http://www.b4x.com/android/forum/pages/results/?query=obfuscation+pitfalls&page=1&prefix=0

 

[thedesolatesoul]

AFAIK there is only one pitfall.
All subs that are called by callsub need to have an _ in them. Otherwise the call to
CallSub("Hello") will be not work.

 

[wimpie3]

OK, and what about CallSubDelayed? What about the reflection library?

And what about this: CallSub(variablename+"_underscore")?

 

[Erel]

Not exactly. The compiler will recognize CallSub / CallSubDelayed where the subs are constant (not variables).

CallSub(Me, "Hello") 'will work with obfuscation
CallSub(Me, SomeVar) 'will not work if the sub doesn't include an underscore

 

[wimpie3]

Seems there are issues with the reflector library as well in obfuscation mode:

Dim reflect As Reflector
reflect.Target = lbl
reflect.SetOnTouchListener("dayTouch")

When I touch the label, I get an error in the console window: "raiseEvent for daytouch returned null"

 

[wimpie3]

Ok, problem solved. When renaming the sub to "day_Touch", everything worked fine. So Erel, this might be a bug... subs in SetOnTouchListener definitely need an underscore.

 

[Erel]

This is not a bug. The compiler cannot know in this case that a sub named "dayTouch" should not be obfuscated.

 

[wimpie3]

OK, but if you "autocorrect" this problem in this case:

CallSub(Me, "Hello")

why not do the same for

SetOnTouchListener("dayTouch")

 

[Erel]

CallSub and CallSubDelayed are internal keywords. Reflector.SetOnTouchListener is not. The best solution would have been for reflector to use the convention used by events which is to add the event suffix to the "event name" parameter (with an underscore between).