This is probably because the files being transferred to Safari inspector is from the system itself.
#1BLOCKER OSX SIMULATOR#
This option is suitable when your system is not running too many applications as firing a simulator suckup a good amount of system resources.īasically, instead of running your app on a real device, run your app in an iPhone simulator via Xcode and debug it normally in your Safari web inspector and this problem will not occur.
I think this is the most working solution. You can basically prepare your iOS app by ionic cordova prepare ios and then run the app using Xcode and deploy it to your iPhone.Īt least, I'm able to see the console logs and sometimes, it even works with Safari web inspector. This is also a kind of workaround and a hack to see it functional. Then opening the Developer's console on Safari worked fine for me without disconnecting. (This is somehow kept my iOS device connected to my Mac)
#1BLOCKER OSX MAC#
Since this is an issue related to connection between iOS & Mac so I opened my Console app and just kept my iPhone selected. This solution is working for a long time now. On iOS Device -> Settings -> Developer -> Clear Trusted Computers then reconnect the USB cable and then try to debug again Option 3 - Make the debugger fool (as of 14th Jan 2019) Safari on MacOS -> Develop -> Empty Cache Option 2 - Clear Trusted Computers Other few options that worked for me: Option 1 - Empty Cache From Safari Most of the answers listed here worked for me for a while but after a few hours they also stopped working and my Safari web console again keeps disconnecting as it opens. I wrote a small article about this to elaborate this in detail Original Answer Ionic cordova run ios -lc -source-map=false For that, all I had to do is to pass -source-map=false to my ionic cordova commands like: ionic cordova run ios -source-map=false So, when I started to run my iOS application without source maps, the problem is gone. In my case, it used to because of the JavaScript & their source map files. And then suddenly, I tried another thing and it worked.īasically, the Safari web inspector disconnects when the size of any files are too large (not sure about the limit). My subconscious mind started to think about this problem when I saw that this issue (of Safari getting disconnected) is not there when I run a plain simple Cordova or Ionic application. Well, after so many trials and opening thousands of blog posts to figure out a solution, I managed to get it working without a single case of failure.įor me, this has been always a problem with my Ionic+Cordova application. Choose trust and now you can choose the open tab on your devices safari and debug. Now on your phone there is a permission question. If you had connected your iPhone device with an usb cable, disconnect it first.ĭevelop > Device name > Apply for development Settings > General > Reset > Reset Location & Privacy
#1BLOCKER OSX DOWNLOAD#
Maybe you need to download the Safari Technology Preview MacOS Sierra and OS X El Capitan (I assume macOS high Sierra is also supported)
#1BLOCKER OSX UPDATE#
After the safari update the web inspector opens and closes immediately. Since for the development build it is not:īefore my web inspector very rarely worked and often just stopped working - but was still open. I could confirm this on a real device with a production build (1.8 MB + 2.4 MB files), the Safari Web Inspector stays always connected. After toggling it on, it worked.įor other devices / versions, please read further down (Maybe you can decrease your build size).ĮDIT: found out, the Web Inspector keeps disconnecting for too large JS files and map files It was suddenly toggled off and I couldn't connect via the Web Inspector. Settings -> Safari -> Advanced -> Check that Webinformation is toggled on. With this configuration it seems to work right now. Settings > General > Reset > Reset Location & Privacy 3. Reset your location and privacy settings on your device.
Sidenote: Maybe you need to download the Safari Technology Preview 2. Open the iPhone simulator in Xcode and debug there with Safari Web Inspector.
0 kommentar(er)
