[TIMOB-25743] Windows: Auto-increment version numbering
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2018-02-22T22:36:26.000+0000 |
Affected Version/s | Release 7.0.0 |
Fix Version/s | Release 7.1.0 |
Components | Windows |
Labels | n/a |
Reporter | Kota Iguchi |
Assignee | Kota Iguchi |
Created | 2018-02-02T04:12:27.000+0000 |
Updated | 2018-05-16T23:37:55.000+0000 |
Description
We might want to introduce automatic-increment for build number during build due to deployment issues (See TIMOB-25616 and TIMOB-25017).
Here's some starting point to discuss:
- Do we accept the difference between version numbering in tiapp.xml and actual app? Note that Developers may want to determine specific version number for the release build.
- We could introduce special placeholder like
<version>1.0.*</version>
but this may cause breaking change and parity issue between platforms. Do we wan to do like this? Or we could just say "If you omit the build number, we just automatically increment it behind scenes, only on Windows platform".
- Do we accept this breaking change regarding new version numbering spec?
- Do we want to enable it by default? Otherwise do we want to introduce new property in tiapp.xml like <enable-auto-build-numvering/> or so
?
- Do we want to introduce this new version numbering spec for other platforms? Do we want to keep parity for it?
- Do we want to make it configurable from Appc Studio? For instance ["Automatically increment" checkbox in UWP packager](https://docs.microsoft.com/en-us/windows/uwp/packaging/images/packaging-screen5.jpg)
https://github.com/appcelerator/titanium_mobile_windows/pull/1177
Master and 7_1_X merged. test and other information can be found at: Master: https://github.com/appcelerator/titanium_mobile_windows/pull/1177 7_1_x: https://github.com/appcelerator/titanium_mobile_windows/pull/1199
Closing ticket; Verified fix in SDK Version: 7.1.0.v20180228160738 and SDK Version: 7.2.0.v20180301101144.
[~kiguchi] Customer update that, please check We've been testing the version auto-increment Appc just implemented for Windows and we noticed that an error is being thrown every time if we run a ti build. Sample project (which is really an empty app) Steps: 1) Compile and install app (ti build -p windows -T ws-local) 2) Wait for it to complete and the app to be launched. Then close it. 3) Run a ti clean 4) Compile and install the app again 5) Observe error [INFO] Project built successfully in 1m 5s 162ms [ERROR] Error: Failed to install app: Found bundle: C:\Users\karom\.titanium\vsbuild\BlankApp\win10.x86\AppPackages\BlankApp\BlankApp_1.16.10.1_Test\BlankApp_1.16.10.1_x86.appxbundle Installing app... Found dependency package(s): C:\Users\karom\.titanium\vsbuild\BlankApp\win10.x86\AppPackages\BlankApp\BlankApp_1.16.10.1_Test\Dependencies\x86\Microsoft.VCLibs.x86.14.00.appx C:\Users\karom\.titanium\vsbuild\BlankApp\win10.x86\AppPackages\BlankApp\BlankApp_1.16.10.1_Test\Dependencies\x64\Microsoft.VCLibs.x64.14.00.appx Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFB, The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. Deployment of package com.propelics.blankApp_1.16.10.1_x86__d7c8pgvss6ysm was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package. NOTE: For additional information, look for [ActivityId] b4aafe06-b585-0004-3ead-bcb485b5d301 in the Event Log or use the command line Get-AppxLog -ActivityID b4aafe06-b585-0004-3ead-bcb485b5d301 At C:\Users\karom\.titanium\vsbuild\BlankApp\win10.x86\AppPackages\BlankApp\BlankApp_1.16.10.1_Test\Add-AppDevPackage.ps1:388 char:13 + Add-AppxPackage -Path $DeveloperPackagePath.FullName -Dep ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ResourceExists: (C:\Users\karom\..._x86.appxbundle:String) [Add-AppxPackage], PSInvalidOperationException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand Error: Could not install the app. at C:\ProgramData\Titanium\mobilesdk\win32\7.1.0.v20180301114750\node_modules\windowslib\lib\winstore.js:104:14 at ChildProcess.
CPUs = 8
Memory = 15.9GB Node.js Node.js Version = 8.9.3 npm Version = 5.5.1 Appcelerator CLI Installer = 4.2.12 Core Package = 7.0.2 Titanium CLI CLI Version = 5.0.14 node-appc Version = 0.2.41 Titanium SDKs 7.1.0.v20180301114750 Version = 7.1.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.1.0.v20180301114750 Platforms = android, windows git Hash = 764bcdd git Timestamp = 3/1/2018 19:52 node-appc Version = 0.2.43 7.0.2.GA Version = 7.0.2 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.0.2.GA Platforms = android, windows git Hash = 5ef0c56 git Timestamp = 2/9/2018 19:02 node-appc Version = 0.2.43 Microsoft (R) Visual Studio 14.0 (selected) Path = C:\Program Files (x86)\Microsoft Visual Studio 14.0\ CLR Version = v4.0.30319 MSBuild Version = v14.0.25420.1 Windows Phone SDKs = not installed Microsoft (R) Windows Phone SDK 10.0 (selected) Path = C:\Program Files (x86)\Windows Kits\10\ 8.1 **Not supported by Titanium SDK 7.1.0.v20180301114750** Path = C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\ Windows PowerShell Enabled = yes {quote}{quote} 3) Run a ti clean {quote} You don't need to run
ti clean
on each time on build. Would you try it withoutti clean
? It means resets the auto increment numbering. We actually designed it that way, in this case you need to * Stop usingti clean
on each build Or, * Use--forceUnInstall
flag to explicitly uninstall existing app I would think this is by design but we could improve error message though.Thanks a lot for info. Will forward to customer.