-
-
Notifications
You must be signed in to change notification settings - Fork 197
Console.log has no output on terminal #3118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have the same issue on the same CLI and runtime version but on Mac and with iOS as target platform. |
If I run the app with |
@bigradish and @NickIliev Did one of you try to use an older version of the CLI yet? I first thought it might be related to the XCode update and the new iOS 11, but as you're using Android on Windows those two things don't seem to be related. |
@christian-kolb I just upgraded to XCode 9 and iOS 11 and my console.log quit outputting to the terminal. Was working fine previous to updating XCode. Have not been able to get it working again. |
Same as glen-stephens |
Hey guys, Regarding the problem with Windows and Android - this is not related to the above issue. We will take a look and let you know. |
This comment was marked as abuse.
This comment was marked as abuse.
@etabakov If it helps, console.log does work to the terminal when running on an actual device, just not from the simulator. |
Here is a separate issue for iOS11 Simulator and Xcode9: #3141. Lets continue the discussion there. |
Why this issue has not received any process till now? |
Can confirm that You can test it out too in |
I am still facing the same issue? ios12 and xcode 9.4 |
Same issue here. ios12 and xcode 9.4. |
Hey guys, you need to update your Xcode in order to make |
From @bigradish on September 13, 2017 2:41
When I follow the steps in the "Debugging apps" section of your tutorial https://docs.nativescript.org/tutorial/chapter-1 , both console.log and console.dir have no output on the terminal.
More info:
Thank you.
Copied from original issue: NativeScript/NativeScript#4835
The text was updated successfully, but these errors were encountered: