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

CLI: Module build should error if the apiversion in manifest does not match the SDKs apiversion


    • Type: Improvement
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: Release 6.0.0, Release 5.5.0
    • Fix Version/s: Release 7.0.0
    • Component/s: Tooling
    • Environment:

      OS: Microsoft Windows 10 Pro 10.0.14393
      Appc core: 6.0.0-57
      Appc NPM: 4.2.8-7
      Ti SDK: 6.0.0.v20160929001638
      Appc Studio:

    • Sprint:
      2017 Sprint 24 SDK



      When building a module if the apiversion in the manifest does not match the platforms apiversion in the SDK then the module build should fail. Currently if the apiversion is different then the build will take place and the user will produce a module that is not considered to be valid for the SDK it is build against. For example.

      • Developer rebuilds Android module for 6.0.0, forgetting to bump apiversion
      • User of module downloads the new module, and tries to build
      • Build fails as the apiversion does not match
      Steps to reproduce
      1. Create a module using ti create -p windows --type module --name mymodule --id com.my.mod
      2. Change the maifest apiversion to 2
      3. Build for Windows using 6.X SDK
      Actual result

      Build takes place despite the differing apiversions between SDK and module

      Expected result

      Build should fail as the apiversions are different


          Issue Links



              • Assignee:
                eharris Ewan Harris
                eharris Ewan Harris
                Kota Iguchi (Inactive)
              • Watchers:
                3 Start watching this issue


                • Created:

                  Backbone Issue Sync

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

                    Git Integration