0 Build Targets

[Sophrinix]

When I run ti info -t ios --output json
I get back a long json response of my simulators as expected.

However, when I open a titanium project with atom I get the following image

I am still troubleshooting this issue to get more information, but at this point your package is the only 3rd party package installed. I have tried this with 0.8.0, 0.7.1, 0.7.0

What are the list of packages you have installed with your atom editor. I am thinking there might be a dependency that isn't explicitly listed in the package.json

I am running a completely plain atom editor aside from having Titanium-Build package installed.

[HazemKhaled]

Same issue here, this package depend on Atom Build, we provide service while Atom Build has to listen to this.

Since Atom Build 0.49.0 days a go @noseglid stop refreshing targets with command build:select-active-target while we have to fill the list with iOS simulator or Android emulators and devices according user select, imagine if you need to re-open atom every time you connect new device to debug, also it'll be ugly to list around 25 same time.

If you have time to debug, see how we can re-fill the targets after the workspace open

# titanium-build.js:162
atom.commands.dispatch(atom.views.getView(atom.workspace), "build:select-active-target");

Workaround for now, return to Atom Build 0.48.0 apm install [email protected]

[noseglid]

With 0.49.0 the refresh was indeed moved from when build:select-active-target is triggered to package activation (or rather after all packages are activated). This was made to increase snappyness when build providers take a long time to provide targets.

You can, however, manually trigger the refresh with build:refresh-targets which may be issued in code or via the command palette. Will this help you?

[Sophrinix]

@noseglid I just tried build:refresh-targets (I let it auto complete and then selected it in the list) from the command palette. No such luck. Also this is now with titanium-build 0.8.1

[Sophrinix]

Btw. Running apm install [email protected] did work.

[noseglid]

Ah I understand the issue. This tool doesn't refresh the targets when settings on the provider is called.

The fix for this issue is to refresh all targets when settings is called. The tool can then register an on and off callback to make the build-package refresh targets if anything happen. Have a look on how this is done for the custom build tool

[jerry42]

So the package is simply not working ?

[HazemKhaled]

@jerry42 just use command as work around apm install [email protected]

@noseglid you pull request is welcome :)

[noseglid]

I am sorry but I do not have time or interest to fix this. The main reason I added support for build providers was so that I would not have to be involved in every build system and its development.

I am however happy to assist with any questions you may have regarding this functionality, as I did in above comment.