My app is running fine with all the devices but only crashes with iphone Xr and the crash report looks like the:
Any help would be appreciated
file link https://drive.google.com/open?id=19lkVCSN9LuShROGXAErE_mNn6E-tO6up
The code on your main thread generated this EXC_BREAKPOINT (SIGTRAP) exception. You should symbolicate this log so you can see precisely where it crashed. Until you do that, you’re just guessing what the source of the problem is. A symbolicated log will tend to narrow down the problem to a particular line of code, from which you can start your diagnosis.
Re EXC_BREAKPOINT, Technical Note TN2151 says:
Swift code will terminate with this exception type if an unexpected condition is encountered at runtime such as:
a non-optional type with a nil value
a failed forced type conversion
Look at the Backtraces to determine where the unexpected condition was encountered. Additional information may have also been logged to the device's console. You should modify the code at the crashing location to gracefully handle the runtime failure. For example, use Optional Binding instead of force unwrapping an optional.
For what it’s worth, there’s a very good chance that the problem is not related to the fact that the device was an iPhone X𝖱, but something else related to that user’s device, settings, permissions, or environment.
Related
I got a crash in my test flight version of an iOS application, but when I check the Xcode crash log system, I am getting the crashed line and crashed function name. But I was not able to find the reason of crash. Does anybody know how to find out the reason of the crash occurred?
Here is the screenshot of the crash log of Xcode -> Organiser.
From this I am not getting the crash reason.
There is a way to show the report in Finder, as per https://help.apple.com/xcode/mac/11.4/index.html?localePath=en.lproj#/devc8ced2ea3 by Control+Clicking in the list of crash reports on the left.
Please update your question with the .crash file, which should provide full information about the crash.
The function that actually crashed is objc_msgSend. The most likely cause is that you sent a message to an object that had a different type than you and the compiler expected.
this is a simple game running on iphone device, it will crash in some cases.but xcode only display this message:
error: memory read failed for 0xd00000000
there is no stack in the left panel.
i found the value in register pc 0xd00000000, it looks like the base address of this process.
i have add a exception breakpoint in xcode it will not active before crash.
this is the memory usage image, i have test it on iphone x:
so i want to know, how to find the directy reason of this crash? is there any method to break the process when the register change to a special value, in this case, when the pc register change to 0xd00000000, make xcode break.
stackoverflow exception cause this crash, it make my stack memory crashed,so xcode can't get the valid stacktrace of this tread.
I am having trouble trying to understand what went wrong when my app crashed for a user based on a crash report i received back.
In Xcode organizer I can see the following:
I can open the crash report in project but all I get is:
This part doesn't change if I select any individual thread, I can't see any variables and it doesn't even tell me what line of code the thread was suspended at. Does anyone have any suggestions of how I should continue to debug this? Thanks in advance.
First of all this crash report is not symbolicated. You should do that. Xcode would do that for you if you download the crash report by Organizer.
Second, this exception usually occurs if you the index specified in objectAtIndex is too large. So if you don't have access to symbolication for this crash report then all you could do is to check all your objectAtIndex: calls to see if the index could get outside of the bounds.
I have an app which is written in swift and uses AFNetwork and some other helpers written in Obj c. On my clients device (iPhone 6+) he is getting an SIGTRAP error, I have tried to recreate the issue on the testing devices that we have and on all the simulators but could not recreate it.
Below is the stack trace, it crashed twice:
http://paste.ubuntu.com/12077304/
When I symbolicate the crash report it is pointing to:
-[Instagram getOwnBaseUrl] (in DiaryApp) (Instagram.m:118)
And on the second instance it point to:
[UIAlertView(AFNetworking) showAlertViewForTaskWithErrorOnCompletion:delegate:cancelButtonTitle:otherButtonTitles:]_block_invoke (in DiaryApp) (UIAlertView+AFNetworking.m:72)
Crash Log : http://paste.ubuntu.com/12077328/
I am not able to pin point the exact cause for the crash. Any help in this regard will be highly appreciated.
Thanks.
SIGTRAP is not the error it is the exception. It doesn't show the origin of the crash. This exceptions throw into Main thread on Main/Next Runloop, so the stacktrace of the main thread does not show the origin of it.
It happen like NSArray indexOutOfBounds or library or anything else
reference link
signal Types
I am unable to post images as I don't yet have 10 rep so my apologies if any of this is vague.
I'm writing an ARC application for Mac OS X and it throws an EXC_BAD_ACCESS error. In an attempt to track down the issue, I have enabled Zombie Objects under the 'Diagnostics' Tab.
I then startup Instruments (Zombies)
Finally I record and cause the app to crash and the error is generated. However, instead of getting any zombie indicators in instruments, I get an app problem report for my app that I'm profiling saying that my app 'quit unexpectedly'. No stack trace is produced for me to navigate and that problem report isn't of much use to me.
Could the EXC_BAD_ACCESS error be caused by something other than dereferencing a pointer to memory that has been released? Should I always expect to get Zombies in this case when there is an EXC_BAD_ACCESS error? If so then how can I see the zombie? What else do I need to configure to get the zombies?
Thanks
Could the EXC_BAD_ACCESS error be caused by something other than dereferencing a pointer to memory that has been released?
Yes. That error simply means that your program tried to dereference a pointer that refers to a location that your program isn't allowed to access. That could be because it points to an object that no longer exists, but it can also happen when you use a pointer without setting it to something valid in the first place, or when you incorrectly try to use a non-pointer value as a pointer.
Should I always expect to get Zombies in this case when there is an EXC_BAD_ACCESS error?
No, NSZombieEnabled only helps you find cases where you're trying to access a deallocated object. It won't help you with other cases that produce EXC_BAD_ACCESS.
You could try adding an exception breakpoint in Xcode.
Click the "Breakpoint navigator" tab in Xcode
Click the plus sign
Click "Add Exception Breakpoint"