Help with crash Log _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) abort_with_payload_wrapper_internal

Can anyone assist with how to interpret this crash log? I'm sees this crashes in our firebase console, when I checked the screen parameter this error happens in different screens.we got 12 crash event in last 30 days for 4 users.Andl all these 12 crashes are on iOS16 and iphoneX. Please help me to fix this crash.Thanks.

devices
100% iPhone
Operating systems
100% iOS 16
Device states
0% background

Device
Model:iPhone X
Orientation: Portrait
RAM free: 57.56 MB
Disk free: 193.1 GB
Operating System
Version:16.0.0
Orientation: Portrait
Jailbroken:No
Crash
Date:Feb 1, 2023, 5:55:59 AM
App version:6.3.2 (6.3.2)

I'm attaching my stack trace here

For your future posts: the title should not be the cpntent of the log but explain the context. You can read this for best practices on the forum: https://developer.apple.com/forums/thread/706527. Have a good day.

What Claude31 said plus…

Do you have an Apple crash report for this? If so, please post it here. See Posting a Crash Report for advice on that.

It’s hard for me to do anything useful with a third-party crash report, not least because I don’t trust them. See Implementing Your Own Crash Reporter for an explanation as to why.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi eskimo Thank you for your replay. I am attaching my Crash report along with this ,

Consider the crashing thread backtrace:

Thread 0 name:
Thread 0 Crashed:
0   WebKit … IPC::Encoder::reserve(unsigned long) + 164 (Encoder.cpp:158)
1   WebKit … IPC::Encoder::reserve(unsigned long) + 92 (Encoder.cpp:46)
2   WebKit … IPC::ArgumentCoder::encode(IPC::Encoder&, ***::String const&) + 364 (Encoder.cpp:191)

The source line in frame 0 almost certainly corresponds to this line in the Darwin open source. That is, WebKit has failed to allocate memory and trapped. This makes it very likely that it’s related to your other issue.


Given the range of issues you’re encountering it’s possible that you have a memory corruption issue in play. I recommend that you test your app with the standard memory debugging tools, just in case they highlight anything.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Help with crash Log _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) abort_with_payload_wrapper_internal
 
 
Q