after using my App created with PhoneGap + iOS for some time, the app crashes with following error message:
[UIWebOverflowScrollView _viewDelegate]: message sent to deallocated instance 0x21e330
I have no idea why this problem is happening. I can not reproduce the error, it happens just suddenly. I am aware that this problem is related to any kind of object that has been released, but as I am using PhoneGap (+ QrCode Plugin) I am sure that this problem is related to Phonegap or to the BarcodeScanner plugin. Could someone give me any insights on how to solve this problem? I have updated to the new PhoneGap version 1.9.0.
Related question: UIWebOverflowScrollView Exception in Phonegap Application
Do you use "-webkit-overflow-scrolling: touch" in your CSS?
We had the same problem with our phonegap-app, it sometimes crashed with the same error message (and sometimes only locked up the upper screen), and it got fixed by removing that said bit of CSS.
If you are using "-webkit-overflow-scrolling: touch", perhaps test if you can get your app to crash without it?
See apache.org for more info on the said bug and possible solutions.
We solved the situation by using iScroll instead of the CSS.
Sorry for the late answer, we just got our problem fixed :P.
Related
I've already integrated facebook login in an app with the previous sdk version. After upgrading to version 3.5, it isn't working. When I want to login, the app crashes, with several [FBSession authorizeWithPermissions:defaultAudience....] callings in the thread.
I've already done all the steps described in Upgrading documentation. Somebody with the same problem?
Thanks in advance.
The app is for iOS.
Set Sandbox Mode to disabled. This will fix this problem for now.
Facebook has fixed part of the problem on the server side. Try it again and it will probably work for you.
https://developers.facebook.com/bugs/188127071335876?browse=search_51770009e1ec62f68874486
This was a server error that was causing this for a lot of developers. However, the server fix only makes the infinite loop problem less likely to happen. It is still there. I created a new bug to track the infinite loop problem.
https://developers.facebook.com/bugs/446010282155033
I am getting the error A signed resource has been added, modified, or deleted while releasing applications in to my iPod. previously by mistake i tried releasing the same application in to iPod but it didnt run as there was errors in my application. After rectifying the errors when i tried releasing the app its showing the above mentioned error..
Pleasing can anyone help me..
Try to do a clean build (Cmd-Shift-K to clean all targets). If that does not work, look into a previous question on this topic.
Debugger is telling me this, when I run my app on device:
Program received signal: “EXC_BAD_ACCESS”.
mi_cmd_stack_list_frames: Not enough frames in stack.
mi_cmd_stack_list_frames: Not enough frames in stack.
I don't get information about where in code that happens. That's all I get. Any idea what that could mean?
The app crashes after that. When the device is not connected to the mac, it still crashes, so not a debugger problem.
Building on the 4.0 sdk onto a 3.1.3 phone caused this for me.
Fixed by weak linking UIKit in the target.
EXC_BAD_ACCESS happens when a message is sent to an object that has already been released.
I've seen "mi_cmd_stack_list_frames: Not enough frames in stack" before when trying to release something that's already been released as well.
My suggestion is to set the NSZombieEnabled environment variable and see which released object you are trying to access.
This site has a great tutorial on it:
http://www.codza.com/how-to-debug-exc_bad_access-on-iphone
I've seen this caused by at least three different kinds of problems:
• As described in the other answer, overrelease errors can do it.
• I had it happen when I was upgrading an app to use iAd and IOS 4.0. I think the problem was that I tried to use the iAd framework in the 3.0 version of the app as well, which of course isn't possible because iAd is only around in 4.0 and above.
• I had it happen when I removed a bunch of stuff from an app and recompiled, but vestiges of the old stuff were still around on the simulator. Resetting the simulator cleared the problem. What I was removing was the Flurry API. I'm afraid I don't know what, specifically, in there stuck around and caused the problem.
I have the same issue. My solution is:Quit the Xcode and then restart it after waiting some time.
I've got such a message when was trying to launch an app on iPhone under iOS 3.1.2 with a string like that
Class messageClass = (NSClassFromString(#"MFMessageComposeViewController"));
At the same time that works well when I use a device with iOS 4.
So I can assume that app could crash when start running on device if there are any references to iOS4-only classes.
Creating a new project and copying all the existing files in it solved this problem for me.
When I tried to upload a build on device it give the following error.
Your mobile device has encountered an unexpected error (0xE8000001)
I am unable to solve this problem. Can anyone tell me why this is happening?
Anytime i get an unexpected error i hard reboot my device by holding down the home and lock buttons until the apple logo appears. No idea what causes it, but the reboot usually fixes it.
This seems to be a bug that is puzzling many users. No idea what the error actually is, but on this forum people claim:
this error will require you to restore your iPhone/touch, either through Xcode's Organizer window or iTunes. No way around it".
This basically happens when there's a communications error between Xcode and the iPhone which leaves Xcode confused about the state the iPhone is in. (You can actually make it happen sometimes by unplugging the phone in the middle of installing a build.) As the error message's text suggests, turning the iPhone off and back on will usually clear the error. You may sometimes have to restart Xcode or even your whole Mac, but not often.
To all
The problem get solved. When I set provisioned profile of device. It works.
Thanks for your help & guideline.
The iPhone app I am developing has a strange quirk where it runs ok when xcode has launched it, but not when launched directly on the device.
I've checked the crash logs and the exception seems to be occurring in libxml2.2 in xmlParseCharData. It's quite a big xml document that is being parsed so I think that might be the problem.
I tried with a smaller xml document and this was fine. So either it is the size of the document or something in the document that is causing it but the same large document is parsed ok when launched via xcode.
Any ideas why this would be happening or how I might start trying to debug it?
I found the problem. The app was taking too long to start. I eventually noticed in the console log in organizer that this was the problem. I changed the app so it has a proper landing screen and it works fine now.
I found a Apple Technical Q&A about this issue.
http://developer.apple.com/iphone/library/qa/qa2009/qa1592.html