We have the loaded the app in the itunes but it got rejected because of following issues...
How to overcome the crashing reports while loading initially
This is the message from apple's site...
"Here is how we found this crash: 1) Launch application while connected to cellular or WiFi network connection. 2) Tap on the Find My Location button. 3) Application produces a crash."
can anyone help me out.
Thanks in advance...
Have you followed Apple's advice at all and tried to reproduce the crash? Do that, and check all the methods related to the Find My Location Button. Good things to look for - double releases, nil objects, infinite loops, that you're targeting the right iOS etc. Beyond stating the obvious, no one here can help you until you help us!
Related
I am currently working on code to log a user's behavior in the app and to report crashes and the sequence leading up to them. I have one big problem, I do not know how to make my app detect if it has crashed. Does anybody know how to do this in swift? Your help would be much appreciated!
I don't think there is currently a way to do this. When your app crashes it ceases to function and all processes stop. Usually any crash and diagnostic data is sent via the user settings panel.
Edit: There is an helpful post here: https://stackoverflow.com/a/8242215/4891259
Hope that helps.
My latest iPhone/iPad application works fine on the simulator.
On the iPad, it works fine for sometime but then crashes. The console shows that it is dues to a segmentation fault that I am assuming is happening due to a message being sent to a zombie. Since this is happening only on the actual device it will not be possible for me to use the NSZombieEnabled/Instruments.
What debug options do I have in the absence of instruments/zombie-detection on actual device?
Code Review - Completed, did not find anything obvious
Put comments and follow through the narrow down on zombies - In progress
What else can I do? any suggestion will be appreciated.
I did go through the past questions but did not get many options to look at....I apologize in advance if this question is already answered but would appreciate if you could share the link or provide guidance.
R.S.
Look at this post to see how to turn on Zombie objects.
https://stackoverflow.com/a/4917557/613156
You can turn it on through the diagnostics panel and it will run on your device.
I'm trying to make sure to cover all my bases with regard to ALAssetsLibrary failing for whatever reason. In looking through the possible errors that could occur when calling:
- (void)enumerateGroupsWithTypes:usingBlock:failureBlock;
i noticed that ALAssetsLibraryDataUnavailableError, but there isn't much information about what might cause this. I want to show an error screen accordingly.
Any insight would be appreciated. Thanks!
I encountered the ALAssetsLibraryDataUnavailableError in 3 cases:
When using the simulator and switching between iPhone and iPad simulator.
On the device, when the photo library was corrupt or in an inconsistent state.
After performing an iOS upgrade without having synced to iTunes.
I would recommend to display a message to the user, you run into this error, recommending:
1. To open the photos app...this usually fixes an inconsistent library.
2. If that doesn't help to reboot the Device and sync with iTunes one time.
Cheers,
Hendrik
Ok I found out another peculiar circumstance where this error appears:
Trying to save an UIImage to photo roll/photo album using UIImageWriteToSavedPhotosAlbum.
iOS asks the user for permission to access the photo library - the user denies(!)
In the completionSelector, the supplied NSError then contains ALAssetsLibrary ALAssetsLibraryDataUnavailableError.
You would think that the error would be something else like ALAssetsLibraryAccessUserDeniedError or ALAssetsLibraryAccessGloballyDeniedError. But it's not. It's just ALAssetsLibraryDataUnavailableError.
This was tested on iPhone 5, iOS 6.0.1. Maybe it's not an error, or it is and they will fix it someday.
Anyway, the "fix" is to have the user go into Settings→Privacy→Photos→have your app turned on here. The localized fix suggestion message is WRONG - it suggest to open the Photos app. No other information about the error given. Anyway, the user should probably know that he/she pushed the "Deny" button - still they might have done so by mistake and later they would have no idea what is going on.
As I get closer to releasing my first public iPhone app I'm concerned about catching crashes in the field. I'm curious to hear how others have gone about this.
I'm not sure what's possible outside of the debugger. Is all lost with an EXC_BAD_ACCESS or can I still catch it and get something useful into a log? Is the program main() the spot to put a #try/#catch?
Apple will collect all crashes for you, and if the user allows apple to gather the reports from his/her phone, you can see them inside iTunes Connect.
This is the kind of information I was looking for. I never found it with a search but saw it linked from another blog recently.
http://cocoawithlove.com/2010/05/handling-unhandled-exceptions-and.html
i am integrating twitter in my iphone music application.i.e when a user clicks a song and then he click on the twitter tab the login page of twitter should be opened and when he enters his username and password and then he clicks on the post button the song name and the comment he has entered in the textview should be posted to his twitter id.
the problem is that when i am clicking on the post button on the command it is showing as posted but then suddenly the program stops giving me an error of “EXC_BAD_ACCESS”.
Please help in solving the problem
You can use Instruments with the Zombie template to find the solution to this bug. You're probably trying to message a deallocated object.
EDIT: On the WWDC Session video's there is a video with a nice and good explanation how to find these kind of bugs. You must be a registered developer to access these videos though.
May I recommend using ShareKit for Social Media integration ?
http://getsharekit.com/ I've used this myself and it's by far the easiest solution of integrating social media interaction in your app.
Hope this helps.
I wrote a blog that gives several approaches to finding EXC_BAD_ACCESS
http://loufranco.com/blog/files/debug-iphone-crash-EXC_BAD_ACCESS.html
Here is what is happening -- Your program is running a line of code that tries to read or write to a memory location that hasn't been mapped for your application. The most likely reason for this is that you have a bug that is corrupting memory or you are sending messages to deallocated objects.
It is very likely that the line of code that is running is not the bug -- it happened sometime before this.
I strongly recommend a Build and Analyze and scan-build, because it finds these kinds of bugs a lot. It will likely flag a lot of code in your project -- you should address each problem because it's likely a real problem that will cause a leak or crash.
After that, try suggestion #4 in the blog which will instruct the simulator to never deallocate any objects -- once an object is in the state where it would be deallocated, it will warn you if anyone sends it a message. This would have caused EXC_BAD_ACCESS, but now gives a good description of what is happening.
Obviously, you need to turn this off in the real application (or have a lot of leaks).