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
|
|---|---|---|---|---|---|
104 |
DAEMON-161
|
11/17/2017 10:23:59
|
Windows: Visual Studio path is incorrect in the system-info
|
Visual studio path is incorrect in the windows system-info path *Actual:* C: /ProgramFiles(x86)/MicrosoftVisualStudio14.0/ *Expected:* C:\Program Files (x86)\Microsoft Visual Studio 14.0 Same goes for the Windows Phone SDK path *Actual:* C: \ProgramFiles(x86)\MicrosoftSDKs\WindowsPhone\v8.1\ *Expected:* C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1
| 1 |
105 |
DAEMON-162
|
11/17/2017 10:49:36
|
Windows system-info: 10.0 SDK emulators are not shown
|
Windows Phone SDK 10.0 emulators are missing in the windows system-info.
| 3 |
106 |
DAEMON-163
|
11/17/2017 10:54:32
|
Windows OS: /system-info/1.x/info command is not responding
|
/system-info/1.x/info command hangs on the windows machine. It's an intermittant issue. Looks like it's getting into recursive loop on "Detecting devices info"
| 2 |
107 |
DAEMON-166
|
11/17/2017 18:49:22
|
appcd-plugin-android: Plugin activation hangs if no Android SDKs are found
|
If the system does not have any Android SDKs, the detect engine will return an empty array, however since it is initialized to an empty array, there's no change and thus no notifications and the detection hangs. The fix requires a check if the results are empty, then resolve the SDK detection. However in doing this, it exposed a timing bug with NDK detection.
| 8 |
108 |
DAEMON-167
|
11/18/2017 03:39:34
|
Android and Genymotion emulators are empty
|
Android and Genymotion emulators are shown empty on the latest daemon 1.0.0-12 Please find the attached files
| 13 |
109 |
DAEMON-168
|
11/18/2017 03:59:49
|
appId is missing in the provisioning profiles
|
appId is missing in the provisioning profiles
| 1 |
110 |
DAEMON-169
|
11/18/2017 17:25:48
|
Issues with Xcode info returned
|
Couple of issues found in the Xcode information returned when querying "appc appcd exec /ios/latest/info" 1. Any Xcode that is not present in the /Applications is not returned 2. The latest xcode in the system is returned as default even after switching to another xcode for default. Check the attached "appcd.txt " for output of running the "appc appcd exec /ios/latest/info" and the "appcCLI.txt" for output running "appc ti info -t ios" The Xcode in downloads folder was made default but daemon output returns the latest code in /Applications as the default and does not list the Xcode in /downalods
| 3 |
111 |
DAEMON-170
|
11/20/2017 05:41:16
|
Move plugins out of appcd-daemon repo into separate repos
|
Once Appc Daemon 1.0.0 ships, we should move the plugins out of the {{appcd-daemon}} repo and into separate repos. This will allow each plugin to be versioned independently of each other and the Appc Daemon core. Also move {{appcd-default-plugins}} into a separate repo so that we can add/remove plugins without having to publish a new appcd.
| 13 |
112 |
DAEMON-171
|
11/20/2017 05:55:34
|
appcd: Stop any running daemon instances post npm install
|
After installing the Appc Daemon, the post install script should use the just installed Appc Daemon code to stop so that the new code will be run.
| 2 |
113 |
DAEMON-173
|
11/20/2017 16:51:08
|
windowslib: EBUSY error on wptool executable
|
h5.Description When running appcd exec /system-info/1.x/info/ it seemed to be taking longer than usual to return, checking the logs I saw the below, I think it's possible that two detect processes are attempting to build wptool at the same time. We apparently deal with this inside windowslib but it seems to be flaky, it might be wise to stagger the detects to allow one to build before the other runs I've had trouble reproducing this in an appc cli build fwiw {code} 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error Caught exception: Error: EBUSY: resource busy or locked, open 'C:\Users\ewan\Documents\git\appc-daemon\node_modules\windowslib\bin\wptool.exe' 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at Object.fs.openSync (fs.js:646:18) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at Object.fs.writeFileSync (fs.js:1291:33) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at Object.callback (C:\Users\ewan\Documents\git\appc-daemon\node_modules\windowslib\lib\wptool.js:596:7) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at C:\Users\ewan\Documents\git\appc-daemon\node_modules\windowslib\lib\visualstudio.js:423:9 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at Array.forEach (<anonymous>) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at ChildProcess.<anonymous> (C:\Users\ewan\Documents\git\appc-daemon\node_modules\windowslib\lib\visualstudio.js:415:11) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at emitTwo (events.js:126:13) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at ChildProcess.emit (events.js:214:7) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at maybeClose (internal/child_process.js:925:16) 2017-11-20T16:24:57.446Z appcd:plugin:host:21052 error at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) {code} h5.Steps to reproduce # Remove wptool.exe from windowslib/bin folder # Start the daemon {{[appc] appcd start}} # Query system info {{[appc] appcd exec /system-info/1.x/info/}} h5.Actual Plugin hangs, windows error above shown in logs h5.Expected No hang
| 8 |
114 |
DAEMON-176
|
11/21/2017 11:26:20
|
Plugins: Pickup the imported values from the titanium config
|
h5.Description DAEMON-156 implemented importing the ti config, so lets implement it into the plugins. We should also watch the config for these values so we rescan if they get set
| 2 |
115 |
DAEMON-178
|
11/22/2017 06:24:41
|
Sync "appc ti config" with the "appc appcd config"
|
How and when do we sync {{appc ti config}} settings to {{appc appcd config}} - so that when studio is working with Appc Daemon it can only look for {{appc appcd config}} Since everybody is trained to work with {{appc ti config}} and they might configure android.sdkPath, sdk.selected,etc., and expect they will be picked up directly in the studio Any thoughts around it?
| 1 |
116 |
DAEMON-179
|
11/22/2017 10:37:58
|
Android NDK is blank in system-info
|
The android info fetched using "appc appcd exec /android/latest/info" returns Android NDK as blank. Attached is the android output returned by appcd and appc cli
| 8 |
117 |
DAEMON-181
|
11/22/2017 20:02:54
|
appcd-config: Figure out how to set metadata for non-appcd config settings
|
We currently do not have plugins define metadata for plugin specific config options. Plugins do not have access to the main config object, thus they cannot directly add metadata. One solution would be for the plugin system to read a plugin specific metadata config and merge it into the main config.
| 8 |
118 |
DAEMON-182
|
11/22/2017 20:04:58
|
androidlib: Addons with a manifest.ini not detected
|
At some point, Android SDK add-ons moved away from {{source.properties}} files and to a {{manifest.ini}} file. We need to support both.
| 5 |
119 |
DAEMON-184
|
11/23/2017 13:30:01
|
windowslib: Unable to build wptool project on a machine where the username contains spaces
|
h5.Description *This isn't a new bug, just exposed by how we decided to expose appcd* One of my machines has a space in the name, this causes an error when building the wptool executable and we're not in the temp dir, we need to escape the project path correctly
| 5 |
120 |
DAEMON-185
|
11/23/2017 13:31:11
|
Unable to stop the daemon
|
Unable to stop the daemon using {{appc appcd stop}}. It's an intermittent issue - doesn't have all the time. However, it doesn't have any impact on the studio for 5.0 release. {code:java} ITEM-AX40113:titanium_studio kkolipaka$ appc appcd stop --debug Appcelerator Command-Line Interface, version 7.0.0-master.44 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Unable to get server pid Error: Not Found ITEM-AX40113:titanium_studio kkolipaka$ appc appcd stop --debug Appcelerator Command-Line Interface, version 7.0.0-master.44 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Unable to get server pid Error: Not Found ITEM-AX40113:titanium_studio kkolipaka$ appc appcd status Appcelerator Command-Line Interface, version 7.0.0-master.44 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Core Version v1.0.0-22 PID 10760 Uptime 91.35 minutes Node Version 8.9.1 Memory RSS 128.35 MB Memory Heap 39.60 MB / 47.08 MB Filesystem Watch System Nodes 156 Node.js FS Watchers 129 Client Watchers 84 β [d] / (35 files, 0 watchers, 0 links, 0 recursion) βββ¬ [d] Applications (77 files, 1 watcher, 0 links, 0 recursion) β βββ [d] Genymotion.app (1 file, 2 watchers, 0 links, 0 recursion) β βββ¬ [d] Xcode-beta.app (1 file, 3 watchers, 0 links, 0 recursion) β β βββ¬ [d] Contents (14 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Developer (8 files, 1 watcher, 1 link, 0 recursion) β β βββ¬ [d] Platforms (7 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] iPhoneOS.platform (8 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Developer (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Library (5 files, 0 watchers, 0 links, 0 recursion) β β β β βββ¬ [?] CoreSimulator (0 watchers, 0 links, 0 recursion) β β β β βββ¬ [?] Profiles (0 watchers, 0 links, 0 recursion) β β β β βββ [?] DeviceTypes (1 watcher, 0 links, 0 recursion) β β β β βββ [?] Runtimes (1 watcher, 0 links, 0 recursion) β β β βββ [d] SDKs (2 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] iPhoneSimulator.platform (5 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Developer (2 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Library (4 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] CoreSimulator (2 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Profiles (2 files, 0 watchers, 0 links, 0 recursion) β β β βββ [d] DeviceTypes (14 files, 1 watcher, 0 links, 0 recursion) β β β βββ [d] Runtimes (1 file, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] WatchOS.platform (7 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Developer (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Library (1 file, 0 watchers, 0 links, 0 recursion) β β β β βββ¬ [?] CoreSimulator (0 watchers, 0 links, 0 recursion) β β β β βββ¬ [?] Profiles (0 watchers, 0 links, 0 recursion) β β β β βββ [?] DeviceTypes (1 watcher, 0 links, 0 recursion) β β β β βββ [?] Runtimes (1 watcher, 0 links, 0 recursion) β β β βββ [d] SDKs (2 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] WatchSimulator.platform (5 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Developer (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Library (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] CoreSimulator (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Profiles (2 files, 0 watchers, 0 links, 0 recursion) β β βββ [d] DeviceTypes (2 files, 1 watcher, 0 links, 0 recursion) β β βββ [d] Runtimes (1 file, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Xcode.app (1 file, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Contents (15 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Developer (7 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Platforms (7 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] iPhoneOS.platform (8 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Developer (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Library (6 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] CoreSimulator (1 file, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Profiles (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ [d] DeviceTypes (22 files, 1 watcher, 0 links, 0 recursion) β β β βββ [d] Runtimes (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [d] SDKs (2 files, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] iPhoneSimulator.platform (5 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Developer (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Library (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [?] CoreSimulator (0 watchers, 0 links, 0 recursion) β β βββ¬ [?] Profiles (0 watchers, 0 links, 0 recursion) β β βββ [?] DeviceTypes (1 watcher, 0 links, 0 recursion) β β βββ [?] Runtimes (1 watcher, 0 links, 0 recursion) β βββ¬ [d] WatchOS.platform (7 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Developer (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Library (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] CoreSimulator (1 file, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Profiles (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ [d] DeviceTypes (6 files, 1 watcher, 0 links, 0 recursion) β β β βββ [d] Runtimes (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [d] SDKs (2 files, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] WatchSimulator.platform (5 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Developer (2 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Library (2 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [?] CoreSimulator (0 watchers, 0 links, 0 recursion) β βββ¬ [?] Profiles (0 watchers, 0 links, 0 recursion) β βββ [?] DeviceTypes (1 watcher, 0 links, 0 recursion) β βββ [?] Runtimes (1 watcher, 0 links, 0 recursion) βββ¬ [d] Library (64 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Developer (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] CoreSimulator (1 file, 0 watchers, 0 links, 0 recursion) β β βββ [d] Profiles (1 file, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Java (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] JavaVirtualMachines (5 files, 1 watcher, 0 links, 0 recursion) β β βββ [d] jdk1.7.0_80.jdk (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [d] jdk1.8.0_121.jdk (1 file, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] jdk1.8.0_131.jdk (1 file, 1 watcher, 0 links, 0 recursion) β β β βββ¬ [d] Contents (3 files, 0 watchers, 0 links, 0 recursion) β β β βββ¬ [d] Home (14 files, 1 watcher, 0 links, 0 recursion) β β β βββ [d] bin (44 files, 1 watcher, 0 links, 0 recursion) β β βββ [d] jdk1.8.0_144.jdk (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [d] jdk1.8.0_151.jdk (1 file, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Keychains (6 files, 0 watchers, 0 links, 0 recursion) β βββ [f] System.keychain (1 watcher, 0 links, 0 recursion) βββ¬ [d] opt (1 file, 2 watchers, 0 links, 0 recursion) β βββ [d] local (10 files, 2 watchers, 0 links, 0 recursion) βββ¬ [d] private (4 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] var (24 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] db (91 files, 0 watchers, 0 links, 0 recursion) β βββ [ld] xcode_select_link β /Applications/Xcode-beta.app/Contents/Developer (8 files, 0 watchers, 0 links, 0 recursion) βββ¬ [d] System (2 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Library (97 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Java (2 files, 0 watchers, 0 links, 0 recursion) β βββ [?] JavaVirtualMachines (1 watcher, 0 links, 0 recursion) βββ¬ [d] Users (5 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] kkolipaka (88 files, 2 watchers, 0 links, 0 recursion) β βββ¬ [d] .android (20 files, 0 watchers, 0 links, 0 recursion) β β βββ [d] avd (10 files, 1 watcher, 0 links, 1 recursion) β βββ¬ [d] .appcelerator (10 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] appcd (5 files, 0 watchers, 0 links, 0 recursion) β β β βββ [?] plugins (1 watcher, 0 links, 0 recursion) β β βββ¬ [d] install (31 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] 7.0.0-master.44 (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] package (15 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] node_modules (354 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] appcd-plugin-android (6 files, 2 watchers, 0 links, 0 recursion) β β β βββ [d] dist (3 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] appcd-plugin-genymotion (6 files, 2 watchers, 0 links, 0 recursion) β β β βββ [d] dist (2 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] appcd-plugin-ios (6 files, 2 watchers, 0 links, 0 recursion) β β β βββ [d] dist (3 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] appcd-plugin-jdk (6 files, 2 watchers, 0 links, 0 recursion) β β β βββ [d] dist (3 files, 1 watcher, 0 links, 0 recursion) β β βββ¬ [d] appcd-plugin-system-info (6 files, 2 watchers, 0 links, 0 recursion) β β β βββ [d] dist (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [d] appcd-plugin-windows (6 files, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] .docker (1 file, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] machine (3 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] machines (1 file, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] default (11 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] default (4 files, 0 watchers, 0 links, 0 recursion) β β βββ [f] default.vbox (1 watcher, 0 links, 0 recursion) β βββ¬ [d] .Genymobile (4 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Genymotion (6 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] deployed (1 file, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] Google Pixel - 8.0 - API 26 - 1080x1920 (9 files, 0 watchers, 0 links, 0 recursion) β β βββ [f] Google Pixel - 8.0 - API 26 - 1080x1920.vbox (1 watcher, 0 links, 0 recursion) β βββ [d] Applications (2 files, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Downloads (304 files, 0 watchers, 0 links, 0 recursion) β β βββ [d] android-ndk-r12b (14 files, 2 watchers, 0 links, 0 recursion) β βββ¬ [d] Library (73 files, 0 watchers, 0 links, 0 recursion) β βββ¬ [d] Android (1 file, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] sdk (1 file, 1 watcher, 0 links, 0 recursion) β β βββ [?] ndk-bundle (1 watcher, 0 links, 0 recursion) β βββ [d] android-sdk-macosx (16 files, 2 watchers, 0 links, 0 recursion) β βββ¬ [d] Developer (2 files, 0 watchers, 0 links, 0 recursion) β β βββ¬ [d] CoreSimulator (1 file, 0 watchers, 0 links, 0 recursion) β β βββ [d] Devices (103 files, 1 watcher, 0 links, 1 recursion) β βββ¬ [d] Keychains (7 files, 0 watchers, 0 links, 0 recursion) β β βββ [f] login.keychain-db (1 watcher, 0 links, 0 recursion) β βββ¬ [d] MobileDevice (2 files, 0 watchers, 0 links, 0 recursion) β β βββ [d] Provisioning Profiles (8 files, 1 watcher, 0 links, 0 recursion) β βββ¬ [d] Preferences (284 files, 0 watchers, 0 links, 0 recursion) β β βββ [?] com.apple.security.plist (1 watcher, 0 links, 0 recursion) β βββ¬ [d] VirtualBox (17 files, 0 watchers, 0 links, 0 recursion) β βββ [f] VirtualBox.xml (1 watcher, 0 links, 0 recursion) βββ¬ [d] usr (7 files, 2 watchers, 0 links, 0 recursion) βββ¬ [d] local (15 files, 2 watchers, 0 links, 0 recursion) βββ [d] bin (124 files, 2 watchers, 0 links, 0 recursion) βββ¬ [d] lib (41 files, 0 watchers, 0 links, 0 recursion) βββ¬ [d] node_modules (4 files, 0 watchers, 0 links, 0 recursion) βββ¬ [d] npm (23 files, 0 watchers, 0 links, 0 recursion) βββ [f] package.json (1 watcher, 0 links, 0 recursion) Plugin Version Type Path Node.js Status Active/Total Requests android 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-android 8.9.1 Active, PID=10778 1 / 1 genymotion 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-genymotion 8.9.1 Active, PID=10779 1 / 1 ios 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-ios 8.9.1 Active, PID=10780 1 / 1 jdk 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-jdk 8.9.1 Active, PID=10781 1 / 1 system-info 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-system-info 8.9.1 Active, PID=10770 7 / 12 windows 1.0.0-22 external /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-windows 8.9.1 Unsupported platform "darwin" 0 / 0 PID Command Started 10770 /Users/kkolipaka/.appcelerator/appcd/node/v8.9.1/darwin/x64/node /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin/bin/appcd-plugin-host /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-system-info 2 hours ago 10778 /Users/kkolipaka/.appcelerator/appcd/node/v8.9.1/darwin/x64/node /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin/bin/appcd-plugin-host /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-android 2 hours ago 10779 /Users/kkolipaka/.appcelerator/appcd/node/v8.9.1/darwin/x64/node /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin/bin/appcd-plugin-host /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-genymotion 2 hours ago 10780 /Users/kkolipaka/.appcelerator/appcd/node/v8.9.1/darwin/x64/node /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin/bin/appcd-plugin-host /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-ios 2 hours ago 10781 /Users/kkolipaka/.appcelerator/appcd/node/v8.9.1/darwin/x64/node /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin/bin/appcd-plugin-host /Users/kkolipaka/.appcelerator/install/7.0.0-master.44/package/node_modules/appcd-plugin-jdk 2 hours ago {code}
| 1 |
121 |
DAEMON-189
|
11/26/2017 06:58:43
|
System-info doesn't have newly created Android AVD
|
System-info doesn't have newly created android AVD. I've created a new android AVD from the studio and it appeared in the ti info but not in the appcd system-info. Please find the attached files. [^appcd_dump_master44.json] [^appcd_systeminfo_master44.json] [^appc_tiinfo_master44.json]
| 3 |
122 |
DAEMON-190
|
11/27/2017 13:41:55
|
Windows: Daemon doesn't start first time when downloading node binary
|
h5.Description *This error should have bubbled through to the cli I think* Starting the daemon when the node binaries are not downloaded on Windows doesn't work first time, logs below. Looking at appcd-nodejs it only handles EXTBUSY which I think is unixy, windows is EBUSY {code} C:\Users\Archibald Thornburnt>appc appcd start --debug Appcelerator Command-Line Interface, version 7.0.0-master.44 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. 2017-11-27T13:32:58.805Z cli-kit:context Adding command: config 2017-11-27T13:32:58.992Z cli-kit:context Adding command: dump 2017-11-27T13:32:58.992Z cli-kit:context Adding command: exec 2017-11-27T13:32:58.992Z cli-kit:context Adding command: logcat 2017-11-27T13:32:58.992Z cli-kit:context Adding command: restart 2017-11-27T13:32:59.008Z cli-kit:context Adding command: start 2017-11-27T13:32:59.008Z cli-kit:context Adding command: status 2017-11-27T13:32:59.008Z cli-kit:context Adding command: stop 2017-11-27T13:32:59.008Z cli-kit:context Adding command: help 2017-11-27T13:32:59.008Z cli-kit:context Context Lookup: 2017-11-27T13:32:59.008Z cli-kit:context Commands: 2017-11-27T13:32:59.008Z cli-kit:context config => config 2017-11-27T13:32:59.008Z cli-kit:context dump => dump 2017-11-27T13:32:59.008Z cli-kit:context exec => exec 2017-11-27T13:32:59.008Z cli-kit:context logcat => logcat 2017-11-27T13:32:59.008Z cli-kit:context restart => restart 2017-11-27T13:32:59.008Z cli-kit:context start => start 2017-11-27T13:32:59.008Z cli-kit:context status => status 2017-11-27T13:32:59.008Z cli-kit:context stop => stop 2017-11-27T13:32:59.008Z cli-kit:context help => help 2017-11-27T13:32:59.008Z cli-kit:context Options: 2017-11-27T13:32:59.008Z cli-kit:context --config => config 2017-11-27T13:32:59.008Z cli-kit:context --config-file => config-file 2017-11-27T13:32:59.008Z cli-kit:context --colors => colors 2017-11-27T13:32:59.008Z cli-kit:context --help => help 2017-11-27T13:32:59.008Z cli-kit:context --version => version 2017-11-27T13:32:59.008Z cli-kit:context -h => help 2017-11-27T13:32:59.008Z cli-kit:context -v => version 2017-11-27T13:32:59.008Z cli-kit:context Parsing: [ 'start', '--debug' ] 2017-11-27T13:32:59.008Z cli-kit:context Parsing argument: start 2017-11-27T13:32:59.008Z cli-kit:context Found command: start 2017-11-27T13:32:59.008Z cli-kit:context Parsing argument: --debug 2017-11-27T13:32:59.008Z cli-kit:context Descending into next context's parser 2017-11-27T13:32:59.023Z cli-kit:context Context Lookup: 2017-11-27T13:32:59.023Z cli-kit:context Options: 2017-11-27T13:32:59.023Z cli-kit:context --debug => debug 2017-11-27T13:32:59.023Z cli-kit:context Parsing: [ { type: 'command', 2017-11-27T13:32:59.023Z cli-kit:context command: 2017-11-27T13:32:59.023Z cli-kit:context Command { 2017-11-27T13:32:59.023Z cli-kit:context _events: Map {}, 2017-11-27T13:32:59.023Z cli-kit:context _links: [Array], 2017-11-27T13:32:59.023Z cli-kit:context desc: 'starts the Appc Daemon if it\'s not already running', 2017-11-27T13:32:59.023Z cli-kit:context options: [Array], 2017-11-27T13:32:59.023Z cli-kit:context action: [AsyncFunction: action], 2017-11-27T13:32:59.023Z cli-kit:context parent: [Object], 2017-11-27T13:32:59.023Z cli-kit:context title: 'start', 2017-11-27T13:32:59.023Z cli-kit:context args: [], 2017-11-27T13:32:59.023Z cli-kit:context commands: {}, 2017-11-27T13:32:59.023Z cli-kit:context groups: [Object], 2017-11-27T13:32:59.023Z cli-kit:context lookup: [Object], 2017-11-27T13:32:59.023Z cli-kit:context camelCase: true, 2017-11-27T13:32:59.023Z cli-kit:context name: 'start', 2017-11-27T13:32:59.023Z cli-kit:context aliases: {} } }, 2017-11-27T13:32:59.023Z cli-kit:context { type: 'unknown option', orig: '--debug' } ] 2017-11-27T13:32:59.023Z cli-kit:context Parsing argument: --debug 2017-11-27T13:32:59.023Z cli-kit:context Found option: debug 2017-11-27T13:32:59.023Z cli-kit:context Negated? false 2017-11-27T13:32:59.023Z cli-kit:context Finalizing parsing 2017-11-27T13:32:59.023Z cli-kit:context Processing default options and environment variables for 2 contexts 2017-11-27T13:32:59.023Z cli-kit:context Filling argv and _ 2017-11-27T13:32:59.023Z cli-kit:context Mixing in environment variable values 2017-11-27T13:32:59.039Z appcd:config Loading JavaScript config file: C:\Users\Archibald Thornburnt\.appcelerator\install\7.0.0-master.44\package\node_modules\appcd-core\conf\default.js 2017-11-27T13:32:59.117Z appcd:config Parsing AST... 2017-11-27T13:32:59.148Z appcd:config Loading JSON config file: C:\Users\Archibald Thornburnt\.appcelerator\install\7.0.0-master.44\package\node_modules\appcd-core\conf\preprod.json 2017-11-27T13:32:59.148Z appcd:common { 2017-11-27T13:32:59.148Z appcd:common "core": { 2017-11-27T13:32:59.148Z appcd:common "enforceNodeVersion": true, 2017-11-27T13:32:59.148Z appcd:common "v8": { 2017-11-27T13:32:59.148Z appcd:common "memory": "auto" 2017-11-27T13:32:59.148Z appcd:common } 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "home": "~/.appcelerator/appcd", 2017-11-27T13:32:59.148Z appcd:common "network": { 2017-11-27T13:32:59.148Z appcd:common "agentOptions": null, 2017-11-27T13:32:59.148Z appcd:common "caFile": null, 2017-11-27T13:32:59.148Z appcd:common "certFile": null, 2017-11-27T13:32:59.148Z appcd:common "httpProxy": null, 2017-11-27T13:32:59.148Z appcd:common "httpsProxy": null, 2017-11-27T13:32:59.148Z appcd:common "keyFile": null, 2017-11-27T13:32:59.148Z appcd:common "passphrase": null, 2017-11-27T13:32:59.148Z appcd:common "strictSSL": true 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "plugins": { 2017-11-27T13:32:59.148Z appcd:common "autoReload": true, 2017-11-27T13:32:59.148Z appcd:common "defaultInactivityTimeout": 3600000 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "server": { 2017-11-27T13:32:59.148Z appcd:common "agentPollInterval": 1000, 2017-11-27T13:32:59.148Z appcd:common "daemonize": true, 2017-11-27T13:32:59.148Z appcd:common "group": null, 2017-11-27T13:32:59.148Z appcd:common "hostname": "127.0.0.1", 2017-11-27T13:32:59.148Z appcd:common "pidFile": "~/.appcelerator/appcd/appcd.pid", 2017-11-27T13:32:59.148Z appcd:common "port": 1732, 2017-11-27T13:32:59.148Z appcd:common "user": null 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "telemetry": { 2017-11-27T13:32:59.148Z appcd:common "enabled": true, 2017-11-27T13:32:59.148Z appcd:common "eventsDir": "~/.appcelerator/appcd/telemetry", 2017-11-27T13:32:59.148Z appcd:common "sendBatchSize": 10, 2017-11-27T13:32:59.148Z appcd:common "sendInterval": 60000, 2017-11-27T13:32:59.148Z appcd:common "sendTimeout": 60000, 2017-11-27T13:32:59.148Z appcd:common "url": "https://api.appcelerator.com/p/v1/app-track" 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "appcd": { 2017-11-27T13:32:59.148Z appcd:common "guid": "14c84daf-b01e-486c-96d3-b8f66da44481" 2017-11-27T13:32:59.148Z appcd:common }, 2017-11-27T13:32:59.148Z appcd:common "environment": { 2017-11-27T13:32:59.148Z appcd:common "name": "preprod", 2017-11-27T13:32:59.148Z appcd:common "title": "Pre-production" 2017-11-27T13:32:59.148Z appcd:common } 2017-11-27T13:32:59.148Z appcd:common } 2017-11-27T13:32:59.195Z appcd:nodejs Checking C:\Users\Archibald Thornburnt\.appcelerator\appcd\node\v8.9.1\win32\x64\node.exe 2017-11-27T13:32:59.227Z appcd:nodejs Downloading https://nodejs.org/dist/v8.9.1/node-v8.9.1-win-x64.zip => C:\Users\ARCHIB~1\AppData\Local\Temp\node-v8.9.1-win-x64.zip 2017-11-27T13:32:59.227Z appcd:dispatcher Searching for route handler: /appcd/config/network 2017-11-27T13:32:59.351Z appcd:dispatcher Route not found: /appcd/config/network 2017-11-27T13:33:00.053Z appcd:request GET https://nodejs.org/dist/v8.9.1/node-v8.9.1-win-x64.zip 200 (16.11 MB) 2017-11-27T13:33:01.819Z appcd:nodejs Downloaded 16,892,891 bytes 2017-11-27T13:33:01.819Z appcd:nodejs Creating C:\Users\Archibald Thornburnt\.appcelerator\appcd\node\v8.9.1\win32\x64 2017-11-27T13:33:01.819Z appcd:nodejs Extracting zip file: C:\Users\ARCHIB~1\AppData\Local\Temp\node-v8.9.1-win-x64.zip 2017-11-27T13:33:01.850Z appcd:nodejs Found node executable (23,089,816 bytes) 2017-11-27T13:33:02.116Z appcd:nodejs Spawning: C:\Users\Archibald Thornburnt\.appcelerator\appcd\node\v8.9.1\win32\x64\node.exe --max_old_space_size=3000 --inspect "C:\Users\Archibald Thornburnt\.appcelerator\install\7.0.0-master.44\package\node_modules\appcd-core\dist\main.js" # {"stdio":["inherit","inherit","inherit","ipc"]} {code} h5.Steps to reproduce # Remove ~/.appcelerator/appcd/node # {{set SNOOPLOGG=*}} # {{appcd start --debug}} h5.Actual Daemon doesnt start h5.Expected Daemon should start
| 1 |
123 |
DAEMON-192
|
11/28/2017 04:32:04
|
"appc appcd exec /system-info/1.x/info" command doesn't respond with 1.0.0-23
|
"appc appcd exec /system-info/1.x/info" command doesn't respond with version 1.0.0-23 {code:java} $ appc appcd exec /system-info/1.x/info Appcelerator Command-Line Interface, version 7.0.0-master.48 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. {code} Please find the attached dump file. [^appcd_dump_master48.json]
| 1 |
124 |
DAEMON-193
|
11/28/2017 04:45:04
|
Failed to start the Appc Daemon
|
"Failed to start the Appc Daemon" message shown when I start a daemon. {code:java} ITEM-AX40113:titanium_studio kkolipaka$ appc appcd start Appcelerator Command-Line Interface, version 7.0.0-master.48 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Failed to start the Appc Daemon {code} Looks like it's showing a wrong message when the daemon is already running. {code:java} ITEM-AX40113:titanium_studio kkolipaka$ appc appcd start --debug Appcelerator Command-Line Interface, version 7.0.0-master.48 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Starting inspector on 127.0.0.1:9229 failed: address already in use Failed to start the Appc Daemon {code}
| 8 |
125 |
DAEMON-195
|
11/28/2017 05:26:14
|
" appc appcd exec start" not working anymore
|
{{appc appcd exec start}} not working anymore. {code:java} $ appc appcd exec start Appcelerator Command-Line Interface, version 7.0.0-master.48 Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved. Not Found {code}
| 1 |
126 |
DAEMON-196
|
11/28/2017 10:44:42
|
appcd-core: Ensure the pid file always exists
|
When the daemon is running, it creates a pid file in the appcd home dir. This is critical as it is used to determine if the daemon is running. If this file is deleted while the daemon is running, this can be problematic as the zombie daemon process will need to manually terminated by the user.
| 3 |
127 |
DAEMON-198
|
11/28/2017 20:23:59
|
Plugin config changes are not applied automatically
|
The Android, Genymotion, iOS, and Windows plugins have config options that are loaded once when the plugins are started. If any plugin specific config options are changed, then do not take effect until the plugin(s) or the daemon is restarted. h4. Default config * plugins.autoReload ** appcd-plugin/src/external-plugin.js * plugins.defaultInactivityTimeout ** appcd-plugin/src/plugin.js * server.agentPollInterval ** appcd-core/src/status-monitor.js ** appcd-plugin/src/external-plugin.js h4. appcd-plugin-android * android.ndk.searchPaths ** appcd-plugin-android/src/android-info-service.js * android.sdk.searchPaths ** appcd-plugin-android/src/android-info-service.js
| 5 |
128 |
DAEMON-200
|
12/04/2017 09:33:32
|
Android device not detected when plugged in after daemon start upon system restart
|
Steps to Reproduce: 1. Restart the system and make sure to plug out connected android device 2. Start Daemon 3. Run the command "/android/1.x/info". The devices section is blank as no device connected yet 4. Connect the device. 5. Again run the command "/android/1.x/info". Actual Result: The device section still shows blank and does not show the connected device. The device is shown in "appc ti info". Note: Repeating step 5 continues to give device as blank untill daemon is restarted. Find attached the daemon dump.
| 8 |
129 |
DAEMON-204
|
12/06/2017 15:51:17
|
appcd-winreg: Add support for specifying registry hive architechture
|
h5.Description From my research into windowslib v2 we're going to need to query the 32 bit registry hive architecture, this can be achieved by passing an opt.arch value to win-reg. If no value is specified we should default to null. This will also need to be added to appcd-detect
| 1 |
130 |
DAEMON-209
|
12/11/2017 08:39:21
|
Studio: iOS SDK home not found and NullPointerException
|
I updated to Appcelerator Studio 5.0.0.201712081732 (official Release) and now the iOS SDK home is not found anymore. Android works. Can I do something to fix it? -- There's a bug in ioslib when it tries to build the list of teams. If one of the provisioning profiles does not have any teams, then the {{teamIds}} will be {{null}}. The code that builds the unique list of teams expects teams to be an array.
| 8 |
131 |
DAEMON-205
|
12/11/2017 15:22:57
|
ioslib: Failing to parse certs if any cert has invalid unicode sequences
|
It's possible for a cert to have a name that cannot be decoded to an unsupported character sequence. We need to wrap each cert parsing in a try/catch so that we just skip the cert and move on.
| 3 |
132 |
DAEMON-206
|
12/11/2017 15:42:34
|
Appcelerator Studio not detecting iOS after upgrading
|
After upgrading Xcode, Appcelerator Studio and node, I can't run any application from Appcelerator Studio. The Run/Debug buttons have disappeared, whenever I click on anything concerning iOS, I get the error: !MESSAGE An internal error occurred during: "Loading Provisioning Profiles...". !STACK 0 java.lang.NullPointerException Attached some of the weird things happening + the logs. I already tried uninstalling Appcelerator Studio, it didn't change anything (besides losing all of my configurations)
| 1 |
133 |
DAEMON-207
|
12/11/2017 18:48:53
|
"appc appcd restart" does not restart the daemon but keeps on adding appcd-plugin-host processes which keep running & consume memory
|
h5.Steps to reproduce: 1. Do a {{appc appcd restart}} in the command prompt. h5.Actual results: 1. The daemon does not restart (Not sure if it does restart internally, but gives wrong message that it didn't in the terminal). {code} ITEM-AX44549:QEUtility-Node lchoudhary$ ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started ITEM-AX44549:QEUtility-Node lchoudhary$ appc appcd restart Appc Daemon already started {code} 2. It also keeps on adding {{appcd-plugin-host}} processes after each restart command run. These processes stay running & consume memory. (Attached a screenshot for reference). h5. Expected results: 1. Daemon should restart successfully every time command is run & should not keep on adding new appcd-plugin-host processes or kill/stop the old ones.
| 13 |
134 |
DAEMON-211
|
12/14/2017 00:20:40
|
issues reflecting available iOS mobileProvision profiles
|
Have downloaded new provisioning profiles as I have a new device to test/run the app in AdHoc mode. I have deleted the existing provisioning files and updated with the new ones (files in command line are the new ones). I have restarted Studio, XCode and the computer for changes to take effect but no success. I am unable to package apps using the new profiles as the certificates are still the old ones. 'Refresh' button doesn't seem to reflect the changes made to certificates and to provisioning Profiles.
| 3 |
135 |
DAEMON-210
|
12/14/2017 20:11:19
|
system-info: npm detection fails if unable to get npm prefix
|
The system-info plugin is responsible for detecting npm. It does this by first locating the npm executable in the system PATH, then tries to get the "prefix" by running {{npm prefix -g}}. However, if this should fail, then the prefix will be {{undefined}} and an exception is thrown when trying to expand the path.
| 5 |
136 |
DAEMON-214
|
01/08/2018 16:24:47
|
Create Appc Daemon plugin template
|
We need a template for creating new appcd plugins.
| 13 |
137 |
DAEMON-216
|
01/09/2018 20:15:34
|
Plugins not ordered on status output
|
The plugins in the output from {{appcd status}} are not ordered.
| 3 |
138 |
DAEMON-217
|
01/09/2018 22:51:38
|
appcd-plugin-titanium-sdk: Titanium info service
|
Create the {{appcd-plugin-titanium-sdk}} plugin and the "info" service. The "info" service is to detect installed Titanium SDKs and modules.
| 13 |
139 |
DAEMON-218
|
01/11/2018 20:51:21
|
appcd-detect: Subdirectories are not watched for changes that would make them valid
|
When detecting things in a directory, if a subdirectory is created, but the criteria in that subdirectory does not exist yet, the subdirectory is never rescanned. This only applies when {{opts.watch=true}}.
| 5 |
140 |
DAEMON-221
|
01/16/2018 16:40:44
|
gulp upgrade: Run 'yarn' in top-level after updates and 'yarn upgrade' for each package
|
The {{gulp upgrade}} task does a good job of updating all of the npm dependencies in each package's {{package.json}}, but the top-level doesn't actually install the new deps. I think we simply need to remove the call to {{lerna bootstrap}} and call {{yarn}}. Also, we never upgrade the dependencies of dependencies. We need to write temporary {{package.json}} files with no {{appcd-*}} deps, run {{yarn upgrade}}, then restore the original {{package.json}}. This will update the {{yarn.lock}} files.
| 5 |
141 |
DAEMON-223
|
01/21/2018 20:20:22
|
Plugin: Noisy warnings in log due to invalid appcd plugins
|
The plugin system will check several directories to see if they are a appcd plugin, however if there are several non-appcd plugin modules, the log will be filled with a bunch of bogus warnings. We need to filter out these warnings so that we only error if we find an appcd plugin with invalid appcd settings.
| 5 |
142 |
DAEMON-224
|
01/23/2018 17:24:47
|
Subscriptions not terminated if connection is reset
|
If a client goes away, the WebSocketServer can emit an error {{ECONNRESET}} instead of emitting an "end" event. We need to add better logging and also listen for errors so that we can end the internal subscription stream.
| 5 |
143 |
DAEMON-230
|
02/02/2018 16:42:06
|
Stream stringified JSON data over IPC and response instead of JSON.stringify()
|
When a plugin sends a JS object response over IPC or a service writes a JS object response over the WebSocket or HTTP response, the JS object is serialized using {{JSON.stringify()}}. However, {{JSON.stringify()}} eats up a ton of memory when the JS object is large. It would be much more efficient to stringify while writing to the stream. There are several npm packages that will stringify a stream, but they are geared towards each write being a small object which they just call {{JSON.stringify()}} on it. What we need is transforming stream that does stringifies the JS object on the fly. Stringify is not a complex algorithm, but would need to figure out how to handle Node specific objects like {{Buffer}}.
| 3 |
144 |
DAEMON-232
|
02/08/2018 17:49:54
|
FSWatcher: Events relating to permission changes to a folder are dropped on Windows
|
h5.Description In DAEMON-222 changed were made to prevent unnecessary change events (a child item changing for example) on a folder bubbling up, which had the side-effect of causing any change events to not fire for a folder on Windows. The current solutions for tracking information through fs.Stats is lightweight on Windows a potential native module (https://github.com/xxoo/node-fswin) was found but the heaviness of using this module wasn't wanted. This is more than likely going to need to be sovled in the future It's probable that issues relating to permissions will be prevalent on unixy systems too h5.Steps to repro TODO
| 13 |
145 |
DAEMON-237
|
02/15/2018 15:04:55
|
Create Appc Daemon 1.1.0 release notes
|
Need to go through the appc-daemon repo and all plugins and write up release notes for v1.1.0.
| 8 |
146 |
DAEMON-238
|
02/16/2018 04:22:57
|
appcd-util: Add ability to cancel a debounce
|
{{debounce()}} uses a {{setTimeout()}} that has no way to be cancelled. This becomes a problem if you are debouncing events for something that you have shutdown.
| 3 |
147 |
DAEMON-239
|
02/16/2018 04:27:01
|
appcd-plugin: Scheme needs to cancel debounced scheme change events on shutdown
|
When the PluginManager shuts down, it unregisters all plugin paths and the scheme associated with the plugin path. If it's shut down while a scheme's debounced change event is pending, things go haywire. The scheme {{destory()}} method needs to call the {{cancel()}} method introduced by DAEMON-238.
| 5 |
148 |
DAEMON-241
|
03/08/2018 16:36:15
|
Telemetry: Events are being sent using the incorrect guid
|
h5.Description Currently the daemon defaults to preproduction for the telemetry. After some discussions it was decided that we need to not have a concept of preproduction and instead do the following * Remove preprod * Remove prod, put into default.js * Add deploytype to the analytics payloads * In the gulp scripts, we should set the telemetry environment on start * Document the variable * Validate that the analytics being sent are shown on dashboard
| 5 |
149 |
DAEMON-242
|
03/09/2018 04:34:12
|
appcd: Global options not displayed on command help
|
Global options should be displayed on the help screen for individual commands, but it's not. {code} $ appcd --help Usage: appcd <command> [options] Commands: config get and set config options dump dumps the config, status, health, and debug logs to a file exec connects to the Appc Daemon and executes the request logcat streams Appc Daemon debug log output restart stops the Appc Daemon if running, then starts it start starts the Appc Daemon if it's not already running status displays the Appc Daemon status stop stops the Appc Daemon if running Global options: --config=<json> serialized JSON string to mix into the appcd config --config-file=<file> path to a appcd JS config file --no-colors disables colors -h, --help displays the help screen -v, --version outputs the appcd version {code} Global options are present above. {code} $ appcd start --help Usage: appcd start [options] starts the Appc Daemon if it's not already running start options: --debug don't run as a background daemon {code} Global options are not displayed enough.
| 5 |
150 |
DAEMON-244
|
03/14/2018 16:05:04
|
appcd-nodejs: Add mechanism for removing old Node.js executables
|
We would like to upgrade the Node.js version of the Appc Daemon, but everytime we do, it will download a new Node.js executable. The problem is we do not want to end up with dozens of Node.js executables. We need a way of timestamp when a specific version of Node.js was last run. Then {{appcd-nodejs}} needs a service that uses a {{setTimeout()}} that periodically archives/deletes executables that haven't been used for some period of time.
| 8 |
151 |
DAEMON-245
|
03/15/2018 06:23:33
|
Upgrade to latest babel packages
|
Update the daemon's babel dependencies to the latest and greatest.
| 8 |
152 |
DAEMON-246
|
03/22/2018 15:54:21
|
appcd-plugin-titanium-sdk: Split info service into sdk and module services
|
We need to split the info service into distinct sdk and module services so that it becomes more logical when we add more functionality for sdks and modules.
| 5 |
153 |
DAEMON-247
|
03/23/2018 05:50:02
|
appcd-plugin-titanium-sdk: Add install, uninstall, and search
|
Now that the Titanium SDK plugin has a "sdk" service that lists all installed Titanium SDKs, we need the ability: * To search for available SDKs to download (by name or branch) * Download and install an SDK from an Appc server * Download and install an SDK from an arbitrary URL * Install an SDK from a local zip file * Uninstall a SDK
| 13 |
154 |
DAEMON-248
|
03/30/2018 04:12:04
|
Allow arbitrary metadata to be added to error objects
|
As the daemon routes errors from a plugin to the core or from the core over a WebSocket, errors are treated special so that can recreate the error as a real Error object whenever coming for another context. The problem is error properties are whitelisted and some are computed (getters). All error handling needs to be cleaned up so that we can pass along arbitrary values added to the original error object. When {{appcd exec}} is returned an error, the error should be stringified to reveal all properties including the hidden error object properties.
| 8 |
155 |
DAEMON-249
|
04/09/2018 12:18:58
|
appcd-plugin-android: Genymotion emulators not reloaded on change
|
h5.Description When making changes to genymotion emulators they are not reloaded under the {{/android/latest/info/emulators}} endpoint, however they are reloaded under the {{/genymotion/latest/info/emulators}} endpoint. It looks like we just need to include the vbox config path in the watch paths h5.Steps to reproduce * Start the daemon {{appcd start}} * Call {{appcd exec /android/latest/emulators}} * Either add or remove a genymotion emulator * Call {{appcd exec /android/latest/emulators}} * Call {{appcd exec /genymotion/latest/emulators}} h5.Actual Genymotion emulator not changed in the android endpoint, it is in the genymotion endpoint h5.Expected Should be changed in both
| 3 |
156 |
DAEMON-250
|
04/09/2018 15:02:30
|
@appcd/plugin-ios: New iOS simulator runtimes are not picked up after install
|
h5.Description *This is probably an improvement as I can't find any reference to us currently attempting to do this* If I install a new iOS simulator runtime in xcode, then the daemon will not pick it up. Looking through the code, I think we need to set up a watcher on [xcode.globalSimProfilesPath|https://github.com/appcelerator/ioslib/blob/6189855ebc055f85957b93bf4bbe595189607396/src/xcode.js#L29] in ioslib and rescan xcodes and simulators on change. h5.Steps to reproduce * Start the daemon {{appcd start}} * Call the ios info endpoint for xcode info {{appcd exec /ios/latest/info/xcode}}, make note of the simRuntimes property * Install a new sim runtime through Xcode (Xcode->Preferences->Components) * When finished call the ios info endpoint again, noting the simRuntimes property for the xcode you installed the runtime in h5.Actual No new runtime is detected h5.Expected New runtime should be detected
| 3 |
157 |
DAEMON-251
|
04/11/2018 21:51:49
|
appcd-plugin: Plugin info not updated when package.json is changed
|
Once the plugin system detects and registers a plugin, it doesn't reload the plugin information when the package.json is changed. If the package.json is modified, the plugin should be stopped. Furthermore, if the package.json is not valid JSON, then it should also be unregistered.
| 5 |
158 |
DAEMON-252
|
04/12/2018 21:17:21
|
Android: Daemon does not detect addition/deletion of genymotion emulator's immediately
|
Does not appear to be a regression. Seen in 1.0.1 as well. h5.Steps to reproduce: 1. Add a 2-3 genymotion emulator in the genymotion app. 2. Run {{appc appcd exec /android/latest/info/emulators}}. 3. Repeat the steps after deleting 2-3 genymotion emulators. h5.Actual result: 1. Appc daemon does not pick up the changes to genymotion immediately for both addition & deletion scenarios but, does after an {{appc appcd restart}}. h5.Expected results: 1. Appc daemon should pickup the changes immediately.
| 8 |
159 |
DAEMON-253
|
04/13/2018 23:04:37
|
Paths of interest should only be watched once
|
The quick and dirty {{watch()}} method used in the Android and iOS appcd plugin info service will record all active fs watch subscription ids, re-watch all paths of interest, then unwatch the original subscription ids. This works, but can lead to fs events being lost. This issue was discovered while fixing DAEMON-252.
| 5 |
160 |
DAEMON-255
|
04/25/2018 15:42:54
|
Appcelerator Studio not detecting android emulator and emulator doesn't come up on windows 7
|
Hello, We have an Enterprise customer who is facing an issue with Appcelerator Studio. Appcelerator Studio not detecting android emulator and emulator doesn't come up on windows 7. We have attached the screenshot, Studio Diagnostic log and *appc ti setup check* log file. If any others information needed please let us know. Thanks
| 5 |
161 |
DAEMON-256
|
05/15/2018 21:50:58
|
Update appcd to latest cli-kit and export CLI definintion
|
cli-kit now allows for extensions and appcd needs to export its CLI definition to be consumable by other cli-kit enabled CLI's.
| 13 |
162 |
DAEMON-258
|
05/23/2018 16:48:35
|
appcd-gulp: Replace del.sync() with fs.removeSync()
|
Since we already depend on {{fs-extra}}, just use it's {{fs.removeSync()}} function instead of pulling in {{del}}.
| 3 |
163 |
DAEMON-260
|
06/26/2018 04:47:14
|
Android configuration issues with the Studio 5.1.0
|
Hi all. I am having issues with Studio on my Mac. It seems to randomly not know that I have Android SDKs installed. It worked last week. Just this morning, I start up studio and on the dashboard I see that Android is ready to go. Then an few seconds later it changes to grayed out and the button says download. I click download and run the install - when I do it recognizes that I already have some versions of the SDK installed. But once through the install process, the problem still exists. I have been doing this all morning. An interesting point is that one of the times I did this process, it worked and I saw the emulators that I have always had available in Studio. Also note that the preferences pane in Studio sometimes shows that it has found the SDKs and the emulators dropdown is populated, but most of the time it looks like the attached screenshot. Any help would be greatly appreciated as I am unable to do Android mobile demonstrations and I have several in the near future. Thanks in advance.
| 5 |
164 |
DAEMON-263
|
09/28/2018 16:02:34
|
appcd-core: Add AMPLIFY CLI version to telemetry
|
Add AMPLIFY_CLI env var to the telemetry payload.
| 2 |
165 |
DAEMON-265
|
10/22/2018 16:18:29
|
appcd-plugin: Expose services in plugin info
|
Wouldn't it be cool if plugin info included a list of service endpoints!?
| 3 |
166 |
DAEMON-266
|
10/25/2018 14:22:51
|
appcd exec doesn't properly handle streamed responses
|
There is an issue where non-subscription based responses are not being terminated when finished. The problem stems from the {{WebSocketSession}} not properly sending a {{fin: true}} on the last message and the client not handling the last message in the request.
| 8 |
167 |
DAEMON-267
|
10/25/2018 17:05:11
|
Investigate possibility of bi-directional websocket requests
|
.
| 1 |
168 |
DAEMON-270
|
01/24/2019 19:45:04
|
Appcd Deamon not working
|
*Steps To Reproduce:* 1.Run appcd command in terminal {code} appc appcd restart {code} *Expected:* Daemon should be restarted *Actual:* The daemon refuses to start and throws error An uncaught exception was thrown! Cannot destructure property `filesize` of 'undefined' or 'null'. Cannot destructure property `filesize` of 'undefined' or 'null'. *Note1:* For me when I changed the cli to 7.0.9 ,it worked fine. *Note 2:* For Josh Quick ,this happens with CLI v7.0.9 also and he tried with node v8.9.3 and v10.15.0 β It also causes Appc Studio to beach ball forever
| 5 |
169 |
DAEMON-271
|
02/14/2019 21:13:20
|
Error streaming object responses to HTTP clients
|
When a request is made to a service from an HTTP client, such as {{curl}}, that streams an object response, the dispatcher context's response stream is eventually piped into Koa's HTTP server's response stream which expects streamed chunks to be either strings or buffers. When an object is streamed, an error is thrown. The solution is to stringify the object before it gets piped to the server response.
| 5 |
170 |
DAEMON-272
|
02/14/2019 23:28:36
|
appcd-subprocess: Remove HTTP source check
|
The {{SubprocessManager}} has a false security measure where only requests from internal routes and plugins and requests from WebSockets can spawn commands. Requests from HTTP are forbidden. Since WebSockets requests are essentially HTTP requests, there's no point blocking HTTP requests. The daemon's web server listens on localhost only, so there's no way for an outside actor to spawn a command. To make things worse, the check to see if the source is indeed "http" is broken. It checks if {{ctx.request.source}} is "http" when it should be checking {{ctx.source}}. This restriction is pointless and does not work. It should just be removed.
| 5 |
171 |
DAEMON-273
|
04/02/2019 08:00:04
|
appcd-plugin: Tunnel messages missing dispatcher context props
|
Plugins run in a child process and communicate with a parent process using an IPC-based tunnel. However the tunnel does not translate over the {{headers}} and {{source}} from a {{DispatcherContext}} instance. Instead of passing the {{DispatcherContext}}'s {{request}} property, the tunnel needs to step up one level and pass the {{headers}}, {{path}}, {{request}} (formerly "data"), and {{source}}.
| 8 |
172 |
DAEMON-274
|
04/03/2019 21:29:42
|
appcd-config: Added support for config layers to be used by plugins
|
Plugin configs are loaded and mixed with the global config, but it's merged at a global level and once merged, remains merged until the daemon is stopped. It also doesn't namespace the plugin configs. To solve this, {{appcd-config}} needs the ability to define config layers. There is a default root layer, but then each registered config file from plugin is a new layer. These plugin config layers are namespaced so that they don't conflict. Note that this does not affect the user-defined config which overlays everything.
| 8 |
173 |
DAEMON-275
|
04/30/2019 06:15:11
|
appcd-gulp: Add Node.js 12 babel conf
|
Node.js 12 ships with V8 that supports new JavaScript features that do not require transpilation. Among the new features are class fields. Node 12 also has support for modules, though this may be a larger scope than simply removing ES6 module transpilation.
| 5 |
174 |
DAEMON-276
|
05/26/2019 13:28:52
|
Deprecate appcd-winreg
|
Now that {{winreglib}} is done, there is no need for {{appcd-winreg}}, so mark the npm package as deprecated and update the following packages to use {{winreglib}} instead: * {{appcd-detect}} * {{appcd-response}} * {{appcd-machine-id}}
| 5 |
175 |
DAEMON-277
|
05/28/2019 19:22:22
|
appcd-plugin: Remove appcd-winreg in [email protected]
|
{{appcd-winreg}} is deprecated and plugins should either migrate to {{winreglib}} or explicitly depend on {{appcd-winreg}}.
| 2 |
176 |
DAEMON-278
|
06/04/2019 17:49:36
|
windowslib: Add ability to get remote device info
|
Microsoft made a handy API we should use: https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-api-core.
| 1 |
177 |
DAEMON-280
|
06/05/2019 16:33:42
|
appcd-default-plugins: Bundle multiple plugin versions
|
Now that there are multiple major versions of appcd plugins, we need figure out a way to ship them. Some tools depend on v1, others on v2. We need both. Ideally plugins would be installed via the AMPLIFY Package Manager, but we're not quite there yet. So, it makes sense to use {{appcd-default-plugins}} as the package. The appcd plugin system does support a nested plugin directory scheme, but this is incompatible with {{node_modules}}. So we'll likely need a pre-publish task that organizes the files appropriately and efficiently.
| 13 |
178 |
DAEMON-281
|
06/07/2019 14:44:35
|
[email protected] is not compatible with [email protected]
|
h5.Description [email protected] is causing plugins to error on startup when using appc daemon 1.x (the appc cli). I have not got any useful logs for this yet. I have rolled back the latest tag for appcd-plugin to 1.3.0 to prevent new users having any issues cc [~cb1kenobi]
| 8 |
179 |
DAEMON-282
|
08/14/2019 14:25:46
|
iOS: Daemon fails to detects iOS 13 simulators
|
h5.Description When using appcd 1.1.3 the ios plugin fails to detect iOS 13 simulators installed via xcode 11. This is fixed in ioslib 3 (and the upcoming v2 of appcd-plugin-ios) but we need to cherry pick the ioslib changes back to v2 to ensure appcd 1.1.3 works for ios 13/xcode 11 release
| 5 |
180 |
DAEMON-283
|
08/28/2019 16:43:07
|
Daemon reports iOS Simulator listing as only 9.3 devices with multiple Xcode's, sim versions installed
|
I'm trying to test debugger changes within Studio around iOS 13. However, the simulator listing displayed shows the list of 9.3 simulators only. I have Xcode 10.3 and 11 beta 6 installed. 11 beta 6 is selected. The JSON info object returned by the daemon only has the 9.3 iOS simulators listed within it. (though the Xcode listings shows 12.4 and 13.0 in it's sim/sdk version listings) As a result, trying to launch to any of the listed simulators ends up failing (around Xcode 10.3 Eula not being accepted - which is presumably related to Xcode 11 being the selected/used one). Here's the result of running {{ti info}}: {code} Xcode 11.0 (build 11M392q) - Xcode default Install Location = /Applications/Xcode-11.Beta.6.app/Contents/Developer iOS SDKs = 13.0 iOS Simulators = 13.0 Watch SDKs = 6.0 Watch Simulators = 6.0 Supported by TiSDK 8.2.0.v20190827073118 = yas EULA Accepted = yas Teams = none 10.3 (build 10G8) Install Location = /Applications/Xcode-10.3.app/Contents/Developer iOS SDKs = 12.4 iOS Simulators = 12.4 Watch SDKs = 5.3 Watch Simulators = 5.3 Supported by TiSDK 8.2.0.v20190827073118 = yas EULA Accepted = no Teams = none iOS Keychains login.keychain-db = /Users/cwilliams/Library/Keychains/login.keychain-db System.keychain = /Library/Keychains/System.keychain iOS Development Certificates /Users/cwilliams/Library/Keychains/login.keychain-db Christopher Williams (8845U7T743) Not valid before = 1/24/2019 10:01 AM Not valid after = 1/24/2020 10:01 AM iOS App Store Distribution Certificates None Apple WWDR Certificate Apple WWDR = installed Development iOS Provisioning Profiles Chris Barber Dev Testapp3 UUID = 9d44fc65-2d11-476b-824c-7e8fa6deef2a App Prefix = WP4952RUHJ App Id = com.appcelerator.testapp3 Date Created = 10/31/2018 12:19 PM Date Expired = 10/31/2019 12:19 PM Managed = No Chris Williams Dev Profile UUID = 23cc7809-fbf5-47d8-a6e2-6a7e865294b6 App Prefix = 6QZBVXG979 App Id = * Date Created = 12/7/2018 2:57 PM Date Expired = 12/7/2019 2:57 PM Managed = No Chris Williams Dev Profile UUID = fb211c43-f6e4-4efc-9ab6-590393ddf15a App Prefix = 6QZBVXG979 App Id = * Date Created = 1/24/2019 10:27 AM Date Expired = 1/24/2020 10:27 AM Managed = No iOS Team Provisioning Profile: com.appcelerator.titanium UUID = ce840fb3-b882-4468-8a97-294b990a3206 App Prefix = B8MTC6CZTL App Id = com.appcelerator.titanium Date Created = 1/24/2019 10:12 AM Date Expired = 1/24/2020 10:12 AM Managed = Yas and is NOT compatible with Titanium vvs dev provisioning UUID = adf28d2a-ab3d-4130-8cfa-742af67c001a App Prefix = WP4952RUHJ App Id = com.appcelerator.vvs Date Created = 11/15/2018 11:56 PM Date Expired = 11/15/2019 11:56 PM Managed = No App Store Distribution iOS Provisioning Profiles None Ad Hoc iOS Provisioning Profiles vvs Adhoc distribution UUID = 68bd0910-dd27-4f99-984b-c61a4ce71062 App Prefix = WP4952RUHJ App Id = com.appcelerator.vvs Date Created = 11/16/2018 4:39 AM Date Expired = 11/16/2019 4:27 AM Managed = No Enterprise Ad Hoc iOS Provisioning Profiles None iOS Simulators 9.3 iPad 2 (ipad) UDID = 7E4B0B67-6FFA-4E35-AEDB-B25C8E1400C6 Supports Watch Apps = no iPad Retina (ipad) UDID = AF4E8716-F8B0-4F5A-8EE1-52595D64597A Supports Watch Apps = no iPad Air (ipad) UDID = E9C9953A-5F50-4ACC-ACC1-05FF6A7C3D7C Supports Watch Apps = no iPad mini 2 (ipad) UDID = CF24D685-20FD-42AC-A19F-D56F954FEED7 Supports Watch Apps = no iPad mini 3 (ipad) UDID = 4B698EF4-4D7E-4D68-B035-6245264C1896 Supports Watch Apps = no iPad mini 4 (ipad) UDID = 235C38DE-00DD-4B6F-A2DF-5E91C5D993F6 Supports Watch Apps = no iPad Air 2 (ipad) UDID = 1FD5F0BC-DA25-4C68-9EBD-053CEBB78854 Supports Watch Apps = no iPad Pro (12.9-inch) (ipad) UDID = 89BCA826-1861-427C-83C4-5315D7356674 Supports Watch Apps = no iPhone 4s (iphone) UDID = 6562C11B-28F8-45FD-A60A-C5C27DB61F7D Supports Watch Apps = no iPhone 5 (iphone) UDID = 78B1AFE3-18D0-468E-BD8F-A1EE9280462C Supports Watch Apps = yas iPhone 5s (iphone) UDID = F4E14045-B317-483F-8669-142C7C62D7A6 Supports Watch Apps = yas iPhone 6 Plus (iphone) UDID = 7354452A-0B5E-4AEF-A604-D72B8C6337D7 Supports Watch Apps = yas iPhone 6 (iphone) UDID = 176863A2-71EA-4260-BF22-5D9AEECAEFAC Supports Watch Apps = yas iPhone 6s (iphone) UDID = 5E14BAD5-B71B-4A5D-8F19-355BD7CB500C Supports Watch Apps = yas iPhone 6s Plus (iphone) UDID = 81817A3A-0DC5-4DCD-BB02-9C9B64D48B19 Supports Watch Apps = yas iPhone SE (iphone) UDID = E4C345E6-F44B-4081-AA53-2B389ECD1834 Supports Watch Apps = yas 13.0 iPad mini (5th generation) (ipad) UDID = 7A5F4D21-6C2A-4833-883C-A1268F0AEAAD Supports Watch Apps = no iPad Air (3rd generation) (ipad) UDID = 55F85749-4C87-4BBF-A0AE-2D7F9634BA88 Supports Watch Apps = no iPad mini 4 (ipad) UDID = 0592AD71-0E03-4D09-9C64-191879B315E4 Supports Watch Apps = no iPad Air 2 (ipad) UDID = 3A0DED6A-131D-47A8-8371-26D872F9DA50 Supports Watch Apps = no iPad (5th generation) (ipad) UDID = 2B29AC6D-8469-4BDA-81F7-EF18AE09123A Supports Watch Apps = no iPad Pro (9.7-inch) (ipad) UDID = 4BFA3613-08B8-46D5-BCAC-78039408EA2A Supports Watch Apps = no iPad Pro (12.9-inch) (ipad) UDID = 868DFF1A-14B3-4777-A869-C224DB03FDB9 Supports Watch Apps = no iPad Pro (12.9-inch) (2nd generation) (ipad) UDID = FB3F1436-F508-4506-935D-DAE52D471F62 Supports Watch Apps = no iPad Pro (10.5-inch) (ipad) UDID = 48E2DACC-8088-498F-AE3A-6AC57765F848 Supports Watch Apps = no iPad (6th generation) (ipad) UDID = 6D93B6DB-0DD7-4B37-B457-0014A26541BC Supports Watch Apps = no iPad Pro (11-inch) (ipad) UDID = 0598FBBD-2E5C-4D84-A740-00F82127606C Supports Watch Apps = no iPad Pro (12.9-inch) (3rd generation) (ipad) UDID = 3CFD35BC-000A-4DDA-8D6F-12EA0E3D65AD Supports Watch Apps = no iPhone 8 (iphone) UDID = 7103E089-D840-4E38-880F-F866F82C11BB Supports Watch Apps = yas iPhone 8 Plus (iphone) UDID = 82158C5A-DF40-4F5B-87B4-D7E1D89B481B Supports Watch Apps = yas iPhone X (iphone) UDID = EB7D2396-3C3E-49F7-855A-A7048F711D85 Supports Watch Apps = yas iPhone Xs (iphone) UDID = DD79AF7C-958B-42DA-AF87-D18DCBBD445F Supports Watch Apps = yas iPhone Xs Max (iphone) UDID = A1CD9662-68BE-41E6-B34C-3A5F5D6A5FB4 Supports Watch Apps = yas iPhone XΚ (iphone) UDID = C7B6BD99-6789-4612-8876-9C3D46D03C21 Supports Watch Apps = yas iPhone 6s (iphone) UDID = D85DB69F-33C5-400B-A794-751EF4E7AA12 Supports Watch Apps = yas iPhone 6s Plus (iphone) UDID = F34F3DEE-2D3C-438A-AB5A-21D18EB27F74 Supports Watch Apps = yas iPhone SE (iphone) UDID = C9D04CCE-E8DD-4173-955B-E7EFC8C57D20 Supports Watch Apps = yas iPhone 7 (iphone) UDID = 30CE1F77-B0A3-4886-BBA8-6F1AFD7EA3FF Supports Watch Apps = yas iPhone 7 Plus (iphone) UDID = 7279613C-5A28-4766-93FC-4752B305BDB3 Supports Watch Apps = yas WatchOS Simulators 6.0 Apple Watch Series 2 - 38mm (watch) UDID = A7A2BBE8-E649-403B-B54C-0B6CD90F6E38 Apple Watch Series 2 - 42mm (watch) UDID = 5D0D7BA0-14EE-41D7-8E4A-CC1A722DAB96 Apple Watch Series 3 - 38mm (watch) UDID = FD47DD68-833B-43BB-8259-4289D9CB61FC Apple Watch Series 3 - 42mm (watch) UDID = 17301FDF-385A-4450-A23D-51F65A8E2571 Apple Watch Series 4 - 40mm (watch) UDID = F83123F5-681F-4286-8F73-3B700A49DB4E Apple Watch Series 4 - 44mm (watch) UDID = B566DFDB-A2E0-4540-BA0A-B7157E6E75FE Connected iOS Devices None iOS Issues ! Unable to find any valid iOS distribution provisioning profiles. This will prevent you from packaging apps for AppStore distribution. You will need to log in to http://appcelerator.com/ios-dist-certs with your Apple Developer account, then create, download, and install a profile. ! Unable to find any valid iOS production distribution certificates. This will prevent you from packaging apps for distribution. You will need to log in to http://appcelerator.com/ios-dist-certs with your Apple Developer account, then create, download, and install a certificate. ! Multiple Xcode versions have not had their EULA accepted: 10.3 (/Applications/Xcode-10.3.app) Launch each Xcode and accept the license. {code}
| 2 |
181 |
DAEMON-284
|
09/17/2019 17:14:55
|
Fix offline support
|
The daemon doesn't work as expected without an Internet connection. Problems arise with installing default plugins and sending telemetry info. There may be other areas.
| 8 |
182 |
DAEMON-285
|
09/24/2019 11:18:38
|
Unsubscribe in external plugin service dispatcher not called when forcefully closing connection
|
Canceling a subscription to a service dispatcher in external plugins won't properly trigger the cleanup logic since the plugin isn't notified about the end of response stream like it is happening in internal plugins. *Steps to reproduce the behavior* # Open a subscription to any internal plugin, e.g. {{appcd exec /appcd/status/system/memory --subscribe}}, and then cancel the subscription by CTRL+C # Notice that the subscription will be properly cleaned up as indicated by the following logs: {code} 2019-09-24T10:15:47.154Z appcd:http:webserver 127.0.0.1:59795 disconnected 2019-09-24T10:15:47.155Z appcd:http:webserver 127.0.0.1:59795 closed WebSocket 2019-09-24T10:15:47.155Z appcd:service-dispatcher cleanup 2019-09-24T10:15:47.155Z appcd:service-dispatcher Stream ended, cleaning up 2019-09-24T10:15:47.155Z appcd:service-dispatcher [782e2d4a-b194-4f9a-806f-9b3cfc47b2f3] Unsubscribing: system.memory 2019-09-24T10:15:47.155Z appcd:service-dispatcher [782e2d4a-b194-4f9a-806f-9b3cfc47b2f3] No more listeners, removing descriptor: system.memory 2019-09-24T10:15:47.156Z appcd:service-dispatcher [782e2d4a-b194-4f9a-806f-9b3cfc47b2f3] Calling service's destroySubscription(): system.memory 2019-09-24T10:15:47.156Z appcd:data-service-dispatcher Removing gawk watch 2019-09-24T10:15:47.156Z appcd:core:websocket-session stream ended 2019-09-24T10:15:47.157Z appcd:core:websocket-session [0] 127.0.0.1:59795 [finish] /appcd/status/system/memory 200 2874ms {code} # Now, do the same for an external plugin, e.g. run {{appcd exec /titanium/latest/sdk --subscribe}} and then cancel the subscription by CTRL+C # No subscription cleanup is done as you can see in the following logs {code} 2019-09-24T10:10:04.797Z appcd:http:webserver 127.0.0.1:59613 disconnected 2019-09-24T10:10:04.797Z appcd:http:webserver 127.0.0.1:59613 closed WebSocket 2019-09-24T10:10:04.798Z appcd:core:websocket-session stream ended 2019-09-24T10:10:04.798Z appcd:core:websocket-session [0] 127.0.0.1:59613 [finish] /titanium/latest/sdk 200 7006ms {code} *Actual behavior* Subscriptions in external plugins are not properly cleaned up and a service dispatchers {{onUnsubscribe}} and {{destroySubscription}} are not being called. *Expected behavior* A subscriptions cleanup logic is properly being executed for external plugins.
| 13 |
183 |
DAEMON-287
|
10/24/2019 18:22:25
|
Remove winreglib dependency from appcd-response
|
appcd-response is used by several packages such as appcd-subprocess which is used by non-appcd projects. appcd-response needs to detect the locale in order to display the appropriate message. On Windows machines, the locale is retrieved from the Windows Registry. Previously, [email protected] uses appcd-winreg (now deprecated) which in turned used winreg to simply spawn the {{reg.exe}} command and query the registry. When appcd-winreg was sunset, it was replaced with the new winreglib, a native Node.js addon. Now when a non-appcd project uses something like appcd-subprocess, it will depend on winreglib and that complicates install issues for specific environments such as Atom plugins on Linux. The solution here is to replace appcd-response's winreglib dependency with two simple {{spawnSync()}} calls.
| 5 |
184 |
DAEMON-288
|
10/25/2019 20:26:07
|
SIGINT triggered in core process
|
When a process spawns {{appcd start}}, then that process is interrupted via CTRL-C (aka SIGINT), then the core daemon process receives the SIGINT also and shutsdown. The daemon should not be receiving the SIGINT.
| 8 |
185 |
DAEMON-306
|
11/18/2019 20:05:52
|
iOS info missing watch info in simRuntimes with the cli 7.1.2-master.6
|
When testing via studio the watch simulators were not shown when using Appc CLI 7.1.2-master.6. It works fine with older appc cli builds. Running the command "appc appcd exec /ios/latest/info" noticed that the simRumtimes are missing the info related to watch.
| 8 |
186 |
DAEMON-307
|
12/06/2019 19:31:38
|
Plugins not installed if access denied to yarn links directory
|
If the yarn links directory exists, but access is denied, it blows up and the daemon does not properly install any plugins. {code} 2019-12-06T17:56:15.849Z appcd:default-plugins Found yarn: /Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/.bin/yarn 2019-12-06T17:56:15.881Z appcd:default-plugins Found lerna: /Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/.bin/lerna 2019-12-06T17:56:15.886Z appcd:server warn { Error: EACCES: permission denied, scandir '/Users/lchoudhary/.config/yarn/link' 2019-12-06T17:56:15.886Z appcd:server warn at Object.readdirSync (fs.js:790:3) 2019-12-06T17:56:15.886Z appcd:server warn at GlobSync._readdir (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/glob/sync.js:288:41) 2019-12-06T17:56:15.886Z appcd:server warn at GlobSync._processReaddir (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/glob/sync.js:137:22) 2019-12-06T17:56:15.886Z appcd:server warn at GlobSync._process (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/glob/sync.js:132:10) 2019-12-06T17:56:15.886Z appcd:server warn at new GlobSync (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/glob/sync.js:48:10) 2019-12-06T17:56:15.886Z appcd:server warn at Function.globSync [as sync] (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/glob/sync.js:26:10) 2019-12-06T17:56:15.886Z appcd:server warn at /Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/lib/globule.js:94:17 2019-12-06T17:56:15.886Z appcd:server warn at /Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/lib/globule.js:29:32 2019-12-06T17:56:15.886Z appcd:server warn at arrayEach (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/node_modules/lodash/lodash.js:516:11) 2019-12-06T17:56:15.886Z appcd:server warn at Function.forEach (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/node_modules/lodash/lodash.js:9342:14) 2019-12-06T17:56:15.886Z appcd:server warn at processPatterns (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/lib/globule.js:25:5) 2019-12-06T17:56:15.886Z appcd:server warn at Object.globule.find (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/globule/lib/globule.js:93:17) 2019-12-06T17:56:15.886Z appcd:server warn at find (/Users/lchoudhary/.appcelerator/install/8.0.0-master.2/package/node_modules/appcd-default-plugins/dist/index.js:119:28) 2019-12-06T17:56:15.886Z appcd:server warn errno: -13, 2019-12-06T17:56:15.886Z appcd:server warn syscall: 'scandir', 2019-12-06T17:56:15.886Z appcd:server warn code: 'EACCES', 2019-12-06T17:56:15.886Z appcd:server warn path: '/Users/lchoudhary/.config/yarn/link' } {code} Reading the yarn links directory is an optional check and thus we simply need to gracefully handle access and continue to install the plugins.
| 5 |
187 |
DAEMON-308
|
01/06/2020 18:42:07
|
Plugin manager telemetry doesn't wait for initialization
|
The {{PluginManager}} scans the initial plugin paths and then enables telemetry. The problem is detecting the plugin schemas is async and the {{PluginManager}} constructor does not properly block the enabling of telemetry events. This behavior is leading to events unnecessary telemetry events being generated during start for each plugin.
| 8 |
188 |
DAEMON-309
|
01/07/2020 18:41:40
|
Add appcd plugin API version
|
The Appc Daemon's plugin system allows plugins to specify which appcd version they are compatible with, however we have to ship new plugins for each major plugin version whenever we bump the appcd major version regardless if the plugin system actually changed. Since the plugin system rarely changes, we shouldn't couple plugins with the appcd version, but rather a separate plugin API version. For example, the iOS appcd plugin 1.x is compatible with every appcd version, but iOS appcd plugin 2.x requires appcd version 3.x because of changes to appcd-detect that is passed into each plugin.
| 13 |
189 |
DAEMON-310
|
01/14/2020 10:22:10
|
@appcd/plugin-android: Fails to start with Error: Recursively watching root is not permitted
|
H5.Description When attempting to start the android plugin I'm getting the below error, this works fine on CLI 7.1.2 (plugin version 1.3.0/appcd version 1.1.3) and CLI 8.0.0-master.4 (plugin version 1.5.2/appcd 3.1.0) (note are we not choosing to lock down plugin versions per default-plugin release, this re-introduces the risk that we had previously worked to eliminate) {code} { "stack": "Error: Recursively watching root is not permitted\n at register (/Users/awam/git/appc-cli/node_modules/appcd-fswatcher/dist/fswatcher.js:967:10)\n at new FSWatcher (/Users/awam/git/appc-cli/node_modules/appcd-fswatcher/dist/fswatcher.js:893:19)\n at FSWatchManager.onSubscribe (/Users/awam/git/appc-cli/node_modules/appcd-fswatch-manager/dist/fswatch-manager.js:81:19)\n at FSWatchManager.subscribe (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/service-dispatcher.js:206:18)\n at FSWatchManager.handler (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/service-dispatcher.js:108:11)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:196:23)\n at Dispatcher.call (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:230:16)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:189:26)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:172:12)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:172:12)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:172:12)\n at dispatch (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:172:12)\n at Dispatcher.call (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:230:16)\n at Function.call (/Users/awam/git/appc-cli/node_modules/appcd-dispatcher/dist/dispatcher.js:84:26)\n at handler (/Users/awam/git/appc-cli/node_modules/appcd-plugin/dist/external-plugin.js:519:55)\n at EventEmitter.onMessage (/Users/awam/git/appc-cli/node_modules/appcd-plugin/dist/tunnel.js:92:4)", "message": "Recursively watching root is not permitted", "status": 400, "statusCode": "400.1", "type": "error" } {code} h5.Steps to reproduce 1. Install appc cli 8.0.0-master.5 from preprod 2. Start the daemon {{appc appcd start}} 3. Call the android endpoints {{appc appcd exec /android/1.x/info}} and {{appc appcd exec /android/2.x/info}} h5.Actual Above error h5.Expected No error, android info should be returned
| 8 |
190 |
DAEMON-313
|
02/06/2020 17:01:00
|
Remove Genymotion
|
The time has come to remove support for Genymotion. The Android emulator has matured and thanks to advances in virtualization technology, it is quite fast. Secondly, Genymotion is not free and it's not like they ever gave us any licenses. Thirdly, we don't want to maintain a second emulator technology, especially one that has only does x86 emulation and often causes incompatibility issues with Titanium native modules. 1. Remove the [code|https://github.com/appcelerator/appc-daemon/blob/bf20fec94c74e055e4359a8e123539054c4cb228/packages/appcd-core/src/server.js#L482-L486] in appcd-core that copies the Genymotion config from the Titanium CLI's config to the appcd config. Bump minor. 2. Deprecate [@appcd/plugin-genymotion|https://github.com/appcelerator/appcd-plugin-genymotion]. 3. Remove all references to Genymotion and VirtualBox in [@appcd/plugin-android|https://github.com/appcelerator/appcd-plugin-android]. Bump major. 4. Remove all references to Genymotion in [@appcd/plugin-system-info|https://github.com/appcelerator/appcd-plugin-system-info]. Bump major. 5. Remove all references to Genymotion and VirtualBox in [@appcd/plugin-titanium|https://github.com/appcelerator/appcd-plugin-titanium]. Bump major. Since we're removing data from the info, this is breaking change and everything (except appcd itself) must have a major version bump.
| 13 |
191 |
DAEMON-314
|
02/07/2020 15:24:05
|
Add plugin API version to appcd status
|
It would be helpful if the appcd status also displayed the plugin API version.
| 5 |
192 |
DAEMON-315
|
02/07/2020 16:04:26
|
Docs: Appc Daemon releases with plugin API, Node versions
|
Document Appc Daemon releases and their plugin API versions. For the meantime, this can go in the markdown docs in the repo.
| 5 |
193 |
DAEMON-316
|
02/07/2020 16:35:29
|
Docs: Generate release notes
|
Each appcd package has a changelog, but there's no high-level release notes that consolidates the changelogs. It would be beneficial to have a tool that pulled determined Appc Daemon releases and merge the release notes per version.
| 8 |
194 |
DAEMON-317
|
02/10/2020 14:55:03
|
Titanium CLI: Call latest major version of Titanium appc plugin
|
The Titanium appcd plugin ships with the Titanium CLI as well as the Appc Daemon default plugins (which is going to change). If the Titanium CLI references @appcd/[email protected], but the default plugins references v1.2.0, then the Titanium CLI should call 1.2.0, not 1.1.0. To solve this, simply call the major version: {code} `/titanium/${semver.major(packageJson.dependencies['@appcd/plugin-titanium'])}/<service>` {code}
| 8 |
195 |
DAEMON-319
|
02/11/2020 07:03:40
|
appcd-core: Upgrade to latest Node.js 12 LTS release
|
While the daemon supports Node 10, we should update the core to Node 12 so that we can use the latest features such as workers. Node.js doesn't gain us much as far as removing Babel transpilation. We could switch over to ES modules, but we still need to transpile for dynamic imports and optional chaining. We probably cannot remove Babel until Node 14 goes LTS in late 2020.
| 2 |
196 |
DAEMON-322
|
02/11/2020 15:59:43
|
androidlib: NDK side-by-side support
|
*Summary:* As of 2019, Google introduced a new NDK "side-by-side" feature which allows you to install multiple NDK versions under the Android SDK directory. All new NDK versions are downloaded to the side-by-side directory and it replaces the old "ndk-bundle" directory. *Example:* The folder structure appear as follows on macOS... {{~/Library/Android/sdk/ndk/19.2.5345600}} {{~/Library/Android/sdk/ndk/20.1.5948922}} {{~/Library/Android/sdk/ndk/21.0.5935234}} {{~/Library/Android/sdk/ndk/21.0.6113669}} There will be an "ndk" directory under the "Android/sdk" directory. Each subdirectory under "ndk" will be the version number of the installed NDK. *Old Behavior:* Before the NDK side-by-side feature existed, Android Studio used to install the NDK under the Android SDK directory as shown below. Updating the NDK version used to replace the old version. Android Studio no longer installs to this directory. {{~/Library/Android/sdk/ndk-bundle}} *To be done:* The CLI should search for the installed NDK directory in the following order. # The "ANDROID_NDK" environment variable, if set. # The newest NDK side-by-side version subdirectory, if available. # The "ndk-bundle" directory.
| 8 |
197 |
DAEMON-326
|
02/13/2020 15:43:16
|
@appcd/plugin-titanium: Add terminal session server with discovery endpoint
|
The Titanium CLI needs bi-directional communication with the Titanium plugin, however the Appc Daemon dispatcher is not capable of supporting true bi-directional data flow, but rather just single request, multi-part responses. To work around this, we need the Titanium CLI to locate the Appc Daemon, start it, ensure the Titanium appcd plugin is registered, and call a terminal discovery endpoint. From there, the Titanium CLI will connect to the terminal session endpoint via a WebSocket.
| 8 |
198 |
DAEMON-328
|
02/13/2020 22:45:40
|
appcd-plugin: Registered plugins not sorted when retrieving status for semver range
|
When getting the status of a plugin where the version is a semver range, it will scan all plugins for a match by name and version. The order of the registered plugins is whichever order they were loaded. The list of plugins must be sorted in order to deterministically find the plugin. If you have @appcd/plugin-titanium v1.6.0 and v1.8.1 installed, getting the status for {{^1.6.0}} should return v1.8.1. {code} appcd exec /appcd/plugin/status/@appcd/plugin-titanium/^1.6.0 {code}
| 3 |
199 |
DAEMON-329
|
02/26/2020 23:13:24
|
node_winreglib.node is not a valid Win32 application
|
User installs Appc Daemon 3.2.0 with Node.js 10.13.0. When the daemon starts up, the Windows plugin cannot load winreglib: {code} { "stack": "PluginError: Failed to load plugin: \\\\?\\C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\winreglib\\build\\Release\\node_winreglib.node is not a valid Win32 application.\r\n\\\\?\\C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\winreglib\\build\\Release\\node_winreglib.node\n at Object.Module._extensions..node (internal/modules/cjs/loader.js:807:18)\n at PluginModule.load (internal/modules/cjs/loader.js:653:32)\n at Function.load (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\appcd-plugin\\dist\\plugin-module.js:71:11)\n at PluginModule.require (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\appcd-plugin\\dist\\plugin-module.js:142:23)\n at require (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\appcd-plugin\\dist\\plugin-module.js:181:36)\n at load (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\node-gyp-build\\index.js:21:10)\n at Object.apply (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\winreglib\\src\\index.js:2:46)\n at PluginModule._compile (C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\appcd-plugin\\dist\\plugin-module.js:196:19)\n at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)\n at PluginModule.Module.load (internal/modules/cjs/loader.js:653:32)", "message": "Failed to load plugin: \\\\?\\C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\winreglib\\build\\Release\\node_winreglib.node is not a valid Win32 application.\r\n\\\\?\\C:\\Users\\Test\\.appcelerator\\install\\8.0.0-master.10\\package\\node_modules\\winreglib\\build\\Release\\node_winreglib.node", "status": 400, "statusCode": "400.1", "type": "error" } {code} Note that winreglib uses N-API and is compatible with Node.js 10.2.0 and newer and that the Appc Daemon 3.2.0's core runs Node 10.16.3. This might be a Windows-only issue as Windows is general the only platform in which plugins are installed at daemon install time, Mac/Linux run into permission issues and have to resort to installing plugins at runtime. This behavior will change in DAEMON-311
| 8 |
200 |
DAEMON-330
|
02/26/2020 23:18:07
|
Lerna cannot find Yarn when installing default plugins on Windows
|
appcd-default-plugins can find Yarn, but Lerna cannot. Probably a bug that is easily reproducible on a clean Windows machine as a dev machine likely has Yarn already installed. System is running Node.js 10.13.0. Appc Daemon core is running Node.js 10.16.3. {code} 2020-02-26T22:39:32.624Z appcd:default-plugins Found yarn: C:\Users\Test\.appcelerator\install\8.0.0-master.10\package\node_modules\.bin\yarn.cmd 2020-02-26T22:39:32.669Z appcd:default-plugins Found lerna: C:\Users\Test\.appcelerator\install\8.0.0-master.10\package\node_modules\.bin\lerna.cmd 2020-02-26T22:39:32.683Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.685Z appcd:default-plugins warn Plugin directory name mismatch: @appcd/[email protected] found in @appcd/plugin-android, invalidating... 2020-02-26T22:39:32.695Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.697Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.698Z appcd:default-plugins warn Plugin directory name mismatch: @appcd/[email protected] found in @appcd/plugin-system-info, invalidating... 2020-02-26T22:39:32.705Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.706Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.707Z appcd:default-plugins warn Plugin directory name mismatch: @appcd/[email protected] found in @appcd/plugin-windows, invalidating... 2020-02-26T22:39:32.714Z appcd:default-plugins Found installed plugin @appcd/[email protected] 2020-02-26T22:39:32.898Z appcd:default-plugins warn Skipping incompatible plugin: @appcd/plugin-ios@^1.5.2 2020-02-26T22:39:32.903Z appcd:default-plugins Downloading @appcd/[email protected] 2020-02-26T22:39:32.907Z appcd:default-plugins warn Skipping incompatible plugin: @appcd/plugin-ios@^2.0.2 2020-02-26T22:39:32.910Z appcd:default-plugins Downloading @appcd/[email protected] 2020-02-26T22:39:32.913Z appcd:default-plugins Downloading @appcd/[email protected] 2020-02-26T22:39:33.045Z appcd:default-plugins Writing plugins/package.json 2020-02-26T22:39:33.049Z appcd:default-plugins Writing plugins/lerna.json 2020-02-26T22:39:33.051Z appcd:default-plugins Plugins dir: C:\Users\Test\.appcelerator\appcd\plugins 2020-02-26T22:39:33.052Z appcd:default-plugins Executing: C:\Users\Test\.appcelerator\install\8.0.0-master.10\package\node_modules\.bin\lerna.cmd bootstrap --no-progress 2020-02-26T22:39:34.085Z appcd:default-plugins:lerna cli v3.20.2 2020-02-26T22:39:34.112Z appcd:default-plugins:lerna versioning independent 2020-02-26T22:39:34.200Z appcd:default-plugins:lerna bootstrap root only 2020-02-26T22:39:34.249Z appcd:default-plugins:lerna 'yarn' is not recognized as an internal or external command, 2020-02-26T22:39:34.251Z appcd:default-plugins:lerna operable program or batch file. 2020-02-26T22:39:34.254Z appcd:default-plugins:lerna lerna ERR! yarn install --mutex network:42424 --non-interactive --emoji=false --ignore-engines --no-lockfile --no-progress --production exited 2 in 'root' 2020-02-26T22:39:34.255Z appcd:default-plugins:lerna lerna ERR! yarn install --mutex network:42424 --non-interactive --emoji=false --ignore-engines --no-lockfile --no-progress --production exited 2 in 'root' 2020-02-26T22:39:34.268Z appcd:default-plugins warn lerna exited with code 2 {code} This ticket may moot with the new plugin management command (DAEMON-311) and the upgrade to Yarn 2 (DAEMON-318).
| 8 |
201 |
DAEMON-331
|
03/02/2020 14:07:23
|
Windows - Android: "No Android SDKs were found under the specified location"
|
When trying to create an application in Appcelerator Studio the following message can be seen in the application creation screen. "No Android SDKs were found under the specified location". When doing an {{appc appcd status}} from the CLI the following can be seen in the plugins section: {code:java} Plugin Version Type Path Node.js Status Active/Total Requests android 1.5.2 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-android\1.5.2 10.16.3 Inactive: Failed to load plugin: No native build was found for platform=win32 arch=x64 runtime=node abi=64 uv=1 libc=glibc 0 / 0 android 2.0.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-android\2.0.1 10.16.3 Inactive 0 / 0 genymotion 1.6.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-genymotion\1.6.1 10.16.3 Inactive: Failed to load plugin: No native build was found for platform=win32 arch=x64 runtime=node abi=64 uv=1 libc=glibc 0 / 0 jdk 1.6.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-jdk\1.6.1 10.16.3 Inactive: Failed to load plugin: No native build was found for platform=win32 arch=x64 runtime=node abi=64 uv=1 libc=glibc 0 / 0 system-info 1.5.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-system-info\1.5.1 10.16.3 Active, PID=5764 0 / 2 system-info 2.0.0 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-system-info\2.0.0 10.16.3 Inactive 0 / 0 titanium 1.8.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-titanium\1.8.1 10.16.3 Inactive: Failed to load plugin: No native build was found for platform=win32 arch=x64 runtime=node abi=64 uv=1 libc=glibc 0 / 0 windows 1.5.2 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-windows\1.5.2 10.16.3 Active, PID=2008 1 / 1 windows 2.0.1 external C:\Users\APPC\.appcelerator\appcd\plugins\packages\@appcd\plugin-windows\2.0.1 10.16.3 Inactive {code}
| 1 |
202 |
DAEMON-332
|
03/03/2020 17:47:37
|
appcd-default-plugins: Yarn and Lerna not found from Appc CLI on Windows
|
appcd-default-plugins locates lerna and yarn by their {{.cmd}} bin script. However, since the Appc CLI package is built on a Linux machine, npm doesn't create the {{.cmd}} files and thus is not able to find them. While appcd-default-plugins would have no problem resolving the lerna and yarn bin scripts directly, {{lerna bootstrap}} calls {{yarn}} and expects the shell (e.g. cmd.exe) to locate the {{.cmd}} file and run it. So, we need the {{.cmd}} files. Adding the {{.cmd}} files to the Appc CLI package when it's being built is probably too much work, instead we can to generate them using the same {{bin-links}} package npm uses.
| 5 |
203 |
DAEMON-334
|
03/06/2020 07:29:55
|
appcd: Drop support for Node 8 and older
|
Node 8 is no longer in maintenance after Dec 31, 2019 and npm dependencies are starting to depend on Node 10 as a minimum. In Daemon 4.0, we need to bump the minimum supported Node version to {{>=10.2.0}}. We choose 10.2.0 so that we get N-API 3 needed by native deep dependencies.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.