Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Crash] Il2CppExceptionWrapper crash on iOS #1195

Open
OguzFARSAK opened this issue Feb 25, 2025 · 11 comments
Open

[Crash] Il2CppExceptionWrapper crash on iOS #1195

OguzFARSAK opened this issue Feb 25, 2025 · 11 comments
Labels
api: core api: firestore needs-info Need information for the developer

Comments

@OguzFARSAK
Copy link

Description

Fatal Exception: Il2CppExceptionWrapper on iOS app

We also tried with Firebase sdk v12.4.0

stacktrace.txt

Reproducing the issue

We can not reproduce

Firebase Unity SDK Version

12.6.0 and 12.4.0

Unity editor version

2022.3.55

Installation Method

.unitypackage

Problematic Firebase Component(s)

No response

Other Firebase Component(s) in use

Analytics, Crashlytics, Firestore, Messaging, Remote Config

Additional SDKs you are using

Applovin Max : 8.0.1

  • GoogleAdsManager ios 11.13.0.1
  • GoogleAdmob ios 11.13.01

GoogleMobile Ads: 9.5.0
Facebook: 17.0.0
Adjust: v5
GameAnalytics: 7.10.3

Targeted Platform(s)

Apple Platforms

Unity editor platform

Mac

Scripting Runtime

IL2CPP

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

Relevant Log Output

Crashed: com.google.firebase.crashlytics.ios.exception

Fatal Exception: Il2CppExceptionWrapper

Crashed: com.google.firebase.crashlytics.ios.exception
0  UnityFramework                 0x2eb18fc FIRCLSProcessRecordAllThreads + 392 (FIRCLSProcess.c:392)
1  UnityFramework                 0x2eb1cdc FIRCLSProcessRecordAllThreads + 423 (FIRCLSProcess.c:423)
2  UnityFramework                 0x2ea96b4 FIRCLSHandler + 34 (FIRCLSHandler.m:34)
3  UnityFramework                 0x2ea4438 __FIRCLSExceptionRecord_block_invoke + 240 (FIRCLSException.mm:240)
4  libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
5  libdispatch.dylib              0x132c4 _dispatch_lane_barrier_sync_invoke_and_complete + 56
6  UnityFramework                 0x2ea33b4 FIRCLSExceptionRecord + 242 (FIRCLSException.mm:242)
7  UnityFramework                 0x2ea3128 FIRCLSTerminateHandler() + 423 (FIRCLSException.mm:423)
8  libc++abi.dylib                0x14068 std::__terminate(void (*)()) + 16
9  libc++abi.dylib                0x1400c std::terminate() + 108
10 libobjc.A.dylib                0x3f81c objc::DenseMapBase<objc::DenseMap<objc_class*, PendingInitialize*, objc::DenseMapValueInfo<PendingInitialize*>, objc::DenseMapInfo<objc_class*>, objc::detail::DenseMapPair<objc_class*, PendingInitialize*>>, objc_class*, PendingInitialize*, objc::DenseMapValueInfo<PendingInitialize*>, objc::DenseMapInfo<objc_class*>, objc::detail::DenseMapPair<objc_class*, PendingInitialize*>>::FatalCorruptHashTables(objc::detail::DenseMapPair<objc_class*, PendingInitialize*> const*, unsigned int) const + 14
11 libdispatch.dylib              0x3de8 _dispatch_client_callout + 40
12 libdispatch.dylib              0xb400 _dispatch_lane_serial_drain + 748
13 libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 380
14 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh + 288
15 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread + 404
16 libsystem_pthread.dylib        0x4934 _pthread_wqthread + 288
17 libsystem_pthread.dylib        0x10cc start_wqthread + 8

If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet
👀 Replace this line with the contents of your Podfile.lock!
@google-oss-bot
Copy link

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

@argzdev
Copy link

argzdev commented Mar 5, 2025

Hey @OguzFARSAK, thanks for reaching out. According to the stacktrace, I'm guessing that the issue might be coming from Firestore.

com.google.firebase.firestore.rpc
0  libsystem_kernel.dylib         0x15f40 poll + 8
1  UnityFramework                 0x453ed7c pollset_work(grpc_pollset*, grpc_pollset_worker**, grpc_core::Timestamp) + 1029 (ev_poll_posix.cc:1029)
2  UnityFramework                 0x4541564 pollset_work(grpc_pollset*, grpc_pollset_worker**, grpc_core::Timestamp) + 363 (cxx_atomic_impl.h:363)
3  UnityFramework                 0x45106d0 cq_next(grpc_completion_queue*, gpr_timespec, void*) + 1039 (completion_queue.cc:1039)
4  UnityFramework                 0x4774c6c grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) + 147 (completion_queue_cc.cc:147)
5  UnityFramework                 0x2efd16c firebase::firestore::remote::Datastore::PollGrpcQueue() + 143 (datastore.cc:143)
6  UnityFramework                 0x302415c firebase::firestore::util::Task::ExecuteAndRelease() + 188 (task.cc:188)
7  libdispatch.dylib              0x3fa8 _dispatch_client_callout + 20
8  libdispatch.dylib              0xb5cc _dispatch_lane_serial_drain + 768
9  libdispatch.dylib              0xc124 _dispatch_lane_invoke + 380
10 libdispatch.dylib              0x1738c _dispatch_root_queue_drain_deferred_wlh + 288
11 libdispatch.dylib              0x16bd8 _dispatch_workloop_worker_thread + 540
12 libsystem_pthread.dylib        0x3680 _pthread_wqthread + 288
13 libsystem_pthread.dylib        0x1474 start_wqthread + 8

Could you share any code snippets that you're executing with relation to Firestore? It'll help speed up our investigation. Thanks!

@argzdev argzdev added needs-info Need information for the developer and removed type: bug labels Mar 5, 2025
@google-oss-bot google-oss-bot added the stale Don't have recent activity label Mar 12, 2025
@google-oss-bot
Copy link

Hey @OguzFARSAK. 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!

@coffee-lady
Copy link

Hello. We are facing the same issue. We don’t have Firestore, only analytics, crashlytics, remote config.

@google-oss-bot google-oss-bot removed the stale Don't have recent activity label Mar 13, 2025
@coffee-lady
Copy link

Here is stacktrace. stacktrace.txt

Libraries:
"com.google.firebase.analytics": "12.4.1",
"com.google.firebase.app": "12.4.1",
"com.google.firebase.crashlytics": "12.4.1",
"com.google.firebase.remote-config": "12.4.1"

Unity version: 2022.3.45

@coffee-lady
Copy link

Also, we had this issue with Firebase 12.3.0. There was a situation when we manually logged an exception in the game, and Crashlytics crashed at the same time as the exception was logged. Then we removed manual exception logging and updated Firebase to 12.4.1, but this crash hasn't gone away, and this crash is massively affecting our users. Please let me know if there is any possible fix.

@argzdev
Copy link

argzdev commented Mar 13, 2025

Hey @coffee-lady, thanks for the extra details. I took a look in the stacktrace, but it doesn't show any details that the crash is coming from Firebase products. I noticed that there were multiple threads indicating Job.Worker and AssetGarbageCollectorHelper, you could be encountering a deadlock situation of resources. That said, it is difficult to say that your issue is related to this one. Is there any reason why you think Firebase is causing this issue?

@coffee-lady
Copy link

Yes, the reason is the previous situation with manual exception logging (Debug.LogException) and related crash. For example there was 62 manually logged non-fatal exceptions and 62 crashes with this stacktrace.

@argzdev
Copy link

argzdev commented Mar 13, 2025

That is interesting, could you share some code snippets with the usage of Firebase so we can take a look at what went wrong? If there's any chance you could share an MCVE, that'll help us investigate this faster. Thanks!

@coffee-lady
Copy link

coffee-lady commented Mar 15, 2025

Hello. I've investigated this issue and I found that this crash happened in unusual circumstances. There was null reference exception in our code that was thrown in another thread, not main. Crashlytics couldn't receive correct stacktrace and I was able to get right stacktrace only thanks to another service of crash reporting. Please improve collecting stacktraces in such circumstances like in another services if this is possible.

@argzdev
Copy link

argzdev commented Mar 17, 2025

Great to hear you were able to get the stacktrace, @coffee-lady. While we really want to help improve our product for better customer experience, without any specific details of what went wrong such as MCVEs, code snippets, or steps to reproduce the behavior, it would be very difficult to determine what went wrong. Nonetheless, thank you for sharing these details!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: core api: firestore needs-info Need information for the developer
Projects
None yet
Development

No branches or pull requests

4 participants