[TIMOB-14267] LiveView - Running multiple instances of the application on iOS and Android, iOS instances lose connection to LiveView Server
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-07-10T00:56:14.000+0000 |
Affected Version/s | Release 3.1.1 |
Fix Version/s | 2013 Sprint 14, 2013 Sprint 14 Tooling, Release 3.1.2, Release 3.2.0 |
Components | LiveView |
Labels | n/a |
Reporter | Bert Grantges |
Assignee | Christian Sullivan |
Created | 2013-06-17T18:48:58.000+0000 |
Updated | 2013-12-03T20:09:21.000+0000 |
Description
When trying to run multiple instances of the application with Liveview enabled across multiple devices/platform notice that Android will continue to update, however iOS instances lose the connection and do not continue to update.
(have validated this against iOS on Device and iOS on Simulator).
See attached video for further clarification.
steps to reproduce:
1) enable an existing application (simple screen) for LiveView
2) run android and iOS builds (emulator/simulator)
3) make a change to the code
Expected Behavior:
Both instances of the application should update continuously
Actual Behavior:
Android will continue to update, however iOS will stop updating after it updates once. Simulator or Device will need to restart to show updates.
Attachments
File | Date | Size |
---|---|---|
Leor_log_20130628.zip | 2013-06-28T20:52:19.000+0000 | 18436 |
liveview-test-07032013-v.rtf | 2013-07-03T12:43:20.000+0000 | 62864 |
Screen Shot 2013-06-27 at Jun 27,1.19.43 PM.png | 2013-06-27T20:21:46.000+0000 | 188276 |
Screen Shot 2013-06-28 at 4.29.01 PM.png | 2013-06-28T20:50:55.000+0000 | 1059881 |
Screen Shot 2013-06-28 at 4.33.52 PM.png | 2013-06-28T20:51:36.000+0000 | 1069656 |
studiodiagnosticlog-07032013.rtf | 2013-07-03T12:43:20.000+0000 | 33000 |
studiolog-07032013.txt | 2013-07-03T12:43:20.000+0000 | 4653465 |
Bump - any updates on this?
Investigating now.
What are versions of liveview and Ti SDK are you using?
liveview 0.1.24 Studio 3.1.1.201306131423 SDK 3.1.1.GA
FYI - also just tried this with the latest SDK from nightly builds - 3.1.2.v20130624104600 Still shows the same behavior. Unable to run multiple instances of the application across devices simulator - after there is one app refresh all but the last connecting instance will cease to refresh
[~bgrantges] I'm more interested in the version of LiveView you are using. Is it still 0.1.24?
see my previous comment - LiveView 0.1.24 - The latest plugin. Bert
We updated the LiveView plugin on nightly and beta streams to 0.1.25, not the RC. I assume we don't yet want to push to RC until some QE confirmation.
[~mxia] Can you confirm if 0.1.25 fixes the issue above or if we need an additional fix? Once we have confirmed it works for us, then I can ask [~bgrantges] to test.
It isn't working yet from my testing. I'm running Appcelerator Studio, build: 3.1.1.201306131423 + LiveView Feature 1.0.0.201306251553, and the diagnostic log shows 0.1.25 LiveView is included. Here are my steps: 1. Create a classic two-tab project and run it on iOS simulator with LiveView enabled; 2. Updating the code, and the app reflects correctly right away; 3. Run the app on Android emulator with LiveView enabled; 4. Updating the code, and one time I saw a runtime error, and the other one I saw no update. Here is the log:
It appears LiveView server got disconnected when the Android emulator is launched.
This is happening because the liveview.js file is symlinked to the builds. So when android builds it replaces the server url in liveview.js with the android proxy url required to access external network ips (10.0.2.2). Since iOS is still symlinked to the same file it can no longer connect due to the new url being invalid.
Fixed in 0.1.26 https://github.com/appcelerator/liveview/commit/5375660cf1231ccfea12b2819687a47dcebc0a31
[~csullivan] I updated to 0.1.26 and ran into a runtime error when launching Android emulator with liveview. Attached the screenshot. Not sure if it's related to this issue itself.
I did a "killall node" from command line and re-launched; still saw the runtime error. Here is the relevant console output:
[~mxia] what does
return if you put it in your app.js and build without liveview
Needed to clean the project and re-build. Now iOS simulator and Android emulator are getting updated together. Did observe a behavior where if you exit Android emulator, iOS simulator will no longer get updated. Will open a separate ticket on it.
Opened TIMOB-14425.
I used an iPhone Sim and an Android AVD. I used the stock Alloy App with a button added to the screen. I edited the screen background (via tss) and the button position (via the xml file) I tested the 0.1.26 Beta of Liveview and it is definitely better than before but I still see several issues: (a) iPhone Simulator still loses connection while Android can be updated (b) I saw one runtime error on Android (c) There is a little trouble getting started where the iPhone wont launch the app and I need to run again; not sure of the 'correct' sequence (what to launch first) Logs and screen shots attached
Android Runtime Error happened only once (not repeatable)
iPhone Simulator stops updating after several modifications (with save each time)
Console, Studio Log and Studio Diagnostic Log
This is not resolved per my latest update and tests LiveView Version: 0.1.26 Titanium SDK: 3.1.2.v20130624104600 - Open up iOS Simulator and Android Emulator and install to both - Make a change to your XML file and save - iOS Simulator and Emulator update as expected (android update is VERY SLOW see APPTS-2291) - Make a change to the same file or another file and save - Android emulator updates eventually, iOS no longer responds Looking through the console output you can see that the iOS Simulator has disconnected see my attached logs/console output
Still witnessing this behavior with latest update of liveview. ReOpening
resolved in https://github.com/appcelerator/liveview/releases/0.1.27
For Appcelerator Studio, build: 3.1.2.201308091728 (containing LiveView 0.1.32), we only support updating one platform at a time when running with LiveView. Closing this ticket.