id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
183 | CLI-1051 | 07/22/2016 22:27:33 | appc login: Deauthorize message does not include -D flag | When using {{appc login}} for the first time on a new machine (or after Deauthorizing one) the CLI will return a message stating the ID of the system being authorized, as well as instructions on how to deauthorize the machine. However the command given to do so is {{appc logout}}, which does not deauthorize the machine. h2. Steps to Reproduce 1. {{appc login}} to an unauthorized machine / {{appc logout -D}} to deauthorize a machine and then {{appc login}}. 2. Enter credentials. 3. You will be prompted to enter an authorization code, which is sent to your account email. 4. Enter the authorization code. h2. Expected Result CLI should return the message "You can deauthorize this computer by logging out with appc logout *-D*" h2. Actual Result CLI returns the message "You can deauthorize this computer by logging out with appc logout" | 1 |
184 | CLI-1052 | 07/25/2016 08:55:21 | Fix Jenkins and travis for appc-cli-titanium | There's a number of things. 1. Currently the jenkins build is failing because it didn't fulfil the required coverage threshold. 2. While unskipping this unit test https://github.com/appcelerator/appc-cli-titanium/blob/master/test/new_test.js#L217, we realise that travis (and jenkins) will break because it prompts for "Do you wish to install Hyperloop?" we may need a flag to suppress this prompt. 3. This configuration is messed up. https://github.com/appcelerator/appc-cli-titanium/blob/master/test/travis_configure.sh#L23 it installs 4.0.0.GA when we should be either installing the latest G.A. version available, or latest master build 4. If we use master branch (6.0.0) it will complain about node version 0.10.x is not supported. which is correct so we should consider changing the CI script to support node 4.x 5. Same issue with jenkins. the ci script is here: https://github.com/appcelerator/jenkins_dsl/blob/master/jobs/appc_cli_dependencies.groovy | 3 |
185 | CLI-1054 | 07/26/2016 10:16:58 | Set connection timeout for appc use command | *Details:* {{appc use -o json --full}} command is not getting timed out if it's unable to get the response. *To reproduce:* # Configure invalid proxy server through CLI Example: {{appc config set proxyServer https://"username:password"@10.10.12.13:4567}} # Run {{appc use -o json --full}} command *Actual:* It's waiting for indefinite time and command is not returning at all. *Expected* As we provided invalid proxyServer, it should timeout after 10sec | 3 |
186 | CLI-1065 | 08/02/2016 05:20:40 | CLI doesn't relay the error message to Studio when login failed | Studio and CLI will exchange the data in the form of json format through socket connection. If a trial plan is expired, studio is keep asking for login credential without showing what was wrong with the credentials. As studio depends on CLI for login, CLI should return the error message as part of the socket communication message protocol. For example: *CLI request for login prompt:* {code:json} {"type":"question","question":[{"type":"input","name":"username","message":"Appcelerator ID:"},{"type":"password","name":"password","message":"Password:"}]} {code} *Studio response to process the login:* {code:json} {"username":"[email protected]","password":"test1234"} {code} If the password is wrong or it was unable to login due to some other issue(ex: trial account expired),CLI should also send the error message. *Here is my proposal for expected response:* {code:json} {"type":"question","question":[{"type":"input","name":"username","message":"Appcelerator ID:"},{"type":"password","name":"password","message":"Password:"}], "errormessage":"Unable to login, your trial plan is expired. Renew your subscription today!"} {code} | 5 |
187 | CLI-1068 | 08/03/2016 23:55:18 | Windows: A iPhone module folder is downloaded for Windows OS | h4. Description A iPhone folder containing {{com.appcelerator.apm}} and {{hyperloop}} module is downloaded for Windows OS. h4. Steps to reproduce: # {{appc new}} create an application with Hyperloop enabled, this will download Hyperloop. # Navigate to {{C:\ProgramData\Titanium\modules\iphone}} h4. Actual The iPhone folder containing {{com.appcelerator.apm}} and {{hyperloop}} is present. h4. Expected There should be no iPhone folder on Windows OS | 3 |
188 | CLI-1066 | 08/04/2016 00:10:47 | Hyperloop: If you have an older version of Hyperloop in your module global space, you cannot get the newer Hyperloop version | *Details:* If you have an older version of Hyperloop in your module global space, you cannot get the newer Hyperloop version. *Notes:* To workaround this issue, you will need to remove both (Android and iOS) Hyperloop modules from the global space. *Steps to reproduce:* # In your global module space, {{~/Library/Application Support/Titanium/modules}} or {{C:\ProgramData\Titanium\modules}}, rename your Hyperloop module version to an older version e.g. {{modules/android/hyperloop/1.2.5}} -> {{modules/android/hyperloop/1.2.4}}. # On Mac, you should remove {{modules/iphone/hyperloop/<ver>}} folder. # Get the latest Hyperloop module via {{appc new}}; go through all the prompts # Check your module global space again *Actual:* The latest Hyperloop module is not downloaded. *Expected:* The newest Hyperloop module should be downloaded if you have an older version of it. | 5 |
189 | CLI-1067 | 08/04/2016 00:45:45 | We don't see "Would you like to enable hyperloop for the app" prompt while enabling services for new app | h5.Steps To Reproduce: 1. Create a new project in appc studio. 2. Fill in all the necessary details in the "New mobile app project" dialog. 3. Make sure you have "Enable appcelerator platform services" enabled. 4. Click next & then finish. h5.Actual Results: 1. We do not get the "Would you like to enable hyperloop for this app" prompt. 2. Hyperloop is enabled & the module is included in the project default. *NOTE*: CLI prompts you if you would like to enable hyperloop for the app. h5.Expected Result: 1. We should get a prompt "Would you like to enable hyperloop for this app". | 5 |
190 | CLI-1069 | 08/05/2016 10:26:57 | Install hyperloop module directly through CLI command | *Current behaviour:* While creating a new project CLI identifies whether it's required to install or update the hyperloop module based on the selected SDK version. *CLI way to update Hyperloop:* # Find the selected SDK # Fetch {{api/v2/downloads}} from 360 dashboard # Identify what version is installed in the system # Identify what is available on the dashboard 360 # If required to install - download the zip, identify folders based on the OS(for example for windows we shouldn't install iOS module) and extract to the target location. *Appcelerator Studio way to update Hyperloop:* Repeat above steps 1-5 again in Java Can we do something like this to avoid duplicate effort and also to maintain the consistency across the tooling (studio/CLI) {code:java} appc install --module hyperloop {code} This command will follow the above steps and install the appropriate Hyperloop module Studio will also use the same command to install the Hyperloop. | 5 |
191 | CLI-1075 | 08/10/2016 06:03:12 | Unable to configure which IP should the LiveView use | h4. Problem Description When your windows machine has several network adapters (either physical or virtual) you can't configure the LiveView to use certain IP. In this case, I have two IPs, one internal for Virtual Box and other external connecting with the Wifi Access Point. For testing liveview with genymotion, I would like to use the internal, when using a device, it should be using the external network adapter (wifi). Any suggestion on how to modify the liveview IP is more than welcomed. | 5 |
192 | CLI-1077 | 08/12/2016 15:38:32 | CLI outputting non-JSON warning to Studio | While doing some Studio work, I saw that the CLI is spitting out warning text in it;s output, when it's being invoked by Studio (presumably with some command asking for JSON output). Since the warning test is not JSON, Studio's parsing breaks: {code} You are attempting to run appc 5.4.0 which was compiled for node v5.12.0 but you are now running node v5.10.0 Rebuilding package modules ... Package modules rebuilt! { "activeSDK": "6.0.0.v20160811221444", "defaultInstallLocation": "/Users/cwilliams/Library/Application Support/Titanium", "installLocations": [ "/Users/cwilliams/Library/Application Support/Titanium", "/Library/Application Support/Titanium" ], "installed": { // rest of JSON snipped ... {code} | 3 |
193 | CLI-1085 | 08/16/2016 00:13:18 | limit the size of a symbol file uploaded to crashserver to 250Mb | in CRASH-65 we limit the size of a symbol file that can be uploaded to the crashserver to 250Mb. this is based on discussions that incorporate competing products and the likely size of a symbol file in the near future weighed against the requirements to support large files. Ideally, the Studio and CLI components should also prevent anything larger than 250Mb from even being posted to the server. This can allow the user to know about the limitation as well. | 3 |
194 | CLI-1079 | 08/18/2016 00:22:09 | Modules and plugins are not overwritten if the files already exist | Hyperloop plugin is picked to illustrate the issue, but this should be reproducible with any modules, plugins or components. *Steps to reproduce* 1. Make sure Hyperloop plugin is installed 2. Modify {{../plugins/hyperloop/package.json}} to a different version, i.e 1.1.1 3. Do {{appc config set lastUpdateCheckTiDownloads null}} or remove Hyperloop module folder to trigger an update 4. Do {{appc new}} *Actual Results* Once the project is created, verify that {{../plugins/hyperloop/package.json}} is not updated. *Expected Results* The Hyperloop plugin should be updated . | 1 |
195 | CLI-1080 | 08/22/2016 12:39:29 | 'SyntaxError: Unexpected end of input' on appc use --prerelease | h5.Description When I ran {{appc use --prerelease}} I got the following error, I can't reproduce this, error comes from [this line|https://github.com/appcelerator/appc-install/blob/master/lib/util.js#L605], *Notes* After this I checked whether http://software-preprod.cloud.appctest.com/ was up, it was but I was met with [this|https://github.com/appcelerator/appc-registry-server/blob/master/web/views/index.hbs#L55], both issues appear related to me, maybe to do with caching registry side? I ran this command around 12:30 BST 22/08/2016 incase that is useful for any logging {code} C:\Users\Ewan>appc use --prerelease -undefined:1 SyntaxError: Unexpected end of input at Object.parse (native) at IncomingMessage.<anonymous> (C:\Users\Ewan\AppData\Roaming\npm\node_modules\appcelerator\lib\util.js:605:25) at emitNone (events.js:72:20) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:921:12) at nextTickCallbackWith2Args (node.js:442:9) at process._tickCallback (node.js:356:17) {code} h5.Steps to reproduce *This steps probably won't reproduce the error, but are what I did* # run {{appc use --prerelease}} h5.Actual result You will get the error above h5.Expected result You should not get an error | 3 |
196 | CLI-1081 | 08/22/2016 19:14:45 | Modules update failed with Error: Invalid URI | *Steps to reproduce* 1. {{appc config set lastUpdateCheckTiDownloads null}} 2. {{appc new}} or {{appc run}} *Expected result* There should be no {{Error: Invalid URI}} error. *Actual result* The process terminates with {{Error: Invalid URI}} error. | 1 |
197 | CLI-1088 | 09/01/2016 13:57:22 | CLI should not re-prompt a user once their account has been locked out | h5.Description APPTS-8562 introduced the ability for accounts to be locked out after a certain amount of failed login attempts, the CLI does not handle this appropriately and outputs an access privileges error while also re-prompting the user. The CLI should inform the user what has happened and provide any other details deemed necessary {code} ? Appcelerator ID: [email protected] ? Password: ************ Invalid Appcelerator ID and password combination. Appcelerator Login required to continue ... ? Appcelerator ID: [email protected] ? Password: ****************** You do not have access privileges to view this content. {code} h5.Steps to reproduce # Run {{appc login}} and enter an incorrect password # GOTO 1 h5.Actual result After 6 attempts the error message changes to {{You do not have access privileges to view this content.}} the CLI will keep prompting the user to login h5.Expected result If a user is locked out of their account, the CLI should not re-prompt and inform the user of the lockout, while displaying any information that is deemed helpful e.g Directing them to check their emails to disable the lockout | 3 |
198 | CLI-1089 | 09/01/2016 14:16:58 | Allow more than one attempt at entering an auth code | h5.Description Currently the CLI only allows a user 1 attempt at entering an auth code. This should be changed to allow the user unlimited attempts until the auth code expires, like the online login, or exit after a certain number of retries while outputting some information to the user. h5.Steps to reproduce # {{appc logout -D}} # {{appc login}} # Enter an incorrect auth code h5.Actual result The CLI will exit on one incorrect auth code h5.Expected result CLI should allow some retries on auth code | 3 |
199 | CLI-1090 | 09/01/2016 17:04:12 | update-notifier still getting installed | h5.Description API-1310 removed update-notifier, however when installing appcelerator npm package it still gets installed, this is because the npm shrinkwrap file still references the package [here|https://github.com/appcelerator/appc-install/blob/f5025900a1f056bc9c404f16d9d51a573dc447a1/npm-shrinkwrap.json#L579]. h5.Steps to reproduce # Install appc npm using {{npm i -g [email protected]}} h5.Actual results update-notifier is installed h5.Expected results update-notifier should not be installed as it's not used | 1 |
200 | CLI-1094 | 09/06/2016 05:21:13 | Build got stuck at validating the session | *Details:* While I'm building a project with iOS simulator - build got stuck at {{check if session is invalidated}} state for more than {color:red}4mins{color}. You can observe the time from the below trace log. {code:java} Appcelerator Command-Line Interface, version 5.4.0 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. 2016-09-06T04:10:10.368Z | TRACE | set environment to {"registry":"https://software.appcelerator.com","security":"https://security.appcelerator.com","baseurl":"https://platform.appcelerator.com"} 2016-09-06T04:10:10.369Z | TRACE | checking credentials for existing session 2016-09-06T04:10:10.498Z | TRACE | Attempting to load session info from config file 2016-09-06T04:10:10.503Z | TRACE | check if session is invalidated 2016-09-06T04:16:15.705Z | TRACE | registry result undefined undefined true undefined false undefined 2016-09-06T04:16:15.705Z | TRACE | registry returned undefined 2016-09-06T04:16:15.706Z | TRACE | session expiry 1473739783566 false 2016-09-06T04:16:15.706Z | TRACE | Arrow Cloud config file: /Users/kkolipaka/.acs 2016-09-06T04:16:15.717Z | TRACE | found Arrow Cloud login { mid: '87d2b0b9eb3b3518fa6c2a16184cf800d60f6bb2', {code} *Expected:* It should timeout after 10sec or so. | 5 |
201 | CLI-1097 | 09/08/2016 00:25:26 | Include Hyperloop "version" to plugin tag in the tiapp.xml | At the moment, when enabling Hyperloop, no version property is assigned to the plugin tag. Under {{tiapp.xml}} you see: {code} <plugins> <plugin>hyperloop</plugin> </plugins> {code} Since we started versioning Hyperloop plugin, we should specify the plugin version in tiapp.xml. | 1 |
202 | CLI-1099 | 09/08/2016 19:24:51 | appc login error when specify arrowcloud url without protocol | *Step to Reproduce* Do {{appc login --cloud admin.cloudapp-enterprise.appcelerator.com}} *Expected Result* Login should succeed. *Actual Result* Login failed with error: {{ERROR | Invalid URI "admin.cloudapp-enterprise.appcelerator.com/login"}} | 1 |
203 | CLI-1100 | 09/08/2016 21:45:52 | appc new to use SDK compatible version of soasta plugin | At the moment, {{appc new}} and enable test service will always use the latest installed soasta plugin regardless of SDK version. In APPTS-8874, there'll be different versions of the plugin for ti sdk 6.0.0/newer, and ti sdk 5.5.X. {{appc new}} will need to be updated to use the compatible plugin version. | 5 |
204 | CLI-1107 | 09/15/2016 22:57:56 | deprecated minimatch. Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue | We should update all the places this appears [email protected] /Users/ingo/.appcelerator/install/5.5.0/package ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └─┬ [email protected] │ │ │ ├─┬ [email protected] ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] ├─┬ [email protected] │ └─┬ [email protected] ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ └─┬ [email protected] | 1 |
205 | CLI-1114 | 09/19/2016 20:16:59 | appc switch org: errors when I only have one org | When I run {{appc switch org}} while I only have one org it errors: {code} Fokkes-MacBook-Pro:ticons-server fokkezb$ appc switch org Appcelerator Command-Line Interface, version 5.5.0 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. No orgs were found! 2016-09-19T19:16:35.169Z | ERROR | true {code} Instead, it should simply say there are no other orgs to switch to. | 1 |
206 | CLI-1115 | 09/21/2016 15:55:37 | Set Node 4.x as minimum supported version | h5.Description In 6.0.0/4.8.0 it's planned to move to 4.X as the minimum supported version. This is implemented in the [SDK/Titanium|TIMOB-23448] and in [TISTUD|TISTUD-8509] but there is no implementation for this in the CLI. It seems to me like we should want to restrict the version in the CLI also and maybe introduce something similar to Titanium i.e warnings for node versions higher than a certain version etc h5.Steps to reproduce # Set node 0.12.7 as your selected node version using your favourite node version manager or the official installer # Download a 6.0.0 CLI, {{appc use 6.0.0-47}} # Use the CLI for non titanium tasks (as Titanium has this already implemented) h5.Actual result The appc cli is perfectly happy with you using 0.12.7 h5.Expected result As we are moving to a minimum of 4.X for every other product. So should the CLI | 2 |
207 | CLI-1117 | 09/23/2016 14:12:31 | checkSession endpoint is hit twice when building | h5.Description When building an application (and other commands that require a user to be logged in) the CLI appears to be hitting the checkSession endpoint twice, once before executing the command and then once again in the command that has been executed. {code} 2016-09-23T13:10:49.712Z | TRACE | check if session is invalidated 2016-09-23T13:10:52.269Z | TRACE | registry result 200 application/json undefined undefined false undefined 2016-09-23T13:10:52.279Z | TRACE | registry returned { expiry: 1475241053030 } 2016-09-23T13:10:52.279Z | TRACE | refresh session expiry to: 1475241053030 2016-09-23T13:10:52.281Z | TRACE | session expiry 1475241053030 false 2016-09-23T13:10:52.281Z | TRACE | Arrow Cloud config file: /Users/eharris/.acs 2016-09-23T13:10:52.283Z | TRACE | found Arrow Cloud login { mid: '0c3c5f85cf1a73d7f072e4e38d40219695855086', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', username: '[email protected]', cookie: [ 'connect.sid=s%3A4O8AjS2WTpr0w045gTzgp2Bj.8krzD4V6QTo%2FqpiQiGKp6ebSlrXwpf10eWOC%2B0gYtq8; Path=/; Expires=Fri, 07 Oct 2016 11:22:36 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise-preprod.appctest.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise-preprod.appctest.com 2016-09-23T13:10:52.284Z | TRACE | Arrow Cloud cookie expiry [ 1475839356000 ] 2016-09-23T13:10:52.284Z | TRACE | session already loaded in opts.session 2016-09-23T13:10:52.285Z | TRACE | getCredentials() session: { "ipaddress": "10.142.9.89", "username": "[email protected]", "password": "<OMITTED>", "session": "<OMITTED>", "nonce": "<OMITTED>", "environment": { "name": "production", "isProduction": true, "acsBaseUrl": "https://preprod-api.cloud.appctest.com", "acsAuthBaseUrl": "https://dolphin-secure-identity.cloud.appcelerator.com", "nodeACSEndpoint": "https://admin.cloudapp-enterprise-preprod.appctest.com" }, "token": "<OMITTED>", "fingerprint": "0c3c5f85cf1a73d7f072e4e38d40219695855086", "fingerprint_description": "Mac OSX Serial Number: C02S40W9G8WP", "org_id": 100001710, "expiry": 1475241053030 } 2016-09-23T13:10:52.285Z | TRACE | loading plugins for command "run" 2016-09-23T13:10:52.317Z | TRACE | run search paths: [ "/Users/eharris/.appcelerator/install/5.5.0/package", "/Users/eharris/.appcelerator/install/5.5.0/package/node_modules", "/Users/eharris/Documents/Appcelerator_Studio_Workspace/ppTAlloy/plugins", "/Users/eharris/Documents/Appcelerator_Studio_Workspace/ppTAlloy/node_modules", "/Users/eharris/Documents/Appcelerator_Studio_Workspace/node_modules", "/Users/eharris/Documents/node_modules", "/Users/eharris/node_modules", "/Users/node_modules", "/node_modules", "/Users/eharris/.appcelerator/.npm/lib/node_modules" ] 2016-09-23T13:10:52.318Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/5.5.0/package/appc.js 2016-09-23T13:10:52.528Z | DEBUG | [PLUGIN-LOAD] 209ms /Users/eharris/.appcelerator/install/5.5.0/package/node_modules/appc-cli-titanium/appc.js 2016-09-23T13:10:52.528Z | DEBUG | run plugin: /Users/eharris/.appcelerator/install/5.5.0/package/node_modules/appc-cli-titanium 2016-09-23T13:10:52.530Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/eharris/.appcelerator/install/5.5.0/package/node_modules/arrow/appc.js 2016-09-23T13:10:52.532Z | DEBUG | run plugin: /Users/eharris/.appcelerator/install/5.5.0/package/node_modules/arrow 2016-09-23T13:10:52.535Z | TRACE | plugin "arrow" failed its "when" function check, skipping... 2016-09-23T13:10:52.536Z | TRACE | loading plugin "titanium" for command "run" CLI options via function 2016-09-23T13:10:52.537Z | TRACE | loading plugin "titanium" for command "run" CLI options via array 2016-09-23T13:10:52.539Z | TRACE | executing command "run" with the following plugins: ["titanium"] 2016-09-23T13:10:52.540Z | TRACE | Attempting to load session info from config file 2016-09-23T13:10:52.541Z | TRACE | check if session is invalidated 2016-09-23T13:10:55.161Z | TRACE | registry result 200 application/json undefined undefined false undefined 2016-09-23T13:10:55.161Z | TRACE | registry returned { expiry: 1475241055924 } 2016-09-23T13:10:55.161Z | TRACE | refresh session expiry to: 1475241055924 2016-09-23T13:10:55.163Z | TRACE | session expiry 1475241055924 false 2016-09-23T13:10:55.164Z | TRACE | session already loaded in opts.session {code} h5.Steps to reproduce # Run {{appc -p ios -l trace}} in a titanium project h5.Actual result checkSession endpoint is hit twice h5.Expected result checkSession endpoint only needto be hit once | 1 |
208 | CLI-1122 | 10/05/2016 16:40:42 | Hyperloop is downloaded everytime lastUpdateCheckTiDownloads expires on Windows | h5.Description When building a project on Windows, during the build if lastUpdateCheckTiDownloads has expired it performs a check for any modules that need to be downloaded, on Windows as we now do not extract the iphone for hyperloop the CLI will download and extract hyperloop every day, When combined with CLI-1106 (the download and extraction process taking anywhere from ~3-10 minutes) this a real nuisance h5.Steps to reproduce # appc config set lastUpdateCheckTiDownloads null # Build a project # appc config set lastUpdateCheckTiDownloads null # Build a project h5.Actual result The CLI will download it hyperloop every time h5.Expected result The CLI should only check for an iphone folder on OSX | 5 |
209 | CLI-1123 | 10/11/2016 23:07:07 | Incorrect APM module version is set in tiapp.xml module tag | **Reproduce Steps** 1. {{appc new -t titanium}} 2. check {{tiapp.xml}} {{modules}} tag for {{com.appcelerator.apm}} **Expected Result** the module version should be in the format of a.b.c. **Actual Result** the module version is set to a long string of digits. | 3 |
210 | CLI-1125 | 10/13/2016 00:33:41 | Remove version attribute from tiapp.xml when creating new app | In 6.0 prerelease, when a new project is created, we added the modules version in tiapp.xml to prevent incompatible modules being used when building a project. i.e {code} <module platform="android" version="a.b.c">mod</module> <module platform="iphone" version="a.b.c">mod</module> {code} With TIMOB-23912 fixed, we should not set version, so project build will pickup the latest compatible module version. So the modules tag should be like this: {code} <module platform="android">mod</module> <module platform="iphone">mod</module> {code} Unless developers want to use a specific version, they can do so by knowingly update the project's tiapp.xml. | 3 |
211 | CLI-1126 | 10/17/2016 12:38:54 | ACA and APM being downloaded everytime when lastUpdateCheckTiDownloads has expired | h5.Description When building an application in an enterprise org, when lastUpdateCheckTiDownloads has expired I am always seeing ACA and APM modules downloaded. After placing some console logs I believe the reason that these modules are always downloaded is because the CLI is checking for the iOS modules in {{/Users/eharris/Library/Application Support/Titanium/modules/iOS/com.appcelerator.apm}} and {{/Users/eharris/Library/Application Support/Titanium/modules/iOS/com.appcelerator.aca}}, because these folders aren't fuond the CLI returns null for the iOS module version on the system and decide to download a new one, *related code is [found here|https://github.com/appcelerator/appc-cli-titanium/blob/master/plugins/util.js#L471]* It may be that the payload data from 360 is incorrect as that is where the platforms are sourced from I believe *This happens on both run and new* h5.Steps to reproduce # Login to an enterprise org in preprod # {{appc config set lastUpdateCheckTiDownloads null}} # {{appc run -p ios -l trace --build-only}} h5.Actual result ACA and APM are downloaded every time, CLI is checking incorrect location for iOS module h5.Expected result ACA and APM should not be downloaded every time, CLI should check for correct locations | 3 |
212 | CLI-1131 | 10/17/2016 20:08:02 | appc use does not show 6.0 version when selected | *Description:* In prod environment, when entering "appc use" or "appc use --prerelease", the resulting list does not show release 6.0.0-61, although that release was selected to be used. *Steps to reproduce:* 1. Type in Mac terminal "appc use 6.0.0-61" 2. Type "appc use" 3. Type "appc use --prerelease" *Result:* The following output shows the results. These results always occur (not intermittent). amukherjee:Titanium amukherjee$ appc use 6.0.0-61 6.0.0-61 is now your active version amukherjee:Titanium amukherjee$ appc use The following versions are available: 5.5.1 Installed (Latest) 5.5.0 Installed 5.4.0 Not Installed 5.3.1 Not Installed 5.3.0 Not Installed 5.2.2 Not Installed 5.2.1 Not Installed 5.2.0 Not Installed 5.1.0 Not Installed 5.0.4 Not Installed 5.0.3 Not Installed 5.0.2 Not Installed 5.0.1 Not Installed 5.0.0 Not Installed 4.1.3 Not Installed 4.1.2 Not Installed 4.1.1 Not Installed 4.1.0 Not Installed 4.0.2 Not Installed 4.0.1 Not Installed 4.0.0 Not Installed amukherjee:Titanium amukherjee$ appc new Appcelerator Command-Line Interface, version 6.0.0-61 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. *Expected Result:* 6.0.0-61 should have been on the list from "appc use", or "appc use --prerelease", but it is not in either case. Note from the results, when "appc new" is typed, the correct version is used, it is just not appearing in the list of versions available/installed. | 2 |
213 | CLI-1128 | 10/18/2016 19:06:18 | Update cli to include acs cli 1.2.2 | We have just released arrowcloud 1.5.3 and new acs cli 1.2.2. Please update cli to include latest acs cli. | 2 |
214 | CLI-1130 | 10/28/2016 14:21:06 | Use node.js os.homedir to get homedir | Currently we use a custom way of getting a users home dir, which isn't perfect and can break CLI-949. When I made the fix for that ticket I couldn't replace it with os.homedir as it was introduced in node v4 and we still supported 0.12. Well, now we no longer support 0.12 so lets use it :) Refs: https://nodejs.org/dist/latest-v4.x/docs/api/os.html#os_os_homedir https://github.com/nodejs/node/pull/1791 | 3 |
215 | CLI-1133 | 11/15/2016 01:07:31 | Update dependencies of appc-inquirer | Building PRs on Travis for appc-cli currently fails due to a bug in the outdated {{inquirer}} module which is part of {{appc-inquirer}}, which in turn is a dependency of {{appc-cli}}. This just occurred recently and only affects Travis builds. Testing with a fork of appc-inquirer with updated dependencies fixed the appc-cli build on Travis. | 2 |
216 | CLI-1134 | 11/15/2016 10:07:00 | When unpublish an arrow app the version in package.json is not considered | Steps to reproduce: 1. Publish arrow app with version 1.0.0 specified in package.json {code:javascript} { ... "version": "1.0.0", ... } {code} 2. Change the version in package.json from "1.0.0" to "0.0.3". Type {code:javascript} > appc unpublish {code} in the root folder of the app. Your app will be unpublish. Desired behavior: It should display some message that the local version of the app is different from that in the cloud, i.e. 'Missing app with version v.0.0.3' or kind of. | 5 |
217 | CLI-1140 | 11/29/2016 14:19:59 | Arrow app crashes with Uncaught Exception Cannot find module './ReactHostOperationHistoryHook' | h5.Description When attempting to run an arrow app the app will crash with the below, while at first glance this may appear to be an issue with arrow, the root cause lies in the {{appc publish}} command as checking jenkins shows that this file is being excluded as it matches one of these[regexes|https://github.com/appcelerator/appc-cli/blob/96ca28c6b63482d9a956beaf8c321f4bd910fa56/lib/publish.js#L113-L116], changing them to use the {{^}} character will fix the issue to include {{./ReactHostOperationHistoryHook}} but will then fail to include two files called {{History.js}} from react-router (these do not cause a crash to my knowledge, but they should be included) and also the {{logs}} folder from arrow-admin-api (this does cause a crash), this folder is required {code} Uncaught Exception Cannot find module './ReactHostOperationHistoryHook' Error: Cannot find module './ReactHostOperationHistoryHook' at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.require (module.js:497:17) at require (internal/module.js:20:19) at Object.<anonymous> (/Users/eharris/.appcelerator/install/6.1.0-300/package/node_modules/arrow/node_modules/react/lib/ReactDebugTool.js:15:37) at Module._compile (module.js:570:32) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) {code} h5.Steps to reproduce # Download 6.1.0-300 {{appc use 6.1.0-300}} # Create an arrow app {{appc new -t arrow -n myarrowapp && cd myarrowapp}} # Run the app {{appc run}} h5.Actual result Crash with the above error h5.Expected result App should not crash | 2 |
218 | CLI-1142 | 12/08/2016 01:38:48 | "Fatal error: The config file "node_modules/grunt-appc-js/.jscsrc" was not found" if grunt-appc-js is called within another grunt plugin | *Details:* {{Fatal error: The config file "node_modules/grunt-appc-js/.jscsrc" was not found}} error is returned if grunt-appc-js is called within another grunt plugin; see attachment. *Steps to reproduce:* # Clone or pull https://github.com/appcelerator/appc-registry-server from master branch # Run {{npm install}} # In Gruntfile.js, comment out these lines: https://github.com/appcelerator/appc-registry-server/blob/master/Gruntfile.js#L68-L70 # Run {{grunt appc_js}} *Actual:* Fatal error is returned; see attachment. *Expected:* Fatal error should not be returned and {{jscs:src}} task should be executed without any issues. | 2 |
219 | CLI-1143 | 12/08/2016 13:54:31 | appc-inquirer skips predefined answers | In CLI-1133 the inquirer dependency of appc-inquirer was updated because of issues in Travis builds. There was a slight behavior change in inquirer which removes unasked question from the answers object. To remain backwards compatible we need to get the unaltered answers object with any default answers provided through options arguments in the CLI. | 2 |
220 | CLI-1163 | 02/09/2017 22:55:54 | Integrate with latest acs cli 1.2.3 | we just published acs npm 1.2.3 please update appc cli to include it | 0 |
221 | CLI-1166 | 03/08/2017 22:22:14 | Correct NSP errors in appc-cli-titanium | nsp check flags [email protected]. update dev to fix the issue: [email protected] > [email protected] > [email protected] > [email protected] | 1 |
222 | CLI-1169 | 03/15/2017 23:18:17 | TypeError: Data must be a string or a buffer thrown when running commands if sid is undefined in config | h5.Description *To fix this delete your appc-cli.json and login again, using preproduction not preprod* When running commands I am seeing the following error get thrown {{TypeError: Data must be a string or a buffer thrown when running commands}}, full stacktrace below. The error is coming from [this line|https://github.com/appcelerator/appc-cli/blob/e9b5892216ec43b98ae592473aaba032fdcd41c4/lib/commands/config.js#L158] The CLI is calling config.get('sid') which has somehow gone walkabouts from my config so it is undefined, I believe this is during the {{appc config set defaultEnvironment}} step below. {code} 2017-03-15T23:05:46.895Z | ERROR | An uncaught exception was thrown! Data must be a string or a buffer 2017-03-15T23:05:46.895Z | ERROR | Data must be a string or a buffer 2017-03-15T23:05:46.897Z | TRACE | TypeError: Data must be a string or a buffer at TypeError (native) at Hash.update (crypto.js:74:16) at config (/Users/eharris/.appcelerator/install/6.1.0/package/lib/commands/config.js:158:13) at getSessionEntitlements (/Users/eharris/.appcelerator/install/6.1.0/package/lib/constants.js:221:51) at Object.setEnvironment (/Users/eharris/.appcelerator/install/6.1.0/package/lib/constants.js:326:42) at executeCommand (/Users/eharris/.appcelerator/install/6.1.0/package/lib/core.js:406:23) at Object.checkLogin (/Users/eharris/.appcelerator/install/6.1.0/package/lib/core.js:385:9) at Command.<anonymous> (/Users/eharris/.appcelerator/install/6.1.0/package/bin/commands/login.js:26:14) at Command.<anonymous> (/Users/eharris/.appcelerator/install/6.1.0/package/lib/commander.js:102:13) at Command.listener (/Users/eharris/.appcelerator/install/6.1.0/package/node_modules/commander/index.js:301:8) {code} h5.Steps to reproduce # Switch to production {{appc logout && appc config set defaultEnvironment production && appc login}} # Switch back to preproduction {{appc logout && appc config set defaultEnvironment preproduction && appc login}} # {{appc config set defaultEnvironment preprod}} # appc whoami/appc login h5.Actual result Above error is thrown h5.Expected result Error not thrown | 1 |
223 | CLI-1171 | 03/21/2017 18:09:19 | cannot find module session | When trying to perform an *appc install* i got the following message: {noformat} 2017-03-21T17:37:51.789Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/jcruz/.appcelerator/install/6.2.0-master.25/package/appc.js 2017-03-21T17:37:51.792Z | WARN | Failed to load package plugin from /Users/jcruz/.appcelerator/install/6.2.0-master.25/package Error: Cannot find module './session' at Function.Module._resolveFilename (module.js:440:15) at Function.Module._load (module.js:388:25) at Module.require (module.js:468:17) at require (internal/module.js:20:19) at Object.<anonymous> (/Users/jcruz/.appcelerator/install/6.2.0-master.25/package/lib/plugins/install.js:24:12) at Module._compile (module.js:541:32) at Object.Module._extensions..js (module.js:550:10) at Module.load (module.js:458:32) at tryModuleLoad (module.js:417:12) at Function.Module._load (module.js:409:3) {noformat} | 1 |
224 | CLI-1173 | 03/21/2017 19:26:19 | Error: Error attempting to login to Arrow Cloud | Logging in via the appc-cli, we get the following: {code} 2017-03-21T16:52:44.561Z | DEBUG | Choose organization... 2017-03-21T16:52:44.561Z | DEBUG | Loading organization list... Appc:sdk fetching https://dashboard.cloudapp-1.appctest.com/api/v1/auth/findSession sid= s:N8K75fOM8SG7bWjUNct7TYVTs-oaJNZZ.c11XzVsy9dkn1bST1xFZb6str41MctUykDfNL0B0y/8 userAgent= Appcelerator/2.0.2 (Macintosh; Intel Mac OS X 16_4_0; en_US) nodejs/4.3.0 Version/2.0.2 Safari/0.0.0 appcelerator/6.2.0-master.25 +21ms Appc:sdk api response, err=null, body='{"success":true,"result":{"cookie":{"originalMaxAge":false,"expires":false,"secure":null,"httpOnly":true,"domain":".cloudapp-1.appctest.com","path":"/","sameSite":null},"sessionID":"N8K75fOM8SG7bWjUNct7TYVTs-oaJNZZ","from":"cli","username":"[email protected]","userHash":"8852ee1098812f87ad6244a0250d0978","token":"Y2+eySETeOW/1uR5PKGh2piqBfk=","guid":"17bddb9a-b87b-42cc-aceb-c61c7ca08d58","sid":"e6a59b96f522301e0b9f98abb160e6c2","org_id":985549229695766,"org":{"_id":"58d09dfed95b7d001c0162b3","org_id":985549229695766,"guid":"8e45e404-4cc0-4e20-8f82-1598c7eb149e","name":"My Organization","admins":["17bddb9a-b87b-42cc-aceb-c61c7ca08d58"],"users":[],"limit_users":-1,"active":true,"creator":"17bddb9a-b87b-42cc-aceb-c61c7ca08d58","created":"2017-03-21T03:29:02.319Z","package":"enterprise","entitlements":{"id":"54d8e4abce78815d81104cb4","name":"Enterprise","apiRateMonth":100000000,"pushRateMonth":100000000,"storageFilesGB":1000,"storageDatabaseGB":100,"containerPoints":9999,"arrowPublish":true,"eventRateMonth":100000000,"daysDataRetained":731,"allowProduction":true,"appDesigner":true,"appPreview":true,"hyperloop":true,"nativeSDK":true,"premiumModules":true,"paid":true,"paidSupport":true,"collaboration":true,"allowChildOrgs":true,"enterpriseEula":true,"partners":["acs","analytics"],"_version":1,"_token":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpZCI6IjU0ZDhlNGFiY2U3ODgxNWQ4MTEwNGNiNCIsIm5hbWUiOiJFbnRlcnByaXNlIiwiYXBpUmF0ZU1vbnRoIjoxMDAwMDAwMDAsInB1c2hSYXRlTW9udGgiOjEwMDAwMDAwMCwic3RvcmFnZUZpbGVzR0IiOjEwMDAsInN0b3JhZ2VEYXRhYmFzZUdCIjoxMDAsImNvbnRhaW5lclBvaW50cyI6OTk5OSwiYXJyb3dQdWJsaXNoIjp0cnVlLCJldmVudFJhdGVNb250aCI6MTAwMDAwMDAwLCJkYXlzRGF0YVJldGFpbmVkIjo3MzEsImFsbG93UHJvZHVjdGlvbiI6dHJ1ZSwiYXBwRGVzaWduZXIiOnRydWUsImFwcFByZXZpZXciOnRydWUsImh5cGVybG9vcCI6dHJ1ZSwibmF0aXZlU0RLIjp0cnVlLCJwcmVtaXVtTW9kdWxlcyI6dHJ1ZSwicGFpZCI6dHJ1ZSwicGFpZFN1cHBvcnQiOnRydWUsImNvbGxhYm9yYXRpb24iOnRydWUsImFsbG93Q2hpbGRPcmdzIjp0cnVlLCJlbnRlcnByaXNlRXVsYSI6dHJ1ZSwicGFydG5lcnMiOlsiYWNzIiwiYW5hbHl0aWNzIl0sIl92ZXJzaW9uIjoxfQ.UKJJtdCZT4-cNFRvIlfgf2rigeO-AJWlTY6Co1PQ1Kk"},"packageId":"54d8e4abce78815d81104cb4"},"invalidated":false,"enterpriseEula":true,"eulaRequired":true,"user":{"_id":"58d09dfed95b7d001c0162b2","email":"[email protected]","firstname":"Administrator","lastname":"User","is_staff":true,"active":true,"activated":true,"guid":"17bddb9a-b87b-42cc-aceb-c61c7ca08d58","disable_2fa":true,"created":"2017-03-21T03:29:02.294Z","updated":"2017-03-21T16:04:25.733Z","keepMeSignedIn":false,"last_logged":"2017-03-21T16:04:25.731Z","logged_in_count":4,"last_logged_in_org":985549229695766,"last_browser_language":"en","metadata":{},"logged_in_from_cli":true,"is_support":false},"role":"admin","nodeacs":false,"osFamily":"Mac OS X","_stoked":1490115164740,"os":"mac os x","client_cert_required":false}}' +275ms 2017-03-21T16:52:44.848Z | TRACE | setting org: My Organization 2017-03-21T16:52:44.849Z | DEBUG | Login to Arrow Cloud/ACS... appc:cli Arrow cloud login request: https://admin.cloudapp-1.appctest.com/login +4ms appc:cli Arrow cloud login response: { code: 401, message: 'Unauthorized' } {"success":false,"errcode":123,"message":"Please provide Appcelerator 360 Session ID or username and password to login!","clusterVersion":"1.6.0"} +290ms 2017-03-21T16:52:45.140Z | TRACE | 401 '{"success":false,"errcode":123,"message":"Please provide Appcelerator 360 Session ID or username and password to login!","clusterVersion":"1.6.0"}' 2017-03-21T16:52:45.141Z | TRACE | getCredentials() session: {} 2017-03-21T16:52:45.142Z | ERROR | Error: Error attempting to login to Arrow Cloud. at Request._callback (/Users/ingo/.appcelerator/install/6.2.0-master.25/package/lib/commands/login.js:354:19) at Request.self.callback (/Users/ingo/.appcelerator/install/6.2.0-master.25/package/node_modules/request/request.js:188:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7) at Request.<anonymous> (/Users/ingo/.appcelerator/install/6.2.0-master.25/package/node_modules/request/request.js:1171:10) at emitOne (events.js:77:13) at Request.emit (events.js:169:7) at IncomingMessage.<anonymous> (/Users/ingo/.appcelerator/install/6.2.0-master.25/package/node_modules/request/request.js:1091:12) at IncomingMessage.g (events.js:260:16) at emitNone (events.js:72:20) appc:run signal received +44s exit sending to ChildProcess { {code} | 3 |
225 | CLI-1175 | 03/21/2017 23:47:36 | appc-cli/Gruntfile.js is not loading "grunt-bump" | In https://github.com/appcelerator/appc-cli/blob/master/Gruntfile.js, needs to load {{grunt-bump}} i.e. {{grunt.loadNpmTasks('grunt-bump');}}. | 1 |
226 | CLI-1176 | 03/22/2017 13:34:42 | appc -v with no cores installed throws TypeError | h5.Description *This only occurs in Node 6 and greater* When running {{appc -v}} on a machine with no cli cores installed the cli will error with the below. {code} path.js:7 throw new TypeError('Path must be a string. Received ' + inspect(path)); ^ TypeError: Path must be a string. Received true at assertPath (path.js:7:11) at Object.join (path.js:1211:7) at Object.getInstallBinary (/usr/local/lib/node_modules/appcelerator/lib/util.js:282:14) at /usr/local/lib/node_modules/appcelerator/lib/install.js:299:30 at /usr/local/lib/node_modules/appcelerator/lib/install.js:256:3 at /usr/local/lib/node_modules/appcelerator/lib/install.js:103:6 at ChildProcess.exithandler (child_process.js:197:7) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at maybeClose (internal/child_process.js:877:16) {code} h5.Steps to reproduce # Rename ~/.appcelerator/install to ~/.appcelerator/foo # Run {{appc -v}} h5.Actual TypeError is thrown h5.Expected TypeError should not be thrown | 1 |
227 | CLI-1177 | 03/22/2017 18:37:41 | appc-cli build is not passing "appcJs:check" | The appc-cli master branch is not passing {{appcJs:check}} when running Grunt: {code} ~/github/appc-cli$ grunt Running "clean:test" (clean) task >> 0 paths cleaned. Running "appcJs:check" (appcJs) task Running "jshint:src" (jshint) task ✔ No problems Running "jscs:src" (jscs) task bin/appc 114 3 'return' outside of function (114:3) lib/commands/platform.js 1 0 internalError: Error running rule jsDoc: This is an issue with JSCS and not your codebase. Please file an issue (with the stack trace below) at: https://github.com/jscs-dev/node-jscs/issues/new TypeError: Cannot read property 'offset' of undefined at Object.enforceExistence (/Users/wluu/github/appc-cli/node_modules/jscs-jsdoc/lib/rules/validate-jsdoc/enforce-existence.js:116:65) at /Users/wluu/github/appc-cli/node_modules/jscs-jsdoc/lib/rules/validate-jsdoc.js:128:27 at Array.forEach (native) at Object.<anonymous> (/Users/wluu/github/appc-cli/node_modules/jscs-jsdoc/lib/rules/validate-jsdoc.js:127:32) at Array.forEach (native) at Object.JsFile.iterateNodesByType (/Users/wluu/github/appc-cli/node_modules/jscs/lib/js-file.js:331:42) at /Users/wluu/github/appc-cli/node_modules/jscs-jsdoc/lib/rules/validate-jsdoc.js:120:18 at Array.forEach (native) at Object.module.exports.check (/Users/wluu/github/appc-cli/node_modules/jscs-jsdoc/lib/rules/validate-jsdoc.js:112:29) at null.<anonymous> (/Users/wluu/github/appc-cli/node_modules/jscs/lib/string-checker.js:189:22) lib/registry-sdk/index.js 664 10 disallowSpacesInsideArrayBrackets: Illegal space after opening bracket 664 15 disallowSpacesInsideArrayBrackets: Illegal space before closing bracket 673 38 disallowSpacesInsideObjectBrackets: Illegal space after opening curly brace 673 67 disallowSpacesInsideObjectBrackets: Illegal space before closing curly brace 899 9 requireSpaceAfterKeywords: One space required after "catch" keyword 985 6 requireSpaceAfterKeywords: One space required after "catch" keyword lib/session.js 36 61 disallowMultipleLineBreaks: ; and cache this lookup, for the positive should have at most 2 line(s) between them 147 35 disallowMultipleLineBreaks: { and } should have at most 2 line(s) between them 437 32 disallowSpacesInsideObjectBrackets: Illegal space after opening curly brace 437 51 disallowSpacesInsideObjectBrackets: Illegal space before closing curly brace test/lib/remove_test.js 35 0 validateIndentation: Invalid indentation character: >> 13 code style errors found! Warning: Task "jscs:src" failed. Use --force to continue. Aborted due to warnings. {code} This will prevent the appc-cli from building on Jenkins. | 3 |
228 | CLI-1180 | 03/28/2017 14:14:03 | CLI rebuild check should determine if a rebuild is needed from the modules version property in node | h5.Description Currently the rebuild check works off process.version which represents the node version. This rebuild is needed because native modules need to be rebuilt when moving between node versions that have a different ABI version (process.versions.modules), CLI-827. I propose that rather than rebuilding on a node version change the rebuild should be determined from the process.versions.modules version, this should lead to less rebuilds. I admit that it wont get us much other than that though :) From an end user (read customer) standpoint this should be invisible, I do not believe that many users switch between CLIs or node versions that often, the main benefit of this would probably be time savings internally. | 3 |
229 | CLI-1186 | 04/06/2017 17:58:47 | Update appc-cli devDependencies to latest and handle false positive assertions | The {{devDependencies}} in appc-cli should be updated to the latest version: https://github.com/wluu/appc-cli/blob/master/package.json#L123-L136 And after updating the {{devDependencies}} to the latest versions, will need to fix the false positive assertions from the {{should}} module: https://github.com/shouldjs/should.js/wiki/Breaking-changes#changes-for-7x | 2 |
230 | CLI-1187 | 04/10/2017 15:49:51 | Unable to run appc cloud publish | *This is a regression from 6.1.0* *Workaround* Add your global node_modules to the NODE_PATH env variable in your bash_profile (or similar) h5.Description When running {{appc cloud publish}} the CLI will error out with {{\[ERROR\] npm not found. Please install npm and try again.Error: Cannot find module 'npm'}}. Originating from acs [here|https://github.com/appcelerator/arrow-cloud-docker/blob/f657ac582f1fa17e35c36b84865593d7515fc6e8/nettle/lib/util.js#L685]. This works fine when using the acs directly, i.e one installed using npm i acs -g. I believe the require in the gobal install of acs works because when require traverses looks npm, acs has added the necessary directory to NODE_PATH [here|https://github.com/appcelerator/arrow-cloud-docker/blob/ae6b4951889ebb82364dd741a3cbf2315a14fdf4/nettle/lib/nettle.js#L20-L26] it ensures my NODE_PATH includes the global node_modules directory, however when this is run in the context of the appc cli all it does is add {{/Users/eharris/.appcelerator/install/6.2.0-master.54/package/node_modules}} to my NODE_PATH. npm being required from the global space can be confirmed by 1. Edit the require to the below, check the log. It will point to your global npm install {code} var npm = require.resolve('npm'); console.log(npm); {code} 2. Change the folder name of the global npm to something that isn't npm. The global acs will now no longer work This may just be a documentation issue and a duplicate of NODEJS-2851 h5.Steps to reproduce # Run appc cloud publish in a directory h5.Actual results The CLI will error out with {{\[ERROR\] npm not found. Please install npm and try again.Error: Cannot find module 'npm'}} h5.Expected results No error or output that can inform a user/point a user to how to rectify the issue | 1 |
231 | CLI-1195 | 04/26/2017 01:28:51 | Pass app original org_id with every build upload | https://github.com/appcelerator/appc-cli-titanium/pull/217 | 1 |
232 | CLI-1197 | 05/03/2017 23:38:12 | Appc CLI integration tests can't handle alphanumeric authorization code | In production, the Appc CLI integration tests can't handle alphanumeric authorization code from 360. This issue is purely on the integration tests side i.e you can still enter the alphanumeric code manually when prompted. | 3 |
233 | CLI-1203 | 05/09/2017 21:36:24 | Emojis should be removed from Appc CLI NPM | *Details:* Since majority of our customers are (and will be) from the enterprise space, having emojis in our Appc CLI NPM seems unprofessional; see [^emojis.png]. Emojis should be removed from Appc CLI NPM. *Steps to reproduce:* # Run {{appc use <CORE_VER>}} # When the CLI starts downloading, immediately press {{ctrl+c}} to cancel the download *Actual:* Emojis will appear when you abort the download; see [^emojis.png]. | 1 |
234 | CLI-1207 | 05/12/2017 00:26:12 | Update appc-platform-sdk dependency to ~2.1.3 in appc-cli-titanium | . | 1 |
235 | CLI-1208 | 05/12/2017 21:52:34 | appc run removes last arg | Last option is removed from the command. {code} // --build-only is removed > appc run -p ios --build-only Command /usr/local/bin/node /Users/feonsua/.appcelerator/install/6.2.1/package/node_modules/titanium/lib/titanium.js build run -p ios --config-file /var/folders/mc/fcb2h6g10_b_9jx5v5qq3z6m0000gp/T/build-1494622257561.json --log-level info --no-banner --project-dir /Users/feonsua/work/testapps/test {code} | 1 |
236 | CLI-1213 | 05/19/2017 20:50:41 | Include Alloy 1.10.* | [email protected] introduced ES6 support in controller. https://jira.appcelerator.org/browse/ALOY-1312 | 0 |
237 | CLI-1215 | 05/23/2017 20:14:34 | appc-install improve subprocess npm rebuild | Use spawn instead of exec for cleaner code and not worry about buffer overflow. https://github.com/appcelerator/appc-install/pull/75 | 3 |
238 | CLI-1219 | 05/24/2017 00:38:15 | LiveView: Upgrade to handle ES6 sytax | h5.Description When using ES6 syntax in an application LiveView will currently error out (however you wont see LiveView error out because of TIMOB-24694). It's possible we could just update the acorn to a newer version allowing ES6 (and newer) code, but # We don't own the package https://www.npmjs.com/package/jsparse-tools # The repo doesnt exist (or is private) We could grab the source from an npm install and update where necessary, I believe MIT allows this. *Notes* I had a quick try of updating to the latest acorn version and these were my observations # The return data from the detect function stays the same across versions, so the acorn upgrade should not problematic # Using const will throw an error, this seems to be because LiveView makes some assumptions about the length of a variable declaration, let works (let and var are both 3 characters long). (https://github.com/appcelerator/liveview/blob/de6bb766edf10b83e28e5f941528d420ef50798d/lib/fserver.js#L314-L324) #* There is a note about usage of const in the docs but I cannot track down the origins of this warning https://wiki.appcelerator.org/display/guides2/LiveView#LiveView-Troubleshooting # This is only run for app.js files I believe | 3 |
239 | CLI-1226 | 06/12/2017 17:54:17 | Automate AppSpider test | We need to test our APIs using AppSpider and upload the results # Using the AppSpider Application, run a scan manually (https://axway.jiveon.com/docs/DOC-80884) against the REST endpoint for preproduction ## URL: http://software-preprod.cloud.appctest.com/arrow/swagger.json ## Inside the AppSpider application, import the Swagger document ## Configure the scan and run it once manually. Save the configuration. # https://axway.jiveon.com/groups/product-security-group/blog/2016/10/14/automating-appspider-and-nessus-with-hakbot ## Recommend copying the Fortify scans to run this nightly: https://github.com/appcelerator/jenkins_dsl/tree/master/fortify-jobs | 5 |
240 | CLI-1229 | 06/16/2017 22:04:46 | Rename appc new options | As part of product rebranding and renaming initiative we need the following changes to the "appc new" command: !image-2017-06-16-17-02-32-741.png|thumbnail! This should not affect any existing functionality. | 2 |
241 | CLI-1230 | 06/16/2017 22:12:18 | Update create arrow app command | As part of the product rebranding and renaming initiative, we are replacing the "Arrow" name. appc new -t arrow should be replaced with appc new -t api !image-2017-06-16-17-07-49-385.png|thumbnail! Should be backward compatible so the previous scripting that used "arrow" should continue to work. Alias approach is OK. | 1 |
242 | CLI-1232 | 06/19/2017 15:27:54 | Update descriptions in appc cloud -help (ACS CLI) | Rename some of the descriptions in the ACS CLI help to refer to new naming Specific lines: Function: Cloud/ACS command line interface and app runner Usage: cloud/acs [COMMAND] [COMMON OPTIONS] [COMMAND OPTIONS] login to the API Runtime cloud logout of the API Runtime cloud restart an app from the API Runtime cloud. If no appname provided it can run in app dir or with -d to specify an app dir. | 0 |
243 | CLI-1233 | 06/20/2017 21:52:53 | If you build appc-cli with NPM 3.X and Node 6.10.3, then you will get ""listener" argument must be a function"" when creating a mobile project | *Details:* If you build appc-cli with NPM 3.X and Node 6.10.3, then you will get {{"listener" argument must be a function}} error when creating a mobile project. *Notes:* * This bug will appear when our (or ECD's) Jenkins build system start using NPM 3.X and Node 6.X to build appc-cli. * To *workaround* the issue, you will need to use the {{--legacy-bundling}} flag: {{npm install --production --legacy-bundling}} * On Jenkins, you will need to replace this line with the above command: https://github.com/appcelerator/jenkins_dsl/blob/master/jobs/appc_cli.groovy#L55 *Technical Notes:* * It seems like the {{wrap}} function from {{lib/logger.js}} (https://github.com/appcelerator/appc-cli/blob/master/lib/logger.js#L99) is being destroyed when {{lib/core.js}} is processing {{node_modules/arrow/lib/plugin/new.js}}; specifically, here: https://github.com/appcelerator/appc-cli/blob/master/lib/core.js#L230 *Steps to reproduce:* # Clone https://github.com/appcelerator/appc-cli # From terminal, run the following commands in the appc-cli repo: {code} # you don't need to delete this if this is your first time cloning the repo rm -rfv node_modules # you can move the json file instead of deleting it rm npm-shrinkwrap.json # at this point, you're performing a simplified version of what Jenkins does starting here: https://github.com/appcelerator/jenkins_dsl/blob/master/jobs/appc_cli.groovy#L55 npm cache clean npm install --production npm prune npm shrinkwrap npm install npm-bundle node ./node_modules/npm-bundle/bin/cli.js {code} # After the tarball is created, create a folder in {{~/.appcelerator/install}} and name it the version from the package.json file i.e. the {{version}} property. # Untar the tarball and move the {{package}} folder to the folder created in the above step # Run {{appc use <VER_YOU_PREV_CREATED>}} # Run {{appc new --name monkey --id com.appc.monkey --type titanium --force --no-services -l trace}} *Actual:* The following error will appear (also, see attached log for full stack trace): {code} 2017-06-20T20:30:11.611Z | ERROR | An uncaught exception was thrown! "listener" argument must be a function 2017-06-20T20:30:11.612Z | ERROR | "listener" argument must be a function 2017-06-20T20:30:11.613Z | TRACE | TypeError: "listener" argument must be a function at _addListener (events.js:216:11) at Socket.addListener (events.js:276:10) at Socket.Readable.on (_stream_readable.js:687:35) at /Users/wluu/.appcelerator/install/6.2.3-master.8/package/node_modules/appc-cli-titanium/plugins/new.js:207:13 at proceed (/Users/wluu/.appcelerator/install/6.2.3-master.8/package/node_modules/appc-cli-titanium/plugins/util.js:221:3) at /Users/wluu/.appcelerator/install/6.2.3-master.8/package/node_modules/appc-cli-titanium/plugins/util.js:193:3 at /Users/wluu/.appcelerator/install/6.2.3-master.8/package/node_modules/appc-cli-titanium/plugins/util.js:88:3 at /Users/wluu/.appcelerator/install/6.2.3-master.8/package/node_modules/appc-cli-titanium/plugins/util.js:78:3 at ChildProcess.exithandler (child_process.js:195:7) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at maybeClose (internal/child_process.js:886:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 2017-06-20T20:30:11.614Z | TRACE | Sending exit signal to titanium process: 26013 {code} *Expected:* You should be able to create mobile project regardless how app-cli is built. | 1 |
244 | CLI-1236 | 06/22/2017 06:18:10 | Trim any spaces from auth code entered for two-factor verification | UX team has recommended that we make a change to the CLI to trim and spaces from the auth code as part of the two-factor verification step. An extra space is added when users copy and paste the auth code from their emails. Links for the Usability teardown [Usability Study #1|https://axway.jiveon.com/docs/DOC-100696] [Usability Study #2|https://axway.jiveon.com/docs/DOC-100695] | 1 |
245 | CLI-1241 | 06/30/2017 19:09:34 | appc login --host option is not recognized | {{appc login --host \[dashboard url\]}} doesn't recognize the custom host option. | 2 |
246 | CLI-1246 | 07/18/2017 07:00:20 | Remove duplicated -v parameter in appc-cli help | in [CLI-675] we added CLI options -v (--vpc-env). However, this conflicts with the short -v option. It appears the simplest approach is to just remove the -v short form for -vpc-env, since that wouldn't have worked. | 1 |
247 | CLI-1250 | 08/02/2017 15:26:10 | Add support for allowing a proxy pac file to be specified in configuration | h5.Description Some customers are behind a proxy where they use a proxy PAC file, when using the Appc CLI this can lead to a bad UX where the customer may have two possible proxy URLs and only through trial and error can they tell which URL will work, a working URL can also go to not working without easy warning also. There are node packages that exist to allow resolving a proxy URL from a given PAC file, for example https://www.npmjs.com/package/pac-proxy-agent, I'm not sure how useful this would be and whether this problem is better solved in a lower level module such as request itself Example usage I would imagine this would be similar to the CA File support we have, so setting it would be set in the appc config like so {{appc config set proxypac C:\Users\Ewan\proxy.pac}} | 5 |
248 | CLI-1253 | 08/03/2017 19:10:59 | Unable to do appc config without appc core | This is only happens when setting up CLI for the first time. After npm install appcelerator, there's no way to set config values, i.e. proxyServer, cafile, through {{appc config}} command. This is an issue for users try to setup CLI behind proxy. Workaround is to use environment variables. | 5 |
249 | CLI-1263 | 09/12/2017 08:05:21 | appc cli include acs cli 2.0.6 | We have just upgraded tiger to 1.6.0 and released latest acs cli 2.0.6. Can you please include the latest acs cli? | 0 |
250 | CLI-1273 | 10/16/2017 23:24:22 | Ti.Database.execute() should return null when no results are found | - Our current {{ti.database.test.js}} test case is failing - {{Titanium.Database.execute()}} should return {{null}} when no results are found *TEST CASE* {code:js} var db = Ti.Database.install('made.up.sqlite', 'category'), rows = db.execute('pragma table_info(\'category\');'); Ti.API.info('rows: ' + JSON.stringify(rows, null, 2)); db.remove(); {code} | 3 |
251 | CLI-1278 | 11/13/2017 18:58:15 | Android build always enables JavaScript encryption | Subsequent Android builds always have the {{encryptJS}} flag set to true when writing the build manifest, regardless of current deployment type. *Steps to reproduce the behavior* # Run a clean build # Run the app a second time without any changes *Actual behavior* Second build and onwards always forces a full rebuild indicated by the following logs: {code} [INFO] Forcing rebuild: JavaScript encryption flag changed [INFO] Was: true [INFO] Now: false {code} *Expected behavior* The build does an incremental build instead of a full rebuild. The above log message should not appear. | 1 |
252 | CLI-1279 | 11/14/2017 22:29:47 | Include API Builder 3.* | Bump API Builder major version. | 1 |
253 | CLI-1280 | 11/14/2017 23:34:18 | CLI: Cannot create projects when using 7.0.0-master.11 | When using CLI 7.0.0-master.11, I am unable to create a new project. I get the below error: {code} ? What's your application id (example: com.myapp)? com.appc.appid An uncaught exception was thrown! "listener" argument must be a function "listener" argument must be a function {code} *Steps to reproduce issue* 1. Create a new project with {{appc new}} 2. Enter valid project information *Expected Results* The project is created successfully *Actual Results* Project creation fails with the above error after entering the app id | 0 |
254 | CLI-1283 | 11/17/2017 05:53:06 | appc use pre-release versions are not listed numerically | This is triggering my ocd. {code} > feonsua$ appc use --prerelease The following versions are available: 7.0.0-master.13 Installed 7.0.0-master.19 Not Installed 7.0.0-master.8 Not Installed 7.0.0-master.26 Installed 7.0.0-master.5 Not Installed 7.0.0-master.2 Not Installed 7.0.0-master.6 Not Installed 7.0.0-master.12 Not Installed 7.0.0-master.4 Not Installed 7.0.0-master.27 Installed (Active) 7.0.0-master.18 Installed 7.0.0-master.23 Not Installed 7.0.0-master.11 Not Installed 7.0.0-master.25 Not Installed 7.0.0-master.24 Not Installed 7.0.0-master.20 Not Installed 7.0.0-master.3 Not Installed 7.0.0-master.22 Not Installed 7.0.0-master.1 Not Installed 7.0.0-master.7 Not Installed {code} Perhaps an ascending sort will create a better experience. Especially when the list is long, it is a pain to keep scrolling up to see the latest version. {code} 6.3.0-master.16 Not Installed 7.0.0-master.1 Not Installed 7.0.0-master.2 Not Installed 7.0.0-master.3 Not Installed 7.0.0-master.4 Not Installed 7.0.0-master.5 Not Installed 7.0.0-master.6 Not Installed 7.0.0-master.7 Not Installed 7.0.0-master.8 Not Installed 7.0.0-master.11 Not Installed 7.0.0-master.12 Not Installed 7.0.0-master.13 Installed 7.0.0-master.18 Installed 7.0.0-master.19 Not Installed 7.0.0-master.20 Not Installed 7.0.0-master.22 Not Installed 7.0.0-master.23 Not Installed 7.0.0-master.24 Not Installed 7.0.0-master.25 Not Installed 7.0.0-master.26 Installed 7.0.0-master.27 Installed (Active) > feonsua$ {code} | 2 |
255 | CLI-1285 | 11/20/2017 13:47:10 | "appc use" must stop the daemon, if present, prior to switching core | We need {{appc use}} to stop the daemon prior to switching the core so that the old daemon code will no longer be used. Here's the basic steps 1. Switch to the new core 2. Check if the new core has {{appcd}} - If it does, run {{appcd stop}} | 2 |
256 | CLI-1287 | 11/21/2017 07:41:48 | CLI Core 7.0.0-master.34 fails to install "ioslib/node-ios-device" with error | h5.Steps to reproduce: 1. Go to preprod & run {code} appc use 7.0.0-master.34{code}. h5.Actual results: 1. Core installation goes well but it fails at installing {{ioslib/node-ios-device}}. {code} Finding version 7.0.0-master.34 ... ✓ Validating security checksum ✓ Installing ... ✓ Compiling platform native modules ... └ alloy/deasync ... ✓ └ external-editor/spawn-sync ... ✓ └ bunyan/dtrace-provider ... ✓ └ package/appcd ... ✓ └ ioslib/node-ios-device ...Failed to install node-ios-deviceundefined; it may not support your current OS. └ bunyan/dtrace-provider ... ✓ └ axway-flow/jsonpath ... ✓ └ bunyan/dtrace-provider ... ✓ └ ldapjs/dtrace-provider ... ✓ Installed!! {code} h5.Expected results: 1. Core installation should not error installing {{ioslib/node-ios-device}}. | 1 |
257 | CLI-1289 | 12/05/2017 16:35:45 | Update AppPreview hook | https://jira.appcelerator.org/browse/PREVIEW-24 CLI needs to update {{appc-app-preview}} once the hook's URL is updated and ssl cert set up correctly. | 1 |
258 | CLI-1290 | 12/11/2017 14:58:50 | npmconf causing errors when resolving plugins | The following error appears when running arrow tests. (which exec an appc run -l trace from a generated project) I never fully traced down the location of the issue in npmconf, but running the app generated by the tests directly does not show this error, so it's possibly something to do with the cwd. {code} invalid config https-proxy=undefined invalid config Must be a full url with 'http://' invalid config loglevel="notice" invalid config proxy=undefined invalid config Must be a full url with 'http://' 2017-12-11T12:57:53.912Z | ERROR | Error: ENOENT: no such file or directory, open 'C:\Users\ahurst\AppData\Local\Temp\arrow-tmp\arrow_test_1512997071265.36.229339544800695\undefined' {code} These config options which are causing the error are npm defaults, however, and not set directly by me. The error is being thrown by the npmconf module, which is now deprecated with warnings of _Do not use this package._. While the suggested alternative is to use npm for this check, I don't feel like having npm as a dependency is a good idea, and I don't think that it is expected. Other packages seem to be using https://github.com/kevva/npm-conf instead. I've created a branch which uses npm-conf instead of npmconf and this no longer throws errors or emits warnings. | 3 |
259 | CLI-1296 | 01/03/2018 14:34:54 | Bump min node version to 8.1.2 or 8.9.0 ( first LTS version) | h5.Description There's an issue with Node 8.0.0 - 8.1.1 that is seen when building Titanium apps (https://github.com/archiverjs/node-archiver/issues/236) this is fixed in Node 8.1.2, I've seen a few people on slack be burned by this, I propose we bump our minimum required node in appc-install to either 8.1.2 or 8.9.1. | 0 |
260 | CLI-1305 | 02/26/2018 17:20:44 | Error thrown when an uncaughtException is thrown by the CLI process | h5.Description When an uncaughtException occurs in the CLI it's possible the CLI will actually error out with the below, we just need to check if logger exists before using it like the other instances. {code} C:\Users\build\.appcelerator\install\7.0.2\package\bin\appc:182 logger.error('An uncaught exception was thrown!'); ^ TypeError: Cannot read property 'error' of undefined at process.uncaughtException (C:\Users\build\.appcelerator\install\7.0.2\package\bin\appc:182:9) at emitOne (events.js:116:13) at process.emit (events.js:211:7) at process._fatalException (bootstrap_node.js:374:26) {code} h5.Steps to reproduce # Cause an uncaught exception in the CLI (TODO) h5.Actual An error in our code is logged, causing us to lose the uncaughtException error h5.Expected Exception should be logged | 8 |
261 | CLI-1306 | 02/26/2018 21:13:03 | Information link about replacing ArrowDB keys is dead | h5.Description When importing an existing app using {{appc new --import}} a short-link is printed out that informs a user the impact of replacing arrowdb app keys in the tiapp, the page in 360 no longer exists. Side note that we also need to replace arrowdb/acs with MBS (I think?) Link redirects to https://platform.axway.com/#/product/migrate-app {code} ? Would you like to enable native API access with Hyperloop for this app? No ? The app has ArrowDB (previously known as ACS) keys already defined. Would you like to replace them? Refer to http://appcel.us/1Gcby7G for more details. No {code} h5.Steps to reproduce # Create an app with services enabled # Import the app using {{appc new --import}} # Go to the link printed to understand the impact of replacing arrowdb keys in the tiapp h5.Actual Dead link h5.Expected A link with information | 0 |
262 | CLI-1309 | 02/27/2018 18:29:38 | Include [email protected] for CLI is unable to recognise JDK 9 fix | (Note JDK 9 is not supported yet, ticket is for reference) When trying to set {{java.home}} in the CLI to JDK 9 using {{appc ti config java.home path/to/jdk}}. The CLI does not set it to JDK 9 and instead will revert back to 1.8. (switching from 1.7 to 1.8 and vice versa works as expected) *Test Steps* 1. Download JDK 9 2. Use the CLI to set java.home to JDK 9 using {{appc ti config java.home path/to/jdk}} 3. Run {{appc info}} 4. Note that the CLI does not recognise it and reverts back to an older JDK version *Actual result* Should be able to switch to JDK 9. | 1 |
263 | CLI-1308 | 03/13/2018 22:57:13 | 'appc use' offline doesn't show installed versions | **Reproduce Step** 1. make sure you have appc core installed 2. run {{appc use}} offline **Actual Result** {{TypeError: Cannot read property 'version' of undefined}} **Expected Output** Installed appc core should be listed. | 2 |
264 | CLI-1312 | 04/10/2018 01:13:36 | Can't start appc daemon with 7.0.3-master.36 | This appears to be a regression. Not seen in 7.0.3-master.34. I did not find any changes merged which would have caused this issue but not 100% sure. h5.Steps to reproduce: 1. Install appc core 7.0.3-master.36. 2. Run {code}DEBUG=* appc appcd start{code}. (Daemon was not running after I installed the core). h5.Actual results: 1. Daemon start fails: https://gist.github.com/lokeshchdhry/3340ef8fd04d074b7eb2838885234fdf h5.Expected results: 1. Daemon should start successfully. | 1 |
265 | CLI-1314 | 04/19/2018 19:06:30 | ABC: Issue enabling cloud and performance services for new apps | H5.Customer created a new app called BackupTest in VPC-Prod today. He selected enable Axway platform services but, cloud and performance services were not enabled. I tried to enable them again by clicking the enable services and still didn't work. After clicking it 4 times, finally the performance is enabled but, the cloud is still not getting enabled. He created another new app testBackup and this time it worked fine. but is still not able to enable the cloud service for the previous app. I've attached the configuration file for their environment. | 5 |
266 | CLI-1319 | 07/02/2018 18:08:24 | Reduce number of vulnerabilities found by npm audit | h5.Description Currently npm audit shows the following number of vulnerabilities, {{found 39 vulnerabilities (14 low, 15 moderate, 7 high, 3 critical) in 920 scanned packages}}. Note that some of these are only dev dependencies, but we should try and fix as many as possible. The npm audit output is pretty noisy so here's a reduced version of modules that will need updating, assume that the version bump is in range unless noted {code} grunt-appc-js (semver major, will need linting fixes I imagine) pac-proxy-agent (semver major) tar (semver major) request mocha (semver major) grunt lodash {code} | 5 |
267 | CLI-1321 | 07/23/2018 23:37:44 | Hyperloop: Windows platform is not added to tiapp.xml | {{<module platform="android">hyperloop</module>}} is only added on creation, if you add it after creation android and windows are added. *Steps to reproduce* # Create a new application in studio with services and hyperloop *Error* Only {{<module platform="android">hyperloop</module>}} is added on creation. *Expected* {{<module platform="windows">hyperloop</module>}} is not added on creation. | 1 |
268 | CLI-1324 | 08/23/2018 16:34:55 | [Windows] Unable to install latest version of the CLI (7.0.6-master.5) | When trying to install latest version of the CLI on pre-prod the installation seems to get stuck. *Test Steps* # Make sure you are on pre-prod # Use {{appc use --prerelease}} to see all releases # Use {{appc use 7.0.6-master.5}} to get the latest version *Expected* CLI should install without any issues *Actual* CLI gets stuck on "Installing" *Note:* Seems to have been broken since {{7.0.6-master.2}} on Windows. | 8 |
269 | CLI-1326 | 08/24/2018 05:09:35 | Fix tar extraction method | - Our core CLI {{tar}} bundles are failing to extract on Windows - To fix this we can simplyify the {{targz}} method in the installer to only use the {{tar}} module | 3 |
270 | CLI-1343 | 08/24/2018 07:54:29 | Android: Setting "appc-sourcecode-encryption-policy" to "remote" crashes on startup as of 7.3.0 | This issue was reported via the [7.3.0 announcement blog post|https://www.appcelerator.com/blog/2018/08/ga-release-titanium-sdk-7-3-0-cli-7-0-5/]: {quote} App fail to run with the following error [ERROR] : V8Exception: Exception occurred at ti:/invoker.js:101: Uncaught Error: abstract method “java.lang.String[] org.appcelerator.kroll.util.KrollAssetHelper$AssetCrypt.getAssetPaths()” {quote} | 13 |
271 | CLI-1328 | 09/12/2018 18:27:29 | AppC CLI --no-prompt flag broken. | I run this following command in appcelerator CLI: {code} appc login --no-prompt --username [email protected] --password passcode {code} Expected behavior: {code} I expect: to get an error (a non-0 return value) {code} But I'm getting this from CLI: {code} Appcelerator Command-Line Interface, version 7.0.2 Copyright (c) 2014-2018, Appcelerator, Inc. All Rights Reserved. login failed, please try again Appcelerator Login required to continue ... ? Appcelerator ID: {code} I did not get return any error code. Instead, CLI prompts me to get logged in once again. Though I did check it in 7.0.6, I have got same results. | 1 |
272 | CLI-1330 | 09/18/2018 07:57:34 | appc use --prerelease -o json will try to download version json | h5.Description When running {{appc use --prerelease -o json}} or {{appc use --prerelease --output json}} the cli will try to download a core version of json, using {{appc use -o json --prerelease}} or {{appc use --output json --prerelease}} will do the correct thing and list the version info. h5.Steps to reproduce 1. Run {{appc use --prerelease -o json}} h5.Actual An attempt is made to download version "json" h5.Expected The version info should be listed | 3 |
273 | CLI-1340 | 01/03/2019 18:44:18 | Login error when using Node 10 in Windows | On a fresh Windows 10 installation I've installed Node 10, Java 8, the Android SDK and the Appcelerator parts with {{npm install -g appcelerator titanium alloy}}. The open source version works fine but when trying to login to my appc account it will stop during the login part. *appc info* {code} Appcelerator Command-Line Interface, version 7.0.9 Copyright (c) 2014-2019, Appcelerator, Inc. All Rights Reserved. Operating System Name = Microsoft Windows 10 Home Version = 10.0.17134 Architecture = 64bit # CPUs = 12 Memory = 15.7GB Node.js Node.js Version = 10.15.0 npm Version = 6.4.1 Appcelerator CLI Installer = 4.2.13 Core Package = 7.0.9 Titanium CLI CLI Version = 5.1.1 node-appc Version = 0.2.44 Titanium SDKs 7.5.0.GA Version = 7.5.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\7.5.0.GA Platforms = android, windows git Hash = 2e5a7423d0 git Timestamp = 11/15/2018 21:50 node-appc Version = 0.2.47 Intel® Hardware Accelerated Execution Manager (HAXM) Not installed Java Development Kit Version = 1.8.0_191 Java Home = C:\Program Files\Java\jdk1.8.0_191 Genymotion Path = not found Genymotion Executable = not found Genymotion Player = not found Home = not found VirtualBox Executable = not found Version = unknown Android SDK Android Executable = not found ADB Executable = c:\android\platform-tools\adb.exe SDK Path = c:\android Android NDK NDK Path = not found NDK Version = not found Android Platforms 1) android-23 Name = Android 6.0 API Level = 23 Revision = 3 Skins = HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800, WVGA854, WXGA720, WXGA800, WXGA800-7in ABIs = Path = c:\android\platforms\android-23 2) android-28 Name = Android 9 API Level = 28 Revision = 1 Skins = HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800, WVGA854, WXGA720, WXGA800, WXGA800-7in ABIs = Path = c:\android\platforms\android-28 {code} When running {{appc -l trace setup}} or {{appc -l trace login}} the login will stop at: {quote} Get the registry... {quote} *Workaround* Commenting out these lines: {code} // get the registry function (opts, cb) { log.debug('Get the registry...'); return registry.getValue('registry', opts, cb); }, {code} in install\7.0.9\package\lib\commands\login.js will skip the registry part and the login will continue up to the end. | 5 |
274 | CLI-1344 | 02/05/2019 23:37:30 | Packaging module with CLI 7.0.10-master.7 throws uncaught exception error | *Steps To Reproduce:* 1.Create a new mobile module project from command line 2. Build it for android or iOS from CLI *Expected:* Module should be packaged successfully. *Actual:* 2019-02-05T23:09:08.817Z | DEBUG | Titanium Downloads Last Checked: 1549391907761 2019-02-05T23:09:08.817Z | ERROR | An uncaught exception was thrown! tiapp.xml not found 2019-02-05T23:09:08.818Z | ERROR | tiapp.xml not found 2019-02-05T23:09:08.818Z | TRACE | Error: tiapp.xml not found at Object.load (/Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/tiapp.xml/lib/tiapp.xml.js:57:9) at updateConfig (/Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/appc-cli-titanium/plugins/run.js:68:26) at Object.getTiConfig (/Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/appc-cli-titanium/plugins/util.js:177:9) at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/appc-cli-titanium/plugins/run.js:44:8 at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/appc-cli-titanium/plugins/util.js:713:11 at fn (/Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/async/lib/async.js:746:34) at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/async/lib/async.js:1213:16 at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/async/lib/async.js:166:37 at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/async/lib/async.js:706:43 at /Users/kmahalingam/.appcelerator/install/7.0.10-master.7/package/node_modules/async/lib/async.js:167:37 Command used: {code} appc new appc ti build -p ios --buildonly {code} *Note:* This is not happening with 7.0.10 master 6 CLI | 2 |
275 | CLI-1346 | 02/12/2019 22:34:08 | Improve the CLI install flow | h5.Description Currently the CLI install process does the following looks for packages that contains native modules and reinstall them. For example, appcd contains a native module, so whenever I download the appc cli, the appcd version in the CLI is reinstalled. We have mostly operated on the basis that a CLI distribution is locked down, but by reinstalling a package we're effectively recreating the dep tree underneath that package, leading to issues like DAEMON-270 I propose that rather than reinstalling the package, we take a similar approach to what's done elsewhere in the CLI where we run {{npm rebuild}} in the root dir. This has two advantages 1) CLIs become locked down "again" as we're just rebuilding native modules, not reinstalling 2) A CLI install becomes much faster I believe, on my machine a rebuild is way faster than an install | 5 |
276 | CLI-1347 | 02/20/2019 13:43:48 | "componentForDownload is not defined" error when running a project | h5.Description I tried to build a project, and hit the following error {code} 2019-02-20T13:36:51.288Z | ERROR | Error: ReferenceError: componentForDownload is not defined at /Users/eharris/.appcelerator/install/7.0.10-master.16/package/node_modules/appc-cli-titanium/plugins/util.js:683:15 at Request._callback (/Users/eharris/.appcelerator/install/7.0.10-master.16/package/node_modules/appc-cli-titanium/node_modules/appc-platform-sdk/lib/index.js:137:11) at Request.self.callback (/Users/eharris/.appcelerator/install/7.0.10-master.16/package/node_modules/request/request.js:185:22) at emitTwo (events.js:126:13) at Request.emit (events.js:214:7) at Request.<anonymous> (/Users/eharris/.appcelerator/install/7.0.10-master.16/package/node_modules/request/request.js:1161:10) at emitOne (events.js:116:13) at Request.emit (events.js:211:7) at IncomingMessage.<anonymous> (/Users/eharris/.appcelerator/install/7.0.10-master.16/package/node_modules/request/request.js:1083:12) at Object.onceWrapper (events.js:313:30) {code} h5.Steps to reproduce 1. Remove the {{lastUpdateCheckTiDownloads}} property from the appc-cli.json 2. Build a project using {{appc run}} h5.Actual Above error h5.Expected No error should occur | 1 |
277 | CLI-1349 | 03/20/2019 10:13:33 | Support passing a custom template directory to alloy new command | h5.Description ALOY-1632 introduced passing a path to a template to the {{alloy new}} command. It would be good to bubble this up to the appc cli. There is an existing {{\-\-testapp}} option that can be used, but it might be better to go with something like {{\-\-template-path}}, it should be clear that this option is only used for Alloy projects | 1 |
278 | CLI-1350 | 04/02/2019 11:30:37 | Update to latest arrow version | h5.Description API Builder team will be updating arrow to handle the recent change to the iconset dashboard ships. We should include this version, the version number is unknown at this time, and it might contain some security fixes too cc [~ahurst] | 1 |
279 | CLI-1352 | 04/19/2019 19:09:42 | Reduce time to check Titanium downloads | - Currently, the CLI checks Titanium downloads when a {{new}} or {{run}} occurs after a 24 hour period. - This is too long, it should re-check after thirty minutes so customers can receive the latest modules shortly after being released. | 3 |
280 | CLI-1354 | 06/06/2019 13:37:20 | Include alloy 1.14.0 | h5.Description We want to include alloy 1.14.0 in the cli 7.1.0 release. Initially we will include the prerelease version {{1.14.0-0}} and then when we're ready we'll cut the release of alloy and include that in the cli. We will need PRs for appc-cli and appc-cli-titanium | 1 |
281 | CLI-1355 | 06/11/2019 04:11:36 | Android "appc run" will always trigger rebuild if "tiapp.xml" is missing encryption policy property | *Summary:* If the "tiapp.xml" file is missing property "appc-sourcecode-encryption-policy", then an Android "appc run" will alway trigger a *rebuild*. This is preventing incremental Android builds from working. *Steps to reproduce:* # Create a default Alloy or Classic app from template. # Build for Android via: {{appc run -p android --build-only}} # Build for Android again using the above command line. # In the build log, notice the following message {code} [INFO] Forcing rebuild: JavaScript files need to be re-encrypted {code} *Cause:* The CLI's {{precompileHook()}} code is wrongly setting the {{AndroidBuilder}} object's "encryptJS" property to {{undefined}} if the "appc-sourcecode-encryption-policy" property was not found. This code should *+only+* set the "encryptJS" field to {{true}} if the encryption policy was found and set to "remote". Otherwise, it should leave the "encryptJS" field alone. [titanium.js#precompileHook()|https://github.com/appcelerator/appc-cli-titanium/blob/cd6a63dbeac0cb6a2327f24e6b2f2e53a54b2984/hook/titanium.js#L216] *Work-around:* Add the following property to the "tiapp.xml" file. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <ti:app xmlns:ti="http://ti.appcelerator.org"> <property name="appc-sourcecode-encryption-policy" type="string">none</property> </ti:app> {code} | 3 |
282 | CLI-1356 | 06/12/2019 14:05:36 | Compiling platform native modules contains more packages than necessary | h5.Description The CLI uses the existence of a postinstall step as a method of determining that a module is a native module. This isn't always the case as packages such as core-js use this as a method of gathering contributions, this doesn't cause any problems but it's a minor cosmetic issue and might cause a slight speed reduction in install time {code} $appc use 7.0.12-70X.4 Before you can continue, the latest Appcelerator software update needs to be downloaded. Finding version 7.0.12-70X.4 ✓ Validating security checksum ✓ Installing ✓ Compiling platform native modules └ babel-register/core-js ✓ └ babel-runtime/core-js ✓ └ babel-runtime/core-js ✓ └ babel-runtime/core-js ✓ └ babel-runtime/core-js ✓ └ external-editor/spawn-sync ✓ └ bunyan/dtrace-provider ✓ └ package/appcd ✓ └ bunyan/dtrace-provider ✓ └ z-schema/core-js ✓ └ z-schema/core-js ✓ └ axway-flow/jsonpath ✓ └ ldapjs/dtrace-provider ✓ └ package/fsevents ✓ {code} | 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.