[TIMOB-15979] LiveView: LiveView will run a previously selected application if left turned on
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Cannot Reproduce |
|---|
| Resolution Date | 2013-12-17T18:15:47.000+0000 |
|---|
| Affected Version/s | Release 3.2.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | LiveView |
|---|
| Labels | qe-3.2.0 |
|---|
| Reporter | Samuel Dowse |
|---|
| Assignee | Christian Sullivan |
|---|
| Created | 2013-12-13T01:04:57.000+0000 |
|---|
| Updated | 2014-06-19T12:42:59.000+0000 |
|---|
Description
Description
If I run LiveView on a project it will run successfully. However I swap to another project in the same workspace with LiveView still enabled it will run the first project again.
Steps To Reproduce
1. Create a default classic project
2. Turn on LiveView and run on iOS simulator
3. Create a default alloy project
4. With LiveView still enabled run on iOS simulator
Expected Result
The new project should be install and running on the simulator
Actual Result
The classic app will run instead of the alloy app.
Comments
JSON Source
[~mxia] Can you verify? I am unable to reproduce.
[~mxia] This might be a studio issue since it does not seem to happen when called from the cli.
Hi Samuel, could you try with the latest Appcelerator Studio, which includes LiveView 1.0.1? I saw this issue before as well, but think it's due to an issue with looking into root app.js instead of platform-specific folder's app.js, and that has been fixed in the latest version. So far I have not seen the issue with the latest build.
Just attempted with the latest LiveView 1.0.1. I have successfully managed to launch a classic application on device with LiveView enabled. I then created a new alloy application and launched it keeping LiveView enabled and the previous app still open on device. The alloy project opened successfully and LiveView is changing the device code as I work as expected. +Extra Information+ In 'ti config' my paths.hooks was still linking to version 1.0.0 despite only having 1.0.1 installed. After manually changing that everything seems to be working as expected.