[CTRadioFrequencyFrontEndScanData encodeWithCoder:] crash

Is your app doing anything with Core Telephony? Or is this crash unrelated to the function of your app?

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

We use it to check the state of the network,like get carrier info etc . this crash only occur on iOS14.x

full stack link

That crash report looks kinda weird. Is it an Apple crash report?

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

apple crash report link

Thanks.

The immediate cause of this crash is a memory access exception in your code:

Code Block  
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000d47756420

Here’s a snippet from your crashing thread:

Code Block  
Thread 34 name:  Dispatch queue: CTTelephonyNetworkInfo
Thread 34 Crashed:
0   libobjc.A.dylib … objc_release + 16
1   Hao123News      … 0x102cf8000 + 65008728
2   CoreFoundation  … CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
3   CoreFoundation  … ___CFXRegistrationPost_block_invoke + 52
4   CoreFoundation  … _CFXRegistrationPost + 440
5   CoreFoundation  … _CFXNotificationPost + 704
6   Foundation      … -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
7   CoreTelephony   … -[CTTelephonyNetworkInfo updateLegacyRat:] + 88

Frames 7 and 6 show that Core Telephony is posting a notification. Frames 6 through 2 are the notification subsystem processing that notification. Frame 1 is in your code, indicating that you received the notification. Frame 0 is objc_release, suggesting that you’ve released an invalid object.

Some spelunking within -[CTTelephonyNetworkInfo updateLegacyRat:] reveals that the notification being posted is CTRadioAccessTechnologyDidChangeNotification. This strongly suggests a bug in your code, that is, the notification is being delivered to your code but the observing object, or some object it references, is corrupt (probably because it’s already been released).

Two things:

• You should symbolicate your log to uncover the identity of frame 1. That might give you a hint as to what’s going on. See Adding Identifiable Symbol Names to a Crash Report for more on how to do that.

• You should run your app with the standard memory debugging tools, and especially Zombies, to see if that makes this crash happen more reliably.

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

In addition to this I also found this collapse，It doesn't seem to have anything to do with NSNotification and Why is this method called?
Looking forward to your reply...

In addition to this I also found this collapse

I can’t do anything with crash reports snippets. If you’re going to post a crash report, please post the whole thing (the text attachment feature means that it doesn’t clog up the timeline :-).

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