Empty Chrome DevTools when using tns debug ios for iOS Simulator

[rosen-vladimirov]

Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?

Yes

Tell us about the problem

When tns debug ios is used and a change in the application code is applied, Chrome DevTools should be reconnected. Once the change is applied on simulator, CLI prints the new URL that should be opened in Chrome DevTools (commonly it is the same as the previous one). In case you open this URL immediately, you'll receive empty DevTools. The problem is that CLI prints the URL when application is still not started on device and DevTools are unable to connect.

Which platform(s) does your issue occur on?

iOS

Please provide the following version numbers that your issue occurs with:

• CLI: 3.4.1
• Cross-platform modules: not applicable
• Runtime(s): not applicable
• Plugin(s): not applicable

Please tell us how to recreate the issue in as much detail as possible.

1. In any project execute: $ tns debug ios and ensure you are using iOS Simulator
2. Once you see the Chrome DevTools URL, open it in Chrome. Everything should work fine.
3. Apply a change in the application code (for example in .js file).
4. When CLI prints the new URL, immediately refresh the previously opened DevTools. They'll appear empty.

NOTE: This feature cannot be implemented before fixing the current issue.

[shamoh19]

Any update on this?

[dtopuzov]

It was fixed and released in nativescript@3.4.2.

@shamoh19 do you still experience the problem? Which is your nativescript version?

[shamoh19]

@dtopuzov Working. But live sync either taking too much time or not happening. Currently I am using latest version 4.0.0

[ndcunningham]

I have the same issue as OP
nativescript 4.1.0-218-05-17-11549
tns-core-modules 4.0.0
tns-ios 4.0.1

Empty inspector even after making an API request, network is also empty

[brobee]

Same issue here version: 5.0.3. Any solution?

[DimitarTachev]

Hi @brobee,

We've made a lot of improvements in the debug experience in 5.1.0, 5.1.1 and 5.2.0. I highly recommend you update to the latest version (5.2.0) and open a new issue if you still experience such behavior.

[sulymkaa]

@DimitarTachev same issue on 6.3.2