Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-17817

Android: Google libraries should always be up to date in Titanium and modules

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: None
    • Resolution: Cannot Reproduce
    • Affects Version/s: Release 3.4.0, Release 3.5.0
    • Fix Version/s: None
    • Component/s: Android
    • Environment:

      SDK 3.5.0, ti.map 2.1.4

      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.

        Attachments

          Activity

            People

            • Assignee:
              emerriman Eric Merriman
              Reporter:
              mokesmokes Mark Mokryn
            • Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Integration