I've been having issues getting inspector to connect to the simulator. The issue happens all the time only when I'm connected into my work VPN from my mac.
Safari 6.0.5.
Xcode 4.6.2
ios simulator 6.0 and 6.1
Basically what I see happening is most of the time the IOS simulator will appear in the safari menu however when it tries to load the inspectable applications it crashes. When safari restarts the menu is gone. It takes a restart to get the menu back but it quickly crashes again.
It appears to be an issue with however these applications share information.
Any ideas?
I have ran into a similar issue:
Every time I tried to inspect/debug my App (ionic App) in the iOS Simulator it crashed!
My temporary solutions was to install Safari Technology preview
Now I can inspect my app and debug without any issue.
I hope it helps somebody else struggling to debug come code lol as I was...
Related
This just started happening and I cannot figure out why. This works fine in firefox, but when using using the debug toolbar in symfony 2.8, it completely locks up chrome. I have to go all the way into my task manager and end the process to get Chrome to close.
Here's a screenshot after waiting 30 minutes. This does not happen in Firefox at all. I've updated Chrome, Symfony, Composer, and every 3rd party library in the application.
I've never seen this before, I'm not even sure where to start troubleshooting this. Any suggestions?
To add, there's no errors being thrown in the server error logs at all. It doesn't appear to be an actual hang on the website, this is additionally confirmed by the toolbar still working in other browsers.
Has anyone successfully installed the push notification system Goroost (https://goroost.com/) with Meteor JS?
The Goroost files are in my public folder, and I am able to hit the essential files of /roost.html, /roost_worker.js, and /roost_manifest.json
I am hosting my site on meteor.com, which may be a factor. The link to my site is here: http://oc_connect.meteor.com/.
I can get the subscription notification and push notifications working in a Safari desktop browser, but not Safari mobile and not Chrome either desktop or mobile.
Any advice gratefully received.
I've made it work by installing Force SSL https://atmospherejs.com/meteor/force-ssl which has kick started Android notifications.
And GoRoost does not currently work with Safari mobile, just Safari desktop. So, the problem is solved.
I'm using Xcode 6.1 and iOS Simulator 8.1. It takes a long time to run the simple apps that I've written using the iOS Simulator. Build process was ok but then the iOS Simulator will show the black blank launch screen then the app screen for like 5 minutes before the app launch. Many times it shows error "Lost connection to iPhone 6(/5/4s)". Tried to re-start Xcode and iOS Simulator, and MacBook Pro multiple times already. Tried to reset "Content and Settings" in the iOS Stimulator, but doesn't help.
What could be the possible causes? Any advice/solution? Thank you.
I suggest that you boot up the device that you want to use prior to the Build&Run in Xcode. If you hit Build&Run in Xcode while the device is not booted, you will need to wait for the device to boot. This can take a long time depending on your I/O load (eg: if Spotlight is indexing at the same time you are trying to boot, or if your home directory is on a slow volume like a network mount).
Just open up iOS Simulator.app ahead of time and select the device you want to test on from the Hardware->Devices menu. Then it will be ready when you need it.
Make sure 'slow animations' is not selected under the Debug tab in the iOS Simulator. That fixed the issue for me.
Googled on this issue and some said it's a Xcode bug with the 6.1 beta, but I had the 6.1 release version installed alreadt. I even try the 6.2 beta, hoping Apple has a fix for this, but no luck, still the same.
So desperate that I decided to upgrade my 3 years old MacBook Pro RAM and harddisk to SSD. Problem solved with the upgrade! The iOS Simulator runs normally now.
Ive been trying to add a button to properly exit an Android app, built using Flex 4.6. I have used the command NativeApplication.nativeApplication.exit(); which seems to work on the emulator, and kills off the emulator.
When I run it on a device, it doesnt exit, it actually seems to go to start of the app (my login screen) which is kinda strange.
I hypothesise that something system-wide is holding the app in process or re-starting it. Anyone had any experience with this?
That code should work. I use it in my android flex app with no problem. The application quits correctly and I am dropped back at the home screen. What version of Android are you using? I was using 2.3 when I did this. If you have it running in debug mode, do you see any errors output to the console? Using the debugger will also allow you to see if it is not quitting properly or restarting on quit(you would see the splash screen again if this was the case)
I was scouring over stackoverflow and somehow unable to find the answer to my problem. My app builds and compiles just fine, but when i try to run it on the simulator, it throws a __dyld_dyld_fatal_error(). However, when i try to run it on an iOS device, everything is smooth. On a side note, I've have just updated my XCode version to XCode 4.2 to support iOS5
It turns out that I had to reset the settings on my simulator before having to run it without any glitches, and made sure of the correct version of iOS that the application has to run on.