MAF: Be careful how you build your APK

So that has been a while.... 1 year and 1 day to be exact.
Today I encountered a really weird issue in MAF. Yes, we are still using that in some projects. We are using 2.4.1 to build an app for a company that needs offline storage and sync. As MAF has this incorporated in the framework, and the customer has lots of ADF developers, the choice for MAF was made.

Anyway, back to the issue.

I was building a new feature and was heavily debugging the app. Next I committed my changes to GIT and pushed them to our GIT server. My stuff was working great :-)
Couple of hours later I was getting complaints that people were not able to run the app that was built from the latest version in GIT....

The app started, but hung on the splash screen..... It took me a while to figure out what was happening, and only after analysing the log very carefully I found a possible cause.

So I figured that the Debug mode could be the cause of the app hanging. I checked my file, and there it was : java.debug.enabled=true

So I changed that to false.

Rebuilt the apk, and the app was running just fine.

So whats the lesson learned: Do not build your app with ava.debug.enabled=true (at least not for Android. I did not try iOS or Windows)

Back soon.


Popular posts from this blog

ADF 12.1.3 : Implementing Default Table Filter Values

ADF 12.2.x : Conditional Showing Message Instead of List of Values Popup

ADF 11g Quicky 3 : Adding Error, Info and Warning messages