Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-23260] Windows: Logs don't appear from background/async threads

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionCannot Reproduce
Resolution Date2016-05-27T03:35:37.000+0000
Affected Version/sRelease 5.3.0
Fix Version/sn/a
ComponentsWindows
Labelsn/a
ReporterJonas Bjurhult
AssigneeKota Iguchi
Created2016-04-20T07:08:19.000+0000
Updated2017-07-26T03:25:49.000+0000

Description

Once index.js has been executed the following is shown in the log: [INFO] : Finished launching the application [INFO] : Waiting for app to connect to log relay -- End application log ------------------------------------------------------- This means that no asynchronous events in the code will be printed and debugging is quite hard to say the least.

Attachments

FileDateSize
setting.png2016-05-06T07:52:53.000+000075558

Comments

  1. Nazmus Salahin 2016-04-20

    Hello, Thanks for reporting. The phenomena that you described is not supposed to happen. It is possible to get error and debug log in the console for Windows Phone. Following is an example of console log that I get for an app on Windows Phone Emulator. 
       -- Start application log -----------------------------------------------------
   [INFO] :   Finished launching the application
   [INFO] :   Waiting for app to connect to log relay
   [ERROR] :  Number of buttons exceeds platform maximum (2), list will be truncated.
   [INFO] :   Disconnected from app
   -- End application log -------------------------------------------------------
    Please let us know the following things. 1. If it is happening every time for any code. 2. If your app is crashing. 3. Your environment details. 4. If it happening for some particular code in index.js please share it. *Environment*: *Device info:* Microsoft Lumia 640 *Node.js Version:* 0.12.7 *npm Version:* 2.11.3 *Titanium SDKs:* 5.2.2.GA and 5.2.1.GA *Java Development Kit Version:* 1.8.0_73 *Titanium CLI Version:* 5.0.5 *Appcelerator CLI Version:* 5.2.2 *Appcelerator Studio:* 4.5.0
  2. Jonas Bjurhult 2016-04-20

    My environment is: SDK 5.3.0.v20160418111755 appc info: Appcelerator Command-Line Interface, version 5.2.2 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. Operating System Name = Microsoft Windows 10 Pro Version = 10.0.10586 Architecture = 32bit # CPUs = 2 Memory = 4.0GB Node.js Node.js Version = 0.12.7 npm Version = 2.11.3 Appcelerator CLI Installer = 4.2.4 Core Package = 5.2.2 Titanium CLI CLI Version = 5.0.6 node-appc Version = 0.2.31 Titanium SDKs 5.4.0.v20160410215408 Version = 5.4.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\5.4.0.v20160410215408 Platforms = android, mobileweb, windows git Hash = 97fe3e2 git Timestamp = 04/10/16 21:54 node-appc Version = 0.2.35 5.4.0.v20160330202802 Version = 5.4.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\5.4.0.v20160330202802 Platforms = android, mobileweb, windows git Hash = 15320e5 git Timestamp = 03/30/16 20:28 node-appc Version = 0.2.35 5.4.0.v20160301084038 Version = 5.4.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\5.4.0.v20160301084038 Platforms = android, mobileweb, windows git Hash = 071c19c git Timestamp = 03/01/16 08:40 node-appc Version = 0.2.35 5.3.0.v20160418111755 Version = 5.3.0 Install Location = C:\ProgramData\Titanium\mobilesdk\win32\5.3.0.v20160418111755 Platforms = android, mobileweb, windows git Hash = 7c38ca5 git Timestamp = 04/18/16 11:17 node-appc Version = 0.2.33 Intel® Hardware Accelerated Execution Manager (HAXM) Not installed Java Development Kit Not found Genymotion Path = not found Genymotion Executable = not found Genymotion Player = not found Home = not found VirtualBox Executable = not found Version = unknown Android SDK Android Executable = not found ADB Executable = not found SDK Path = not found Android NDK NDK Path = not found NDK Version = not found Android Platforms None Android Add-Ons None Android Emulators None Genymotion Emulators None Connected Android Devices None Microsoft (R) Visual Studio 14.0 (selected) Path = C:\Program Files (x86)\Microsoft Visual Studio 14.0\ CLR Version = v4.0.30319 MSBuild Version = v14.0.24730.2 Windows Phone SDKs = not installed Microsoft (R) Windows Phone SDK 10.0 Path = C:\Program Files (x86)\Windows Kits\10\ 8.1 (selected) Path = C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\ Windows PowerShell Enabled = yes Windows Phone Emulators 8.1 Emulator 8.1 WVGA 4 inch 512MB UDID 8-1-1 Emulator 8.1 WVGA 4 inch UDID 8-1-2 Emulator 8.1 WXGA 4.5 inch UDID 8-1-3 Emulator 8.1 720P 4.7 inch UDID 8-1-4 Emulator 8.1 1080P 5.5 inch UDID 8-1-5 Emulator 8.1 1080P 6 inch UDID 8-1-6 10.0 Windows Phone Devices Device UDID 0 Java Development Kit Issues × JDK (Java Development Kit) not installed. If you already have installed the JDK, verify your JAVA_HOME environment variable is correctly set. The JDK is required for must be manually downloaded and installed from http://appcelerator.com/jdk. Android Issues × JDK (Java Development Kit) not found. If you already have installed the JDK, verify your JAVA_HOME environment variable is correctly set. The JDK can be downloaded and installed from http://appcelerator.com/jdk.
  3. Jonas Bjurhult 2016-04-20

    1. If it is happening every time for any code. Yes, it is 100% reproducible. My colleague who is working on the same project does not get this error however. 2. If your app is crashing. No, not that I'm aware of. 3. Your environment details. See comment above 4. If it happening for some particular code in index.js please share it. I will try to isolate this in a minimal app and get back to you later with details.
  4. Jonas Bjurhult 2016-04-20

    I can reproduce this by creating a new default alloy app: index.js: 
       function doClick(e) {
       Ti.API.info("Hi there");
       alert($.label.text);
   }
   
   $.win.open();
    index.xml: 
       <Alloy>
   	<Window class="container" id="win">
   		<Label id="label" onClick="doClick">Hello, World</Label>
   	</Window>
   </Alloy>
    The log says: -- Start application log ----------------------------------------------------- [INFO] : Finished launching the application [INFO] : Waiting for app to connect to log relay [INFO] : ACS Login Results for environment development: [INFO] [object Object] -- End application log ------------------------------------------------------- The Ti.API.info("Hi there"); is not printed when I click the label
  5. Jörgen Buder 2016-04-22

    Let me know if you need me to test anything in the backgournd service and the LOG marco you have there, that is the only problem I have on my host, but I know Win 10 seems more problematic...
  6. Kota Iguchi 2016-04-22

    Tested 5.3.0.v20160418111755 on Windows 10 but I was not able to reproduce this. [~jonasbjurhult] Do you set something special on your tiapp.xml? For example native module or Capabilities etc. I also wonders if there's some kind of firewall program running in background that prevents logger from running. Note that Titanium CLI uses specific port to receive log (I think it's around 8666.
  7. Jonas Bjurhult 2016-04-22

    I run a default installation of Windows 10 Pro in Parallels, no programs added beside the dev tools needed for Titanium development. I tried disabling windows firewall but still get the same result.
  8. Jonas Bjurhult 2016-04-29

    This works when running windows 8.1 enterprise so it is probably a Windows 10 problem
  9. Kota Iguchi 2016-05-06

    Just got Parallels for me. Titanium CLI logging worked for me on Windows 10 & Parallels on Mac. In order to logging work, I needed to change Parallels Networks sources to "*Wi-Fi*". !setting.png|thumbnail! As side note, I'm note sure if it's related but I enabled "Enable nested virtualization" according to [Installing the Windows Phone SDK](http://docs.appcelerator.com/platform/latest/#!/guide/Installing_the_Windows_Phone_SDK-section-43306274_InstallingtheWindowsPhoneSDK-RunningWindows8withParallels).
  10. Kota Iguchi 2016-05-07

    I have also experienced that I actually needed to sign out my local account from Windows, that's needed because Windows requires re-sign-in (or restart) to update Windows Hyper-V related configuration. Without sign-out, logging disconnected for me just like this ticket describes. Just in case, hope this helps.
  11. Kota Iguchi 2016-05-17

    [~jonasbjurhult] This still doesn't work for you? I've tried *Wi-Fi* network and "Enable nested virtualization" and then re-sigin-in worked for me like described above, and I'm interested to see if it works for you.
  12. Kota Iguchi 2016-05-27

    I try to reproduce this using Windows 10 + Parallels on Mac but had no luck. we may need more info to reproduce this.

JSON Source