I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Thanks for reporting, @FenWangSiCheng. Based on this related issue, it seems like the _Block_copy crash is caused by memory corruption. As mentioned there, could you try reproducing the issue locally with zombies or asan?

Hey @FenWangSiCheng. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

we app also crash on it.

we upgrade the google ad sdk, Google-Mobile-Ads-SDK (= 9.11.0)- GoogleAppMeasurement (= 9.6.0), then much crash.

the previous (Google-Mobile-Ads-SDK (8.13.0) , GoogleAppMeasurement (8.10.0)) is OK.

0 libsystem_blocks.dylib 0x000000020bcd3afc __Block_copy + 56
1 libdispatch.dylib 0x00000001c624c478 __dispatch_Block_copy + 32
2 libdispatch.dylib 0x00000001c624c478 __dispatch_Block_copy + 32
3 libdispatch.dylib 0x00000001c62658e0 _dispatch_after + 280
4 QQKSong 0x0000000103bfbcb0 -[APMPersistedConfig scheduleSynchronizeToDisk] + 168
5 libdispatch.dylib 0x00000001c624dfdc __dispatch_client_callout + 20
6 libdispatch.dylib 0x00000001c625d574 __dispatch_lane_barrier_sync_invoke_and_complete + 56
7 QQKSong 0x0000000103bfb90c -[APMPersistedConfig setString:forKey:] + 136
8 QQKSong 0x0000000103bada04 -[APMIdentity enforceConsentSettings] + 60
9 QQKSong 0x0000000103baea80 ___32-[APMIdentity updateIdentifiers]_block_invoke + 72
10 libdispatch.dylib 0x00000001c624c4b4 __dispatch_call_block_and_release + 32
11 libdispatch.dylib 0x00000001c624dfdc __dispatch_client_callout + 20
12 libdispatch.dylib 0x00000001c6255694 __dispatch_lane_serial_drain + 672
13 libdispatch.dylib 0x00000001c62561e0 __dispatch_lane_invoke + 384
14 libdispatch.dylib 0x00000001c6260e10 __dispatch_workloop_worker_thread + 652
15 libsystem_pthread.dylib 0x000000020bcd7df8 __pthread_wqthread + 288
SEGV_ACCERR
Issue ID：B8406351C0E70EB236028468F644741C

I'm facing the same crash

Our team is also facing the same issue. Based on the firebase report the crash will occur within the 1 second of application's lifetime. In our case the Firebase SDK is at version 9.4.1 we only use the Performance/Crashlytics/Analytics.

Xcode version: 14.1
Crash is occurring 99% on iOS 16 and 1% on iPadOS 16

app_issue_133f7018ececd87706d536fdd73317f8_crash_session_eac3c2da52b64144857bef2ee8b5df7b_DNE_0_v2_stacktrace.txt

Also experiencing this same crash

Hey @FenWangSiCheng. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

Please see a Crashlytics stack trace attached for further info

com.jerrycan.SydneyMetro_issue_551aba4faf049111918d804d8b9dd590_crash_session_6135e81c213e4cffa71498f73e21a5bc_DNE_0_v2_stacktrace.txt

Thanks for the bug report. The fix will be available in v10.4.0 (released around 1/20/2023).

Thanks @tsunghung, appreciate the follow up! 👍🏼

Hi everyone– this fix released today in Firebase 10.4.0!