We have a strange issue with Verizon iPads. Anytime we send an email on this particular intranet site the browser crashes. It will literally close itself down and bring you back to the desktop.
Does anyone know if iPad has some debugging tools for troubleshooting this kind of an issue?
This issue does not occur on desktop browsers, ATT iPad's or any other browser that has been tested.
Usually if the app crashes the browser, it could mean stack overflow. The app may have a recursive call that caused stack overflow,
Related
I have a Cordova 4.3.0 app that I'm trying to debug with desktop Safari's web inspector. I can connect and debug fine, but if I quit the app (dismiss from multitasking view, or stop via XCode), Safari crashes. If I try to close the debugging window in Safari instead, Safari crashes. I don't have this issue when debugging the same app in the emulator, only when debugging on device.
I'm not setting any debugger breakpoints; I'm using Safari to watch the console output, and to occasionally inspect the web app.
Is this a known issue? Anything I need to do to safely close the debugging session?
You should give GapDebug a try. It's nearly the best debugger for Cordova/Phonegap apps i've ever seen.
Hope that i helped you! :-)
Problem: So I have that website which is developed with Google Web Toolkit (gwt). However, since the recent patch, the application freezes at a certain point for iPhone5 users with Safari. Other iOS-Devices like iPad seem to work fine so far.
My approach:
However, since I do not have an iPhone, I tried various online tools simulating websites on the iPhone but neither of them is having any trouble. Then I tried the Chrome's built-in device emulator which did not cause any trouble, as well.
Question: Is there any way, I can debug this case or at least reproduce it given the fact that I do not have access to an iPhone?
In case the answer is 'no': how can I debug a freezing Safari given the fact that I get access to an iPhone?
Bonus question: Why do the iPhone emulators not freeze? At least I would expect them to behave in a strange way or give me some message, that something might be wrong.
Solved the problem by using browserstack.com, which emulates an OS environment in-browser, where I could use the iPhone-Dev-Tools. Other browser-based emulators did not work as they did not emulate the OS and thus did not recreate the errors described.
Are there any strategies for troubleshooting a page that crashes iOS Safari when
Appears to be a problem rendering - the page starts to load/render then fail
Only on iPhone. iPad is just fine. Both iPhone 5s and 4s.
Web Inspector in desktop Safari closes immediately after iOS Safari closes
Nothing concrete in the crash logs for Safari
The iOS simulator seems to be fine
If so, what can I do? I can't give any concrete code for the page as I have no idea what is causing it - it would just be a link to the page.
Check out Fiddler, I use it mainly on a PC but there seems to be a Mac build as well. It may help give you a bit more insight into the traffic coming in and out of your machine. Although if the page crashes Safari the issue may be on your machine in which case Fiddler wont help much but its worth a shot to see if some of the web traffic is causing the issue.
http://fiddler.wikidot.com/mono
Can you be a bit more specific as to the page, what it does, why it may cause a crash, did you write it or is it a page out there that you are trying to access?
We have a website which crashes the iPad. On PC dekstops we've managed to lower the memory footprint by alot, and thought this would fix the iPad crash issue. It does not.
We have the iPad now connected to a Mac and are using Safari Web Inspector to debug it.
However, I do not see any option to view the ipad's memory use, or the size of the javascript objects. Is there a good site to go to to learn more about how to use this technique?
Note that it's not a dev Mac with XTools, just someone's personal MacBook.
We really want to just detemine if the error is something otehr than memory usage.
Bit of a hardware question here. I am developing iPad applications for a client and am finding that when I send over beta versions for the client to test, he is finding many more crashes on his devices than I am seeing. A lot of these crashes are 'low memory crashes' which I simply am not seeing/able to reproduce.
Am wondering what differences between the 2 devices there may be so that we can work out if it is a hardware issue. Any ideas?
Make sure of the client's configuration/environment matches your environment. Eg: Outlook Exchange Sync, MobileMe sync. In my Contacts application these caused a lot of crashes because of these.
If possible add more logs and get the logs from console of the client device and verify.
Possibly your client has more stuff running at the same time. Or your own app is background-enabled and is getting killed from time to time...
Always test your own code with the Simulator - it has a feature that allows you to simulate low memory warnings.