Even on Entry modules, after starting the Debugger, new browser instance open, but screen still blank for some minutes then raises this error: Load timeout for modules: (Modules name)My Colleagues can debug the same modules without problems. I guess is something locally, just don't know what.
What I already tried:
Any suggestion?
@Wallace Haese :
When you start a debug session in Google Chrome, it typically begins listening on a local port (usually 9222) for remote debugging.
In my case, I can confirm this by running the following command on macOS:
It shows Chrome listening on port 9222.
If you don’t see something similar, it's possible that some software (firewall, antivirus, or security settings) is blocking the communication.
Try running Service Studio as Administrator, or temporarily disabling firewall/antivirus software, and then attempt debugging again to see if that resolves the issue.
I ran S. Studio as admin and Seems to be workingAlso, I cleaned the temp folder.Thanks for your help!
Hi @Wallace Haese ,
Have you refreshed all the dependencies?
May be runs a full solution and try again.
Check other modules of your app? or this is only happening for particular module?
Regards,
Manish Jawla
Hi @Manish Jawla Good point. Actually my colleagues can debug on same modules, that show error for me.And it happens with different entry modules. I'm not sure, but I guess is something locally, just don't know what.
Can you try to check your colleagues service studio version? Are you both using the same?
And can you try to clean the temp files of your system %temp% from this folder.
And try to check the chrome browser version as well with your colleague.
Let’s try these suggestions :-).
Hope this helps,
Regards
The S. Studio are in the same version and Chrome is updated. I did your test. I cleaned the temp folder, but also executed S. Studio as admin and Seems to be workingThnaks!