I've taken the liberty to update the android version of the module to use Google Play Services 7.8 and Ti SDK 4.1.0.
I gave it a new version number for android: 3.2.0.
This was important to me, because we use ti.dfp for serving ads via Doubleclick for Publishers. We need MRAID 2 compatibility, which requires Google Play Services 7.8. If multiple modules in a project use Google Play Services, they all have to be on the same version.
It is possible to hack around this by manually copying the desired version of the google-play-services.jar file into the modules that use other versions (and in fact I have to do that for ti.map and ti.cloudpush). My hope is that if we can get some of the most popular modules that use Google Play Services onto the same version of Google Play Services, it might make development of android apps a little easier.
I've taken the liberty to update the android version of the module to use Google Play Services 7.8 and Ti SDK 4.1.0.
I gave it a new version number for android: 3.2.0.
This was important to me, because we use ti.dfp for serving ads via Doubleclick for Publishers. We need MRAID 2 compatibility, which requires Google Play Services 7.8. If multiple modules in a project use Google Play Services, they all have to be on the same version.
It is possible to hack around this by manually copying the desired version of the google-play-services.jar file into the modules that use other versions (and in fact I have to do that for ti.map and ti.cloudpush). My hope is that if we can get some of the most popular modules that use Google Play Services onto the same version of Google Play Services, it might make development of android apps a little easier.