[codenameone-discussions] Re: Cannot install new build on older Android device

2016-06-20 Thread Shai Almog
We have a fix for that build error which will be a part of the next update. Notice that with the new Google play support you can include only location support without including the ads support which is exactly why we deprecated the global sweeping build switch. See

[codenameone-discussions] Re: Cannot install new build on older Android device

2016-06-20 Thread mcw
Another suggestion in the referenced article was to build with android gradle=false but that generated a build error. I built with android.grade=false and android.includeGPlayServices=false -compile: [javac] Compiling 536 source files to /tmp/build7034578418479870721xxx/AWMain/bin/classes

[codenameone-discussions] Re: Cannot install new build on older Android device

2016-06-20 Thread mcw
The referenced article says: We transitioned the Google Play Services support to be on by default as that is the common use case and makes API's like the location API far more usable. As a result 2.3.1 became the minimum OS version as imposed by Google. This device is running 2.3.5 so it

[codenameone-discussions] Re: Cannot install new build on older Android device

2016-06-19 Thread mcw
I went back through previous versions of CodenameOne version by version. When I got back to version 3.1 I was able to install the build on my Android 2.3.5 device. Unfortunately along the way I had to comment out a new CodenameOne API calls I was using, so this is not really a solution for me.