[ALOY-510] Issue using 'alloy run' (deprecated) for building on iOS device
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Medium |
|---|
| Status | Closed |
|---|
| Resolution | Won't Fix |
|---|
| Resolution Date | 2013-03-08T22:58:12.000+0000 |
|---|
| Affected Version/s | Alloy 1.0.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | n/a |
|---|
| Labels | qe-sdk3.0.2 |
|---|
| Reporter | Federico Casali |
|---|
| Assignee | Tony Lukasavage |
|---|
| Created | 2013-02-07T20:02:12.000+0000 |
|---|
| Updated | 2014-08-06T22:10:32.000+0000 |
|---|
Description
Problem description
Not possible to specify the iOS certificates and run the app con device when running 'alloy run -p ios -T device'
Steps
From Terminal in any project folder, run 'alloy run -p ios -T device'.
The user is informed that the command is actually deprecated and to use 'titanium build' instead (alloy run will be removed with 1.1.0).
The user is then prompted with which 'iOS Developer Certificate' to use.
However, the cursor is not placed in the same line and pressing the return key does not generate the list of the available certificates, nor fillin in the certificate name produce any consequence.
Using 'ti build -p ios -T device' works fine as expected.
Comments
JSON Source
I'm content to leave this as is since "alloy run" is deprecated as of 1.0.0 and will be removed in 1.1.0 in favor of using "titanium build" directly. Thoughts?
The behavior I expect when encountering a 'deprecated' feature is that it still works as expected but I get a warning that will be soon replaced (or removed) in the upcoming release. I would then discontinue using the deprecated feature for the next rev. Since the deprecated feature should still function, it seems like we should fix this. However, it seems also acceptable to have 'alloy run' notify the user of the deprecation, inform to use instead 'titanium build' and then go right back to the prompt without executing any other action.
I guess I wasn't as concerned about this because it *_never_* worked from "alloy run". That being the case, that it never worked for ios device builds, do you still think it needs to support device builds?
'Alloy run' is no longer mentioned in the docs (http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Quick_Start-section-34636229_AlloyQuickStart-CompileandRun ), I think we can lower the severity.
"alloy run" is deprecated and will soon be removed, probably in Alloy 1.1.0