I use WebStorm 10.0.4 on Windows 7.
I have a single page Angular application that I am working on in WebStorm. Up to this point I have always been able to preview my built app in Chrome using WebStorm's "Open in Browser" feature.
This morning however, the problem started. Every time I try to open up my project's index file in the browser, the page becomes unresponsive and eventually Chrome prompts me to kill the page. I cant even open developer tools.
Anyone have any idea why this may be happening?
Related
I want to know how we can debug a application ex: facebook in chrome, how we can stepover each backend actions when we login into facebook. How the flow goes in backend when we login into FB...
can we do this in chrome without setting it any breakpoints ?
can we do this in chrome without setting it any breakpoints ?
As far as I know, it cannot be done. If you want to debug your project, you have to set breakpoint. Besides, you should have the sample and should use the localhost to debug it.
First of all, you should open the prject on VS and then debug it with Chrome.
1), when you debug an asp net project, it usually have naming rules. If you open a new form page in Chrome, you can find the related page on the solution explorer, and set a breakpoint on the top of it.
2) Chrome can only debug Javascript code. If you want to debug it, you should press F12 on Chrome to open the developer mode. You can see that the JS code of the current page is under the Source menu, you can set a breakpoint directly at the beginning of the script.
Then you can click on the UI button or menu to start debugging(both js and backend activity ). Also, when you enter a new form page, just follow the above two steps to debug it.
In addition, since VS2017, you can just debug js in VS, enable option Enable Javascript debugging for Asp.Net under Tools-->Options-->Debugging-->General.
Then, you can search under the solution explorer, find the current debug form page-->find the related js file, and set a breakpoint on the top of it. After it, you can start to debug the menu of asp net project.
Note: every time you enter a new page, you should search both front end and back end pages to set a breakpoint manually.
I'm currently working on an Angular application (7.2.10) and on the latest version of iOS available on my device (12.4.1) we have hit an issue that I can't seem to figure out. The issue only occurs on Chrome on iOS, I am unable to replicate this issue on any other browser on the affected devices. The iPad air (1st gen) I am running against is using Chrome version 77.0.3865.93. It was first reported by a colleague using an iPad Pro, and we have has a couple of clients call in saying it's not working on their iPhones.
If we load the entry point to our web application (https://ams.invenias.com) the screen is completely blank. Nothing loads, and the spinner stops immediately.
I've tried a few avenues to try and get to the root of the problem, but I am yet to get anywhere. I have...
Using ios-webview-app to run iOS simulator within safari on a mac. This just resulted in the website loading as normal, so something wasn't being simulated correctly.
ios-webkit-debug-proxy to attempt to get developer tools in chrome for iOS. This ended up not working at all, either I was unable to get it running or our particular network setup meant it would never work.
Using weinre to get some sort of developer tools to read network activity/logs. I wasn't able to get this running initially, however after a bit of tinkering I was able to use this alongside Browserstack to get developer tools. Unfortunately, nothing in the logs or DOM was erroring or showed any reason as to why it might not be starting correctly.
After connecting via number 3, I was able to find out that angular itself is not bootstrapping, and no javascript is being executed on the page (from within the transpiled code, javascript included in other .js files, or within index.html executes correctly.) I'm now on day 3 with this issue, and no end in sight.
Oddly enough, if we use the 'Request Desktop Site' feature within the browser, the site loads perfectly.
Thanks,
Cameron
I am using React Native 0.13. Currently I have an Android emulator in which I can preview the application. I work in OSX Yosemite. In a lot of cases nothing happens when I click on a button or link and it is due to some error in javascript, but I do not get any error message anywhere, so it becomes very hard to solve the problem. For console logging I use:
adb logcat *:S ReactNative:V ReactNativeJS:V
Which displays the console.log outputs, but it doesn't give me the exact errors when the code breaks.
Can someone suggest me a good way of debugging and how to get the error output to work?
Best way to debug JS code is by using Chrome devtools. You can enter the mode when JS code is executed remotely in chrome tab, and then use normal chrome tools to do step through debugging. To do so you'd need to open react-native dev menu and select "debug in chrome" (see this link for more detailed instructions). Then in chrome you can open dev console with alt + ⌘ + j, go to "sources" tab and use ⌘ + p to navigate to some specific JS file. Then place breakpoints there etc...
If you want to debug java code, the easiest way is to have Android Studio launch your app. Then you can run your app with debugger attached (with ctr + d) or use "Attach debugger to Android process" button from the launch menu and selecting your running app from the menu. Then you can place breakpoints in Android Studio for the java code.
I used to be able to debug javascript from webstorm with no problem at all.
Thanks to the jetbrains chrome extension, it simply opened a new tab in chrome and launched my site in there with no problem whatsoever.
But recently I had to reboot my computer (with a beloved windows update) and now this is not working anymore.
When I start the debugging from webstorm chromes opens a new tab and I see the following in the address bar and then nothing...
data:text/html;base64,PCFET0NUWVBFIGh0bWw+PHRpdGxlPkxvYWRpbmcgaHR0cDovL3ZtLnNob3RndW4ubG9jYWwvPC90aXRsZT4=
My site is not opened and the page remains blank in chrome.
Most probably this is a result of Chrome update: some Chrome API changes introduced in v.37 break js debugger. WEB-12418 is fixed in WebStorm 9 EAP
I have seen several posts that talk about remote debugging of javascript code on Android, but they all miss the point of what I am trying to do.
I have a Nexus 7 and I want to use it as a remote development environment when I am away from my desktop. I have created a chrooted debian distribution to run apache and php and git (via ssh). This chrooted environment mounts a subdirectory of the /sdcard directory from outside the chroot environement. Apache document root of a virtual host is pointing at a directory within this. Before leaving the desktop I can git push the latest release to the tablet. When I return git pull can get what I have done back again.
I then (when away from home and NOT connected to any network) can edit the code using an Android editor (using the 920 text editor), but then run the browser to look at what I have developed using localhost the apache virtual host picks this up and displays it.
The application I am developing IS NOT FOR ANDROID - it is ultimately for the desktop. But I want to be able to debug it like I was on the desktop. Breakpoints and single stepping are the prime thing, but also I tend to use the html section in firebug to adjust my CSS before editing it.
Is there a way to get either the chrome developer tools or firebug add on for firefox to load into a browser that will run in android?
I use Firebug lite bookmarklet for iPhone and iPad, never tried on Android, check this out http://martinkool.com/post/13629963755/firebug-on-ipad-and-iphone it must be similar on Android.
To activate it use this steps:
Create a new bookmark or bookmark a page
Rename the bookmark to “Firebug”
Copy the textarea link:
javascript:(function(F,i,r,e,b,u,g,L,I,T,E){if(F.getElementById(b))return;E=F[i+'NS']&&F.documentElement.namespaceURI;E=E?Fi+'NS':Fi;Er;Er;Er;(Fe[0]||Fe[0]).appendChild(E);E=new%20Image;Er;})(document,'createElement','setAttribute','getElementsByTagName','FirebugLite','4','firebug-lite.js','releases/lite/latest/skin/xp/sprite.png','https://getfirebug.com/','#startOpened');
Edit the Firebug bookmarklet, remove the URL and paste the
bookmarklet
Choose “Done” (on the virtual keyboard) and you’re all set
Hitting that bookmarklet should give you a fully functioning Firebug at the bottom of your mobile device.
At least not for Firefox Mobile, because all the devtools are still partially based on XUL, where the Firefox Mobile is using Native UI.
I don't think there is any plan in the close future to change this situation; it's not a common scenario.
However, you should be able to do something using the Debugger API, creating an add-on for Firefox Mobile. But I don't know if it's worthy.