Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-17817] Android: Google libraries should always be up to date in Titanium and modules

GitHub Issuen/a
TypeImprovement
PriorityNone
StatusClosed
ResolutionCannot Reproduce
Resolution Date2016-09-25T18:39:23.000+0000
Affected Version/sRelease 3.4.0, Release 3.5.0
Fix Version/sn/a
ComponentsAndroid
LabelsTCSupport, android, googleplay, module
ReporterMark Mokryn
AssigneeEric Merriman
Created2014-09-30T16:35:13.000+0000
Updated2017-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.

Comments

  1. Ivan Skugor 2014-10-02

    Yes please! Many modules share the same problem.
  2. Hans Knöchel 2016-09-25

    Current versions of ti.map include a newer version of the play-services. Resolving for now.
  3. Lee Morris 2017-03-27

    Closing ticket as the issue cannot be reproduced.

JSON Source