How can I see safari extension loader logs - safari

is there a way that I can see complete verbose to what is happening and what does safari in the steps of loading an extension?
I have a problem with how safari loads extensions and I want to see every step of that. Does anyone know if this logs exist and can be viewed?
Thanks!

This logs can be found inside the Console.app from macOS.

Related

First run after install from Google Play

I prepare apk and upload to Google Play.
When I first run it on phone I receive message: Open in Chrome and button - OK. Can I hide this message on first run? I cannot find solution for that.
It's possible to remove the Running in Chrome message. Improvements on how the information is displayed to users is being discussed in this bug: crbug.com/981323

IE11 - failed to open http://localhost:8080

I am trying to access my VueJS application running on my node server on IE11 by accessing the URL http://localhost:8080. However I cant access the same as only a blank screen appears. I have babel polyfill installed and imported in my main file and have babel presets already setup in babelrc file.
My app is currently running and is accessible on Chrome but not on IE11.
I don't get a single error message in console and have no clue what could be going wrong. Has anyone ever faced this?
You need to use polyfills. IE11 does not support ES2015, it needs to be transiled by babel. There seem to be various ways of doing this.
Please check this guide: jacklyons.me/how-to-fix-vuejs-not-working-in-ie11
or here: cli.vuejs.org/guide/browser-compatibility.html

React Native Remote Debugger shows cached bundles in Chrome

When I'm trying to use Remote JS Debugging in Google Chrome shows Cached Bundles. See the image below.
Remote Debugger UI Screenshot:
On my emulator its not connecting to remote debugger.
Android Emulator Screenshot
Is there anyone who encountered this problem?
I'm using React Native Version 0.47.
Thanks in advance.
If you use Chrome, clear cache from browser and reload app from react native. This fix my issue :)
Get rid of that final forward slash and it should kick you to the normal debug window. I'm running 64.0.3282.186 version of Chrome and this works for me. However, I know someone who says they get force redirected to the address with the forward slash, so I hope you're not in that boat.
To fix the error, you need to clear your cache in chrome and it will work again.
Close the packager and install the app again. This worked for me.

ReferenceError: safari is not defined

Whenever I click on a textarea the following message pops up:
What could possibly trigger this?
Thanks!
Note: I'm using JQM 1.4.5 and the textarea is normal, nothing was configured.
I was having the same issue on one of my projects, with the same traceback as yours. It was strange, as there was no bundle.js in my project, or even being loaded. I found it was an issue with one of my extensions, so disabling extensions and clearing cache should fix your issue.
Are you using chrome browser?
If so, sign out of your chrome browser. That should fix it.
It might be that you have some installed chrome extensions whose javascript codes are conflicting with your project

How to disable phonegap autoreload (At least during dev)

Here is my issue:
I've installed phonegap and phonegap desktop.
http://code.riffzone.net/phonegap-install-msw/
Now, when I'm working on my application (Jquery Mobile), I'm testing it on a browser, but the application is reloading again and again after every 2 seconds and I can't even write something in the form input, reloading to fast..
I don't understand where this is coming from?
Here is the screen shot of my browser and the firebug console where you can see the page reloading over and over (1) and the api_auto_reload in the console (2).
Thanks a lot :)
The reload should be triggered only when some of your source files is changed. For some reason it does detect change on your files constantly. That reason is quite hard to find out without debugging more. You can, though, turn the auto reload off with --no-autoreload switch for phonegap serve like this
phonegap serve --no-autoreload
It was phonegap desktop beta (the minimalist server) and not phonegap (command line) which was causing this bug.
If you have the same issue, make sure you are not using it.