[TIMOB-17817] Android: Google libraries should always be up to date in Titanium and modules
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | None |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2016-09-25T18:39:23.000+0000 |
Affected Version/s | Release 3.4.0, Release 3.5.0 |
Fix Version/s | n/a |
Components | Android |
Labels | TCSupport, android, googleplay, module |
Reporter | Mark Mokryn |
Assignee | Eric Merriman |
Created | 2014-09-30T16:35:13.000+0000 |
Updated | 2017-03-27T20:44:14.000+0000 |
Description
The version of the Google Play Services becomes an issue when there are two modules using them. For example - I'm developing a Chromecast module which must use a recent version of this library, in a project that also uses the ti.map module. The project will not build if there are two different versions of Google Play Services, thus in any case I overwrite the version in ti.map with the newest copy.
This is also true of other libraries, such as the Android support libraries. A project will not build if there are two different versions of the library in modules, Titanium, etc.
Thus, Titanium and its modules should always have the latest version of the relevant libraries - good practice in any case due to bug fixes, etc.
Relevant cases:
https://github.com/appcelerator/titanium_mobile/pull/6022
https://github.com/appcelerator-modules/ti.map/issues/59
In most cases all that is needed is just replacing the file with the new version.
Yes please! Many modules share the same problem.
Current versions of ti.map include a newer version of the play-services. Resolving for now.
Closing ticket as the issue cannot be reproduced.