Git Product home page Git Product logo

titanium-cli's Introduction

Titanium CLI

Titanium CLI is a Command Line Tool for creating and building Titanium Mobile applications and modules. It's open-source and easy to use. We've designed Titanium to be suitable for command line beginners, but still be powerful and extensible enough for production usage.

Prerequisites

The Titanium CLI requires Node.js 18 or newer.

Installation

[sudo] npm install -g titanium

After install, Titanium CLI is executable as ti or titanium.

Obtaining a Titanium SDK

You will need to download a Titanium SDK:

# stable release (recommended)
titanium sdk install

Setting up the Titanium CLI

Before you begin using the Titanium CLI, you should configure it by running the "setup" command:

titanium setup

Usage

titanium <command> [options]

Built-in Commands

config

Configure your CLI settings.

# list all config settings
titanium config

# get a config setting
titanium config <key>

# set a config setting
titanium config <key> <value>

help

Displays help or help for a specific command.

ti

titanium --help

titanium <command> --help

sdk

Download and install Titanium SDKs

sdk install

Installs a specific version of the Titanium SDK. If no version is specified, it assumes the latest.

titanium sdk install

titanium sdk install <version>

titanium sdk install <version> --force

sdk uninstall

Uninstalls a Titanium SDK.

titanium sdk uninstall <version>

sdk list

Lists all installed Titanium SDKs. Optionally lists all branches and releases.

titanium sdk list

titanium sdk list -r
titanium sdk list --releases

setup

Reconfigures the Titanium CLI by asking you a series of questions.

titanium setup

version

Displays the current version of the CLI and exits.

titanium -v

titanium --version

info

Displays information about your development environment including Xcode installs, iOS SDKs, Android SDKs, and so on.

titanium info

titanium info --json

Hacking the Titanium CLI

In order to begin hacking on the Titanium CLI, you need to download and install git.

If you have already installed a previous version of the Titanium CLI, it's recommended you uninstall the old one first:

[sudo] npm uninstall -g titanium

The Titanium CLI is essentially pure JavaScript, so there is no build process. You just need to pull the code and resolve the dependendencies.

git clone [email protected]:tidev/titanium-cli.git
cd titanium-cli
npm install
sudo npm link

Running Unit Tests

To run the unit tests, simply run:

npm test

Contributing

Interested in contributing? There are several ways you can help contribute to this project.

New Features, Improvements, Bug Fixes, & Documentation

Source code contributions are always welcome! Before we can accept your pull request, you must sign a Contributor License Agreement (CLA). Please visit https://tidev.io/contribute for more information.

Donations

Please consider supporting this project by making a charitable donation. The money you donate goes to compensate the skilled engineeers and maintainers that keep this project going.

Code of Conduct

TiDev wants to provide a safe and welcoming community for everyone to participate. Please see our Code of Conduct that applies to all contributors.

Security

If you find a security related issue, please send an email to [email protected] instead of publicly creating a ticket.

Stay Connected

For the latest information, please find us on Twitter: Titanium SDK and TiDev.

Join our growing Slack community by visiting https://slack.tidev.io!

Legal

Titanium is a registered trademark of TiDev Inc. All Titanium trademark and patent rights were transferred and assigned to TiDev Inc. on 4/7/2022. Please see the LEGAL information about using our trademarks, privacy policy, terms of usage and other legal information at https://tidev.io/legal.

titanium-cli's People

Contributors

caspahouzer avatar cb1kenobi avatar cheekiatng avatar dependabot-preview[bot] avatar dependabot[bot] avatar esasse avatar ewanharris avatar feons avatar fokkezb avatar greenkeeper[bot] avatar greenkeeperio-bot avatar hansemannn avatar hieupham007 avatar ingo avatar janvennemann avatar jhaynie avatar joshualambert avatar m1ga avatar muhammaddadu avatar nebrius avatar samueldowse avatar sgtcoolguy avatar skypanther avatar srahim avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

titanium-cli's Issues

An in-range update of husky is breaking the build 🚨

The devDependency husky was updated from 2.6.0 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

husky is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit cannot be built (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Commits

The new version differs by commits ahead by 0, behind by 24.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

How to make a backwards-compatible Titanium module?

Title says it all: is it possible to make Titanium modules that are backwards-compatible with Titanium apps that are lower than 7.0.0GA?

I tried to set the minsdk value in manifest for my module to 6.0.4GA but Appcelerator doesn't allow me to add it for apps lower than 7.0.0GA.

How can I make a backwards-compatible Titanium module built with Titanium 7.0.0GA?

Cli-commands in Mobile SDK

I tried to execute the commands from titanium, I have this error in Linux.

[ERROR] The 2.0.2.GA of the SDK does not support this CLI tool

Do I need a more recent version? I checked the code and it searches for a 'cli-commands' directory inside my mobile sdk path, but there's no directory.

Thank you very much for you nice work,

Javi.

xcode project wont find node

Titanium CLI 3.0.9

When i generate a titanium mobile project and try to run it it wont build.
It tells me that it cant find "node"
If i change the prebuild command from

node "/usr/local/bin/titanium" build --platform iphone --sdk 3.1.0 --no-prompt --no-banner --xcode
exit $?

to

/usr/local/bin/node "/usr/local/bin/titanium" build --platform iphone --sdk 3.1.0 --no-prompt --no-banner --xcode
exit $?

Then it works.
Looking at log. In the xcode build process, PATH does not contain /usr/local/bin

Titanium 3.2 wont install properly

$ sudo npm install -g alloy titanium

Then I get:

/usr/local/etc/bin/ti -> /usr/local/etc/lib/node_modules/titanium/bin/titanium /usr/local/etc/bin/titanium -> /usr/local/etc/lib/node_modules/titanium/bin/titanium

Then I run:

$ titanium -v

returns:

3.1.2

I've also run

$ npm list -g titanium

returns:

/usr/local/share/npm/lib
└── [email protected]

Assets folder doesn't work for CommonJS modules

Hello!
There is my question on the forum http://developer.appcelerator.com/question/158947/localization-in-commonjs-module-for-ios

I'm developing a CommonJS module and I want to add localization files in it. I've successfully added localization files for android, but not for iOS.
The common way using assets folder works for iOS native modules, but it doesn't work for CommonJS modules.

As far as I see, titanium ignores assets folder in CommonJS modules.

An in-range update of danger is breaking the build 🚨

The devDependency danger was updated from 9.1.8 to 9.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Release 9.2.0
  • CHANGELOG (007f8a7)
  • bump down version (b4a9697)
  • Merge pull request #915 from kristof0425/feat/add-buddy-works-ci (77325ea)
  • Merge branch 'master' into feat/add-buddy-works-ci (9705c53)
  • Merged by Peril (c3eecbd)
  • Merge branch 'master' into feat/add-buddy-works-ci (8a2f7fc)
  • Merge branch 'master' into master (5e3668a)
  • Merge pull request #916 from danger/fix_ci (f30f9d0)
  • Merge branch 'master' into fix_ci (d6873a9)
  • Blocks PRs which change the package version, and moves the integration tests to node 10 now that the github package has a minimum of 10 (215e79d)
  • docs(BuddyWorks): add CI setup comment (d346570)
  • chore: bump version, update changelog (b67d492)
  • docs(README): add Buddy.works to supported CI sources (5730ec4)
  • feat(ci_source): add Buddy.works (8664c19)
  • Merge branch 'master' into master (562bf75)
  • Merge pull request #912 from nguyenhuy/patch-1 (58ec25f)
  • Update CHANGELOG.md (0dd3132)
  • Improve docs for GitHub Actions (5a053c6)
  • docs: updated changelog for jira/issues check, 🤖🦍🐙 (f3d81c0)
  • feat: added flag to bypass jira/issues check, 🤖🦍🐙 (c9034b2)
Commits

The new version differs by 21 commits.

  • eeea80f Release 9.2.0
  • 007f8a7 CHANGELOG
  • b4a9697 bump down version
  • 77325ea Merge pull request #915 from kristof0425/feat/add-buddy-works-ci
  • 9705c53 Merge branch 'master' into feat/add-buddy-works-ci
  • c3eecbd Merged by Peril
  • 8a2f7fc Merge branch 'master' into feat/add-buddy-works-ci
  • 5e3668a Merge branch 'master' into master
  • f30f9d0 Merge pull request #916 from danger/fix_ci
  • d6873a9 Merge branch 'master' into fix_ci
  • 215e79d Blocks PRs which change the package version, and moves the integration tests to node 10 now that the github package has a minimum of 10
  • d346570 docs(BuddyWorks): add CI setup comment
  • b67d492 chore: bump version, update changelog
  • 5730ec4 docs(README): add Buddy.works to supported CI sources
  • 8664c19 feat(ci_source): add Buddy.works

There are 21 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from 5.13.0 to 5.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit cannot be built (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v5.14.0
  • 85a04b3 Fix: adds conditional for separateRequires in one-var (fixes #10179) (#10980) (Scott Stern)
  • 0c02932 Upgrade: [email protected] (#11401) (Ilya Volodin)
  • 104ae88 Docs: Update governance doc with reviewers status (#11399) (Nicholas C. Zakas)
  • ab8ac6a Fix: Support boundary spread elements in sort-keys (#11158) (Jakub Rożek)
  • a23d197 New: add allowSingleLineBlocks opt. to padded-blocks rule (fixes #7145) (#11243) (richie3366)
  • e25e7aa Fix: comma-spacing ignore comma before closing paren (fixes #11295) (#11374) (Pig Fang)
  • a1f7c44 Docs: fix space-before-blocks correct code for "classes": "never" (#11391) (PoziWorld)
  • 14f58a2 Docs: fix grammar in object-curly-spacing docs (#11389) (PoziWorld)
  • d3e9a27 Docs: fix grammar in “those who says” (#11390) (PoziWorld)
  • ea8e804 Docs: Add note about support for object spread (fixes #11136) (#11395) (Steven Thomas)
  • 95aa3fd Docs: Update README team and sponsors (ESLint Jenkins)
  • 51c4972 Update: Behavior of --init (fixes #11105) (#11332) (Nicholas C. Zakas)
  • ad7a380 Docs: Update README team and sponsors (ESLint Jenkins)
  • 550de1e Update: use default keyword in JSON schema (fixes #9929) (#11288) (Pig Fang)
  • 983c520 Update: Use 'readonly' and 'writable' for globals (fixes #11359) (#11384) (Nicholas C. Zakas)
  • f1d3a7e Upgrade: some deps (fixes #11372) (#11373) (薛定谔的猫)
  • 3e0c417 Docs: Fix grammar in “there’s nothing prevent you” (#11385) (PoziWorld)
  • de988bc Docs: Fix grammar: Spacing improve -> Spacing improves (#11386) (PoziWorld)
  • 1309dfd Revert "Build: fix test failure on Node 11 (#11100)" (#11375) (薛定谔的猫)
  • 1e56897 Docs: “the function actually use”: use -> uses (#11380) (PoziWorld)
  • 5a71bc9 Docs: Update README team and sponsors (ESLint Jenkins)
  • 82a58ce Docs: Update README team and sponsors (ESLint Jenkins)
  • 546d355 Docs: Update README with latest sponsors/team data (#11378) (Nicholas C. Zakas)
  • c0df9fe Docs: ... is not an operator (#11232) (Felix Kling)
  • 7ecfdef Docs: update typescript parser (refs #11368) (#11369) (薛定谔的猫)
  • 3c90dd7 Update: remove prefer-spread autofix (fixes #11330) (#11365) (薛定谔的猫)
  • 5eb3121 Update: add fixer for prefer-destructuring (fixes #11151) (#11301) (golopot)
  • 173eb38 Docs: Clarify ecmaVersion doesn't imply globals (refs #9812) (#11364) (Keith Maxwell)
  • 84ce72f Fix: Remove extraneous linefeeds in one-var fixer (fixes #10741) (#10955) (st-sloth)
  • 389362a Docs: clarify motivation for no-prototype-builtins (#11356) (Teddy Katz)
  • 533d240 Update: no-shadow-restricted-names lets unassigned vars shadow undefined (#11341) (Teddy Katz)
  • d0e823a Update: Make --init run js config files through linter (fixes #9947) (#11337) (Brian Kurek)
  • 92fc2f4 Fix: CircularJSON dependency warning (fixes #11052) (#11314) (Terry)
  • 4dd19a3 Docs: mention 'prefer-spread' in docs of 'no-useless-call' (#11348) (Klaus Meinhardt)
  • 4fd83d5 Docs: fix a misleading example in one-var (#11350) (薛定谔的猫)
  • 9441ce7 Chore: update incorrect tests to fix build failing (#11354) (薛定谔的猫)
Commits

The new version differs by 38 commits.

  • af9688b 5.14.0
  • 0ce3ac7 Build: changelog update for 5.14.0
  • 85a04b3 Fix: adds conditional for separateRequires in one-var (fixes #10179) (#10980)
  • 0c02932 Upgrade: [email protected] (#11401)
  • 104ae88 Docs: Update governance doc with reviewers status (#11399)
  • ab8ac6a Fix: Support boundary spread elements in sort-keys (#11158)
  • a23d197 New: add allowSingleLineBlocks opt. to padded-blocks rule (fixes #7145) (#11243)
  • e25e7aa Fix: comma-spacing ignore comma before closing paren (fixes #11295) (#11374)
  • a1f7c44 Docs: fix space-before-blocks correct code for "classes": "never" (#11391)
  • 14f58a2 Docs: fix grammar in object-curly-spacing docs (#11389)
  • d3e9a27 Docs: fix grammar in “those who says” (#11390)
  • ea8e804 Docs: Add note about support for object spread (fixes #11136) (#11395)
  • 95aa3fd Docs: Update README team and sponsors
  • 51c4972 Update: Behavior of --init (fixes #11105) (#11332)
  • ad7a380 Docs: Update README team and sponsors

There are 38 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

CLI not working on Ubuntu 13.10

I am currently running node v0.10.15. When I install CLI v 3.2.0 either via npm -g or via git clone and run ti -v I get the correct version output i.e. (3.2.0). However, if I simply run "ti" I get:

michael@michael-Bonobo-Extreme:/usr/local/lib/node_modules/titanium$ ti
Titanium Command-Line Interface, CLI version 3.2.0, Titanium SDK version 3.1.3.GA
Copyright (c) 2012-2013, Appcelerator, Inc.  All Rights Reserved.

Please report bugs to http://jira.appcelerator.org/

[ERROR] "/usr/local/bin/ti" is an unrecognized command.

Run 'node help' for available commands.

if I simply checkout 3.1.2 instead:

git checkout tags/3.1.2
sudo npm install

Than run ti, i get the correct output and am able to use/compile apps just fine. I've tried npm cache clean, uninstall, unlink binaries...etc Nothing works with 3.2.0 CLI for me in Ubuntu 13.10. If do however have the 3.2.0 SDK installed and can see with 3.1.2 CLI:

michael@michael-Bonobo-Extreme:/usr/local/lib/node_modules/titanium$ ti sdk
Titanium Command-Line Interface, CLI version 3.1.2, Titanium SDK version 3.1.3.GA
Copyright (c) 2012-2013, Appcelerator, Inc.  All Rights Reserved.

Please report bugs to http://jira.appcelerator.org/

Installed SDKs:
3.2.0.GA           /home/michael/.titanium/mobilesdk/linux/3.2.0.GA
3.1.3.GA [active]  /home/michael/.titanium/mobilesdk/linux/3.1.3.GA
3.1.1.GA           /home/michael/.titanium/mobilesdk/linux/3.1.1.GA

If I activate 3.2.0.GA the CLI obviously complains about the CLI version.

Error occurs : tiapp.xml generated by TitaniumCLI

Using the Command Line , android emulator & android device transfer fails with the tiapp.xml generated by TitaniumCLI.(command: titanium create)

I could not find a part of the problem,
You can be overcome in the following ways:

You obediently by the generating a from TitaniumStuidio , you can get the exact tiapp.xml.
Use this exact tiapp.xml , android build from the command line you will be available.

I hope so , exact tiapp.xml is now generated by the command.
I'm sorry they become poor English, I hope you will be helpful.

Error: CreateProcessW: The system cannot find the file specified.

Hi,
i am get the error:

"Error: CreateProcessW: The system cannot find the file specified." on build command.
I`am on WinXP. Project is created with CLI and PATHS to Java, Node and Android SDK are set.

U:\webnexx\helloworld>titanium.cmd build
Titanium Command-Line Interface, CLI version 3.0.24, Titanium SDK version 3.0.3.v20130301174549
Copyright (c) 2012-2013, Appcelerator, Inc.  All Rights Reserved.

Please report bugs to http://jira.appcelerator.org/

Target platform [android,mobileweb]: android

[DEBUG] No project level plugins to load
[DEBUG] Loaded plugin hooks:
[DEBUG] D:\Dokumente und Einstellungen\roeber\Anwendungsdaten\Titanium\mobilesdk\win32\3.0.3.v20130301174549\cli\hooks\plugin
s.js
[DEBUG] D:\Dokumente und Einstellungen\roeber\Anwendungsdaten\Titanium\mobilesdk\win32\3.0.3.v20130301174549\android\cli\hook
s\install.js
[DEBUG] D:\Dokumente und Einstellungen\roeber\Anwendungsdaten\Titanium\mobilesdk\win32\3.0.3.v20130301174549\android\cli\hook
s\run.js
CreateProcessW: Das System kann die angegebene Datei nicht finden.
[ERROR] Project failed to build after 31ms

[ERROR] Project failed to build after 32ms

Specify build type (ipa vs app)

There does not currently seem to be any support for specifying whether the build should produce an ipa or an app similar to how the studio allows you to specify.

It would be nice to be able to do:

titanium build
  --platform ios
  --pp-uuid xxx-xxx
  --distribution-name cert-name-xxx
  --target dist-adhoc
  --output-dir ./build
  --output-type app

Alloy compiler failed (cannot find module <project>/undefined)

I have a titanium mobile project. I am trying to run it from the command line. I do:

$ npm install titanium -g
$ titanium sdk install 3.5.0.GA
$ titanium build --platform=iphone

and I get this error:

[INFO]  Deploy type: development
[INFO]  Building for target: simulator
[INFO]  Building using iOS SDK: 8.2
[INFO]  Building for iOS Simulator: iPhone 4s
[DEBUG] UDID: F0598C60-FAF3-414E-8333-E4124DDC177A
[DEBUG] Simulator type: iphone
[DEBUG] Simulator version: 8.2
[INFO]  Building for device family: universal
[DEBUG] Setting Xcode target to Debug
[DEBUG] Setting Xcode build OS to iphonesimulator8.2
[DEBUG] Xcode installation: /Applications/Xcode.app/Contents/Developer
[DEBUG] iOS WWDR certificate: installed
[INFO]  Minimum iOS version: 7.0
[INFO]  Debugging disabled
[INFO]  Profiler disabled
[INFO]  Forcing rebuild: /Users/connorleech/Proteus/app-ti-pasteboardWriter/build/iphone/build-manifest.json does not exist
[INFO]  Initiating prepare phase
[INFO]  Found Alloy app in /Users/connorleech/Proteus/app-ti-pasteboardWriter/app
[INFO]  Executing Alloy compile: /usr/local/bin/node  compile /Users/connorleech/Proteus/app-ti-pasteboardWriter/app --config platform=ios,version=0,simtype=none,devicefamily=universal,deploytype=development,target=simulator
[DEBUG] module.js:340
[DEBUG]     throw err;
[DEBUG]           ^
[ERROR] : Cannot find module '/Users/connorleech/Proteus/app-ti-pasteboardWriter/undefined'
[DEBUG]     at Function.Module._resolveFilename (module.js:338:15)
[DEBUG]     at Function.Module._load (module.js:280:25)
[DEBUG]     at Function.Module.runMain (module.js:497:10)
[DEBUG]     at startup (node.js:119:16)
[DEBUG]     at node.js:906:3
[ERROR] Alloy compiler failed

I want to run the app in my iOS simulator. Running it on an ipad simulator would be best. What am I doing wrong?

Getting missing file app.js

Hi,

What is happening is that I had a app that was working fine. I deleted it from my sim. Then I tried to reload the app and I got this error:

[ERROR] Error loading path: file:///Users/bradenpowers/Library/Application%20Support/iPhone%20Simulator/7.0.3/Applications/627F3E26-8B17-470F-B675-3703ADA87843/Citadel%20Mobile.app/app.js, Error Domain=NSCocoaErrorDomain Code=260 "The operation couldn’t be completed. (Cocoa error 260.)" UserInfo=0xd068210 {NSFilePath=/Users/bradenpowers/Library/Application Support/iPhone Simulator/7.0.3/Applications/627F3E26-8B17-470F-B675-3703ADA87843/Citadel Mobile.app/app.js, NSUnderlyingError=0xd0681b0 "The operation couldn’t be completed. No such file or directory"}
[ERROR] Script Error Could not find the file app.js

I get the same error using the CLI or Studio. It is an Alloy project.

Titanium Create New App with Cloud-Enable option

Hey Guys,
I'm happy to use Titanium CLI.
But i don't find the way to create new app with cloud-enable option(ACS).
Please let me know how to create new app with cloud-enable option by cli.
Thanks.

An in-range update of lint-staged is breaking the build 🚨

The devDependency lint-staged was updated from 8.1.4 to 8.1.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v8.1.5

8.1.5 (2019-03-01)

Bug Fixes

  • fix issue with scoped pkg listr-update-renderer (#587) (63b085f), closes #585
Commits

The new version differs by 2 commits.

  • 63b085f fix: fix issue with scoped pkg listr-update-renderer (#587)
  • 1303573 docs: Update screencast and installation instructions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of danger is breaking the build 🚨

The devDependency danger was updated from 7.0.12 to 7.0.13.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

danger is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for Release 7.0.13
  • Adds more debug logs for babel (0ceecd5)
Commits

The new version differs by 2 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version sanity check fails on "3.0-BETA3-1-g18104da"

[ERROR] tiapp.xml contains an invalid version "3.0-BETA3-1-g18104da"
[ERROR] The version may only contist of letters, numbers, dashes, underscores, pluses, and spaces.

Not sure what's going on here, does it not like the .?

Error ubuntu (Linux) 13.04 with NodeJs 10.12

adam@ntio λ sudo npm install titanium -g
npm http GET https://registry.npmjs.org/titanium
npm http 304 https://registry.npmjs.org/titanium
npm http GET https://registry.npmjs.org/longjohn
npm http GET https://registry.npmjs.org/node-appc/0.1.30
npm http GET https://registry.npmjs.org/revalidator
npm http GET https://registry.npmjs.org/prompt
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/sprintf
npm http GET https://registry.npmjs.org/temp/0.4.0
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/wrench
npm http GET https://registry.npmjs.org/winston
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/node-appc/0.1.30
npm http 304 https://registry.npmjs.org/revalidator
npm http 304 https://registry.npmjs.org/prompt
npm http 304 https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/node-appc/-/node-appc-0.1.30.tgz
npm http GET https://registry.npmjs.org/revalidator/-/revalidator-0.1.5.tgz
npm http 304 https://registry.npmjs.org/sprintf
npm http 304 https://registry.npmjs.org/temp/0.4.0
npm http 304 https://registry.npmjs.org/wrench
npm http 304 https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/temp/-/temp-0.4.0.tgz
npm http 304 https://registry.npmjs.org/winston
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/longjohn
npm http GET https://registry.npmjs.org/async/-/async-0.1.0.tgz
npm http 200 https://registry.npmjs.org/node-appc/-/node-appc-0.1.30.tgz
npm http 200 https://registry.npmjs.org/revalidator/-/revalidator-0.1.5.tgz
npm http 200 https://registry.npmjs.org/temp/-/temp-0.4.0.tgz
npm http 200 https://registry.npmjs.org/async/-/async-0.1.0.tgz
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/read
npm http GET https://registry.npmjs.org/utile
npm http GET https://registry.npmjs.org/eyes
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/stack-trace
npm http GET https://registry.npmjs.org/cycle
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/xmldom/0.1.11
npm http GET https://registry.npmjs.org/uglify-js
npm http 304 https://registry.npmjs.org/read
npm http 304 https://registry.npmjs.org/utile
npm http 304 https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/mute-stream
npm http GET https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/eyes
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/ncp
npm http 304 https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/stack-trace
npm http 304 https://registry.npmjs.org/cycle
npm http 304 https://registry.npmjs.org/node-uuid
npm http 304 https://registry.npmjs.org/xmldom/0.1.11
npm http GET https://registry.npmjs.org/xmldom/-/xmldom-0.1.11.tgz
npm http 304 https://registry.npmjs.org/uglify-js
npm http 304 https://registry.npmjs.org/mute-stream
npm http 304 https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/ncp
npm http 200 https://registry.npmjs.org/xmldom/-/xmldom-0.1.11.tgz
/usr/bin/titanium -> /usr/lib/node_modules/titanium/bin/titanium
/usr/bin/ti -> /usr/lib/node_modules/titanium/bin/titanium
[email protected] /usr/lib/node_modules/titanium
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected])
adam@ntio λ titanium --help

/usr/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:181
        throw e;
              ^
TypeError: Object #<Object> has no method 'readdirSyncRecursive'
    at Object.<anonymous> (/usr/lib/node_modules/titanium/node_modules/node-appc/lib/messaging.js:49:21)
    at Module._compile (module.js:456:26)
    at Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at /usr/lib/node_modules/titanium/node_modules/node-appc/lib/appc.js:51:34
    at Array.forEach (native)
    at Object.<anonymous> (/usr/lib/node_modules/titanium/node_modules/node-appc/lib/appc.js:50:3)
---------------------------------------------
    at exports.execFile (child_process.js:691:9)
    at exports.exec (child_process.js:578:18)
    at detectLocale (/usr/lib/node_modules/titanium/lib/titanium.js:53:4)
    at setLocale (/usr/lib/node_modules/titanium/lib/titanium.js:60:3)
    at /usr/lib/node_modules/titanium/lib/titanium.js:78:4
    at Object.<anonymous> (/usr/lib/node_modules/titanium/lib/titanium.js:85:3)
    at Module._compile (module.js:456:26)
    at Module._extensions..js (module.js:474:10)

to upgrade or install 'titanium' from npm with node js 10.12, generates an error

TypeError: Bad argument

Hi I'm trying to build to android the project but i'm getting one error in subprocess

I'm not sure what exactly that errors means i could not figure out how to solve that...

Titanium Version: 3.2.3
Command: titanium build -b -p android

Last Message

[INFO]  Packaging application: null "package" "-f" "-m" "-J" "/var/www/project/build/android/gen" "-M" "/var/www/project/build/android/AndroidManifest.xml" "-A" "/var/www/project/build/android/bin/assets" "-S" "/var/www/project/build/android/res" "-I" "/home/vagrant/android/android-sdk-linux/platforms/android-19/android.jar" "-I" "/home/vagrant/.titanium/mobilesdk/linux/3.2.2.GA/android/titanium.jar" "-F" "/var/www/project/build/android/bin/app.ap_"

Error Message

child_process.js:933
  var r = this._handle.spawn(options);
                       ^
TypeError: Bad argument
    at ChildProcess.spawn (child_process.js:933:24)
    at exports.spawn (child_process.js:733:9)
    at Object.run (/home/vagrant/.titanium/mobilesdk/linux/3.2.2.GA/node_modules/node-appc/lib/subprocess.js:48:14)
    at AndroidBuilder.<anonymous> (/home/vagrant/.titanium/mobilesdk/linux/3.2.2.GA/android/cli/commands/_build.js:3501:20)
    at /usr/local/node/node-v0.10.28/lib/node_modules/titanium/lib/hook.js:232:13
    at /usr/local/node/node-v0.10.28/lib/node_modules/titanium/node_modules/async/lib/async.js:232:13
    at async.eachSeries (/usr/local/node/node-v0.10.28/lib/node_modules/titanium/node_modules/async/lib/async.js:130:20)
    at _asyncMap (/usr/local/node/node-v0.10.28/lib/node_modules/titanium/node_modules/async/lib/async.js:226:9)
    at Object.mapSeries (/usr/local/node/node-v0.10.28/lib/node_modules/titanium/node_modules/async/lib/async.js:216:23)
    at async.series (/usr/local/node/node-v0.10.28/lib/node_modules/titanium/node_modules/async/lib/async.js:549:19)

Using XCode to run app on device wont work

Titanium CLI 3.0.9

I use xcode a lot to debug on device. I need this especially when i use motion sensors, gps ....
Since the integration of node as the build system, i am facing quite a problem, XCode wont correctly launch the app on my device.
I think that what s really happening is that the app package is not correctly done an maybe even not correctly copied

  • remove the app from your device
  • clean
  • build in ti studio
  • launch the xcode project
  • run on device
    Then you get this error
[DEBUG] Loading: /var/mobile/Applications/92E009DA-982E-4BED-8857-525A93A84EE0/Pif Paf.app/app.js, Resource: app_js
[ERROR] Error loading path: file://localhost/var/mobile/Applications/92E009DA-982E-4BED-8857-525A93A84EE0/Pif%20Paf.app/app.js, Error Domain=NSCocoaErrorDomain Code=260 "The operation couldn’t be completed. (Cocoa error 260.)" UserInfo=0x522b730 {NSFilePath=/var/mobile/Applications/92E009DA-982E-4BED-8857-525A93A84EE0/Pif Paf.app/app.js, NSUnderlyingError=0x522d850 "The operation couldn’t be completed. No such file or directory"}
[ERROR] Script Error = Could not find the file app.js.

ios app wont run on ipad simulator

Titanium Studio Version: 3.0.1.201210221016-7m7fFDDFFdIwz-iduRTbXqLuKQbz
Node CLI 3.0.9
Using the new node system i cant run, from ti studio, my app on ipad simulator. It will always launch the iphone simulator.

Even if i open the simulator, switch to ipad device, run from ti .studio. It still is the iphone simulator.

An in-range update of lint-staged is breaking the build 🚨

The devDependency lint-staged was updated from 9.0.1 to 9.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit cannot be built (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v9.0.2

9.0.2 (2019-07-03)

Bug Fixes

  • run all commands returned by function linters (0dd0c94)
Commits

The new version differs by 3 commits.

  • 28da59a docs: fix ignore example glob
  • 0dd0c94 fix: run all commands returned by function linters
  • 146e6ce docs: add ignore glob example

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Toolchain silently ignores invalid quotes in tiapp.xml

When adding modules the toolchain will happily process the following:
<module platform=“iphone” version="1.0.0">com.example.test</module>
silently and then cause run-time module lookup failures.

Change it to:
<module platform="iphone" version="1.0.0">com.example.test</module>
and everything works correctly

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

  • #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

  • #3766: Make reporter constructor support optional options parameter (@plroebuck)
  • #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

🐛 Fixes

  • #3829: Use cwd-relative pathname to load config file (@plroebuck)
  • #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
  • #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

📖 Documentation

🔩 Other

  • #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
  • #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)
Commits

The new version differs by 28 commits.

  • f4fc95a Release v6.1.0
  • bd29dbd update CHANGELOG for v6.1.0 [ci skip]
  • aaf2b72 Use cwd-relative pathname to load config file (#3829)
  • b079d24 upgrade deps as per npm audit fix; closes #3854
  • e87c689 Deprecate this.skip() for "after all" hooks (#3719)
  • 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
  • 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
  • 586bf78 Update JS-YAML to address security issue (#3845)
  • d1024a3 Update doc examples "tests.html" (#3811)
  • 1d570e0 Delete "/docs/example/chai.js"
  • ade8b90 runner.js: "self.test" undefined in Browser (#3835)
  • 0098147 Replace findup-sync with find-up for faster startup (#3830)
  • d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
  • a3089ad update package-lock
  • 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

There are 28 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-mocha is breaking the build 🚨

The devDependency eslint-plugin-mocha was updated from 6.1.0 to 6.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 6.1.1

Bug Fixes

  • Fix no-setup-in-describe to allow Mocha suite config (#209)
Commits

The new version differs by 6 commits.

  • 185f36e 6.1.1
  • 1e32ad7 Merge pull request #209 from straub/fix/208-no-setup-in-describe-timeout
  • 64d1db4 Fix no-setup-in-describe to allow suite config call via computed member expression
  • 0d838d5 Test no-setup-in-describe on disallowed and computed member expressions
  • 0569acd Document no-setup-in-describe suite config exception
  • a34ccf9 Fix no-setup-in-describe to allow Mocha suite config

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Path must be a string. Received undefined

i run a simple hello world program which run in browser perfectly but when
deploying in android mobile it case the following error
...
...
[INFO] : Packaging application: /home/ankit/Android/Sdk/build-tools/24.0.0/aapt "package" "-f" "-m" "-J" "/home/ankit/Appcelerator_Studio_Workspace/Hello/build/android/gen" "-M" "/home/ankit/Appcelerator_Studio_Workspace/Hello/build/android/AndroidManifest.xml" "-A" "/home/ankit/Appcelerator_Studio_Workspace/Hello/build/android/bin/assets" "-S" "/home/ankit/Appcelerator_Studio_Workspace/Hello/build/android/res" "-I" "/home/ankit/Android/Sdk/platforms/android-23/android.jar" "-F" "/home/ankit/Appcelerator_Studio_Workspace/Hello/build/android/bin/app.ap_" "--auto-add-overlay" "--extra-packages" "ti.modules.titanium.ui:android.support.v7.appcompat:android.support.v7.cardview" "-S" "/tmp/116611-26251-glfet8.13w744pldi/res" "-S" "/tmp/116611-26251-2govyk.i30ytoi529/res" "-S" "/tmp/116611-26251-1coto6l.3oour9hpvi/res"
2016-07-11T11:10:27.847Z | ERROR | An uncaught exception was thrown!
Path must be a string. Received undefined
2016-07-11T11:10:27.848Z | ERROR | Path must be a string. Received undefined

An in-range update of eslint-config-axway is breaking the build 🚨

The devDependency eslint-config-axway was updated from 4.3.0 to 4.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-axway is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit cannot be built (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 10 commits.

  • 1d0501e chore(release): v4.4.0
  • e1fcf56 docs: add typescript setup to additional configurations
  • 851f1a7 fix: disable indent
  • 05f2f35 feat: support 2.x versions
  • 24f2c91 fix: override indent to match main setup
  • 1befd38 feat: add support for linting typescript
  • 9021c3b ci(jenkins): move shebang to line 1
  • 31886fc Merge pull request #24 from ewanharris/add_jenkins
  • 4acb048 chore(deps): update dependencies
  • 270503b ci: setup jenkins

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit cannot be built (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v5.16.0
  • dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
  • c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
  • 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
  • bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
  • b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
  • afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
  • 4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
  • f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
  • 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)
Commits

The new version differs by 11 commits.

  • ded2f94 5.16.0
  • ea36e13 Build: changelog update for 5.16.0
  • dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
  • c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
  • 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
  • bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
  • b452f27 Chore: Update README to pull in reviewer data (#11506)
  • afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
  • 4fe7eb7 Chore: use nyc instead of istanbul (#11532)
  • f16af43 Chore: fix formatters/table test (#11534)
  • 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Can only install SDK up to version 4.0.0.GA

Am I missing something here or can you only install SDK up to version 4.0.0.GA. If so there should be a note in the readme of this project (such that it is displayed on the git hub page) noting that the appcelerator SDKs including the titanium ones should now be installed via the https://www.npmjs.com/package/appcelerator package. Even better put this note in the help when you run this CLI's sdk function.

Cannot get hooks to work

I'm writing a hook as apart of TiNy so you can also do:

titanium ios

This should be doable using the hooks, just like the included tisdk3fixes hook manipulates the commands given.

However, when I add the hook it doesn't log anything when I call ti build or ti create etc. When I call ti or ti config it does log.

Are the hooks not implemented for build and create yet?

Install from npm error

Here is the output from where it breaks. Thanks:

npm ERR! error installing [email protected]
npm ERR! error installing [email protected]
npm http 304 https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/stack-trace

npm ERR! Error: No compatible version found: read@'>=1.0.0- <1.1.0-'
npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.0.2","0.0.3","0.1.0","0.1.1"]
npm ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:488:10)
npm ERR!     at next_ (/usr/local/lib/node_modules/npm/lib/cache.js:438:17)
npm ERR!     at next (/usr/local/lib/node_modules/npm/lib/cache.js:415:44)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:408:5
npm ERR!     at Object.saved [as oncomplete] (/usr/local/lib/node_modules/npm/lib/utils/npm-registry-client/get.js:147:7)
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>
npm ERR! 
npm ERR! System Darwin 12.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "titanium"
npm ERR! cwd /Users/david
npm ERR! node -v v0.6.8
npm ERR! npm -v 1.1.0-2
npm ERR! message No compatible version found: read@'>=1.0.0- <1.1.0-'
npm ERR! message Valid install targets:
npm ERR! message ["0.0.1","0.0.2","0.0.3","0.1.0","0.1.1"]
npm http 304 https://registry.npmjs.org/eyes
npm http 304 https://registry.npmjs.org/cycle

npm ERR! Error: ENOENT, no such file or directory '/usr/local/lib/node_modules/titanium/node_modules/___node-appc.npm/package/tools/7zip/7za.exe'
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>
npm ERR! 
npm ERR! System Darwin 12.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "titanium"
npm ERR! cwd /Users/david
npm ERR! node -v v0.6.8
npm ERR! npm -v 1.1.0-2
npm ERR! path /usr/local/lib/node_modules/titanium/node_modules/___node-appc.npm/package/tools/7zip/7za.exe
npm ERR! fstream_path /usr/local/lib/node_modules/titanium/node_modules/___node-appc.npm/package/tools/7zip/7za.exe
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory '/usr/local/lib/node_modules/titanium/node_modules/___node-appc.npm/package/tools/7zip/7za.exe'
npm ERR! errno {}
npm ERR! fstream_stack Object.oncomplete (/usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:204:26)
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/david/npm-debug.log
npm not ok

running ios app from ti studio: no log

Titanium CLI 3.0.9

when running an app on ios simulator from ti studio, i dont see the app log.

When i debug an app, it is at debug level and i see app log

Updating UI view elements slow

Hi,

I am having issues when displaying multiple labels (around 20 labels, inside views).
If I try to update them (color and text) via a XHR call result you seen the labels change value one by one.

So updating a view can take me 3-5 seconds, which just does not work in my case.
The question would be what is the best way to build a view that loads fast (create elements with proper data in them or update an empty shell?).

I have used createListView to build lists and use templates and that works pretty well, why is a simple view so slow??

NOTE: On the simulator I get rendering times under 100-200 ms and that's fine. On my old iphone 4 I get display times of 3-5 seconds so...

Thanks
Chris

An in-range update of eslint is breaking the build 🚨

The devDependency eslint was updated from 6.2.2 to 6.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.3.0
  • 0acdefb Chore: refactor code (#12113) (James George)
  • 52e2cf5 New: reportUnusedDisableDirectives in config (refs eslint/rfcs#22) (#12151) (Toru Nagashima)
  • 020f952 Update: enforceForSequenceExpressions to no-extra-parens (fixes #11916) (#12142) (Milos Djermanovic)
  • aab1b84 Fix: reset to the default color (#12174) (Ricardo Gobbo de Souza)
  • 4009d39 Fix: yoda rule produces invalid autofix with preceding yield (#12166) (Milos Djermanovic)
  • febb660 Fix: no-extra-boolean-cast invalid autofix with yield before negation (#12164) (Milos Djermanovic)
  • 4c0b70b New: support TypeScript at config initializer (fixes #11789) (#12172) (Pig Fang)
  • 94e39d9 Chore: use GitHub Actions (#12144) (Toru Nagashima)
  • e88f305 Chore: support es2020 in fuzz (#12180) (薛定谔的猫)
  • 00d2c5b Docs: corrected class extension example (#12176) (Marius M)
  • 31e5428 Chore: Fix wrong error object keys in test files (#12162) (Milos Djermanovic)
  • 197f443 Fix: func-name-matching crash on descriptor-like arguments (#12100) (Milos Djermanovic)
  • 644ce33 Fix: no-self-assign false positive with rest and spread in array (#12099) (Milos Djermanovic)
  • a81d263 Fix: fix message of function-paren-newline (#12136) (Pig Fang)
  • 77f8ed1 Chore: update blogpost template (#12154) (Toru Nagashima)
  • 6abc7b7 Docs: Document the exception in no-unsafe-negation (#12161) (Milos Djermanovic)
Commits

The new version differs by 18 commits.

  • 329e295 6.3.0
  • 94180da Build: changelog update for 6.3.0
  • 0acdefb Chore: refactor code (#12113)
  • 52e2cf5 New: reportUnusedDisableDirectives in config (refs eslint/rfcs#22) (#12151)
  • 020f952 Update: enforceForSequenceExpressions to no-extra-parens (fixes #11916) (#12142)
  • aab1b84 Fix: reset to the default color (#12174)
  • 4009d39 Fix: yoda rule produces invalid autofix with preceding yield (#12166)
  • febb660 Fix: no-extra-boolean-cast invalid autofix with yield before negation (#12164)
  • 4c0b70b New: support TypeScript at config initializer (fixes #11789) (#12172)
  • 94e39d9 Chore: use GitHub Actions (#12144)
  • e88f305 Chore: support es2020 in fuzz (#12180)
  • 00d2c5b Docs: corrected class extension example (#12176)
  • 31e5428 Chore: Fix wrong error object keys in test files (#12162)
  • 197f443 Fix: func-name-matching crash on descriptor-like arguments (#12100)
  • 644ce33 Fix: no-self-assign false positive with rest and spread in array (#12099)

There are 18 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Change color of device log to normal foreground color..

Please remove bright black color as the default device output logging color.
My reasoning is that the default color should always be the default terminal color, I find this quite distracting. I am not used to see this elsewhere either.

Studio: Error connecting to download server Ubuntu 14.04 LTS

Hi!

I'm running Appcelerator Studio x64 for Linux under Ubuntu 14.04 LTS.

And i'm already ran this commands below.

sudo apt-get install libjpeg62 libwebkitgtk-1.0-0
echo 'export MOZILLA_FIVE_HOME=/usr/lib/mozilla' >> ~/.bashrc

And, i do have ACS, Alloy, Titanium CLI and other stuff installed via NPM.
And, i do have Oracle-Java-7 installed.
And, i already ran this command "appc setup"

But still i having this error: http://imgur.com/5fOryax

If it helps, i followed this instruction: http://tutorialforlinux.com/2014/04/19/how-to-install-appcelerator-titanium-studio-on-ubuntu-14-04-trusty-lts-64bit-linux-step-by-step/
Is there a way to launch Appcelerator Studio in Ubuntu 14.04 LTS?

Versions of installed stuff:

NodeJS: v0.12.7
Alloy: 1.7.29
Acs: 1.0.32
Titanium CLI: 5.0.5
Titanium SDK: 4.0.0.GA [selected]  4.0.0.v20150518154210 /home/abraham/.titanium/mobilesdk/linux/4.0.0.GA

p.s. running this from terminal not helping (even Login button not works).

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.2.0 to 6.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/jenkins/branch: This commit looks good (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 11 commits.

  • ef6c820 Release v6.2.1
  • 9524978 updated CHANGELOG for v6.2.1 [ci skip]
  • dfdb8b3 Update yargs to v13.3.0 (#3986)
  • 18ad1c1 treat '--require esm' as Node option (#3983)
  • fcffd5a Update yargs-unparser to v1.6.0 (#3984)
  • ad4860e Remove extraGlobals() (#3970)
  • b269ad0 Clarify effect of .skip() (#3947)
  • 1e6cf3b Add Matomo to website (#3765)
  • 91b3a54 fix style on mochajs.org (#3886)
  • 0e9d8ad tty.getWindowSize is not a function inside a "worker_threads" worker (#3955)
  • 48da42e Remove jsdoc index.html placeholder from eleventy file structure and fix broken link in jsdoc tutorial (#3966)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Longjohn error with Titanium CLI (OSS version)

Hello, i'm using the open source versión of Appcelerator Titanium. I've followed this tutorial (https://github.com/m1ga/titanium_with_atom/blob/master/README.md) and installed those node packages: titanium, tisdk and alloy. I've installed the last Titanium SDK (4.1.0.GA).

My problem is when i do a "ti info" or a "ti build -p ...." i allways get this error:

//usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:195
throw e;
      ^
Error: spawn EACCES
at exports._errnoException (util.js:746:11)

My node versión is v0.12.7.

I've followed this workaround (https://community.appcelerator.com/topic/937/longjohn-js-throw-e-when-running-titanium-cli) and i've downgrade the longjohn version to 0.2.4 but now i get this error related with the same longjohn package:

 //usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:185
throw e;
      ^
ChildProcess.emit (events.js:110:17),maybeClose (child_process.js:1015:16),Socket.<anonymous> (child_process.js:1183:11),Socket.emit (events.js:107:17),Pipe.close (net.js:485:12)

Does anyone know how to resolve this issue? I can't develop anything with Titanium now.

sdk install - Global quiet flag not preventing progress bar output

When installing the sdk with the --quiet flag, I still get the progress bar. No test seems to be done it he sdk.js command file to test if this flag is set in the function handling the download reception.

Thus, the bar variable shouldn't be set at all in the « response » event handler, nor the function « tick » on the bar object in the « data » event handler.

Thanks in advance for fixing this !

Building for submission to app store fails

Running the command to package the application for app store submission results in an error.

ti build -p ios -T dist-appstore -R "<Company Name>" -P "<Distribution Certificate>"

[ERROR] :  titanium_prep failed to run (10)
[ERROR] :  This application cannot be built with the Titanium open source SDK because it is an Appcelerator Platform registered application. Please use the Appcelerator Platform CLI tools or Appcelerator Studio to build this application.

I've unregistered the application with Appcelerator and have tried using the SDK's greater than 4.X.X, all with the same result.

Http response doesn't work for iOS just for Android

Hello,
I have an issue.
I have this code :

xhr = Ti.Network.createHTTPClient();
xhr.setRequestHeader('Content-Type', 'application/json');
xhr.open('POST', 'http://adress/to/my/Valid/RESTapi/');
xhr.onload = function(){
alert("response " + this.responseText + " "+ JSON.stringify(this);
};
xhr.onerror = function(){
alert("error ss" + this.responseText);
};
var sending = [];
sending.push(SSObject(20021, 2));//returns json struct
xhr.send(JSON.stringify(sending));//send array with struct

In Android it response correctly, but in iOS I receive a empty array in 'this.responseText' and 'this' response just {url:'http://adress/to/my/Valid/RESTapi/' ,method: 'POST'}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.