Crash at FPRNetworkTrace.m

[ValentineVV]

Description

FPRNetworkTrace.m

Here is stacktrace:

          Crashed: org.alamofire.session.rootQueue
0  libobjc.A.dylib                0xeea0 objc_moveWeak + 196
1  CoreFoundation                 0x4da84 _CFXNotificationRegistrarAddObserver + 392
2  CoreFoundation                 0x4d880 CFXNotificationRegistrarAdd + 576
3  CoreFoundation                 0x4d060 _CFXNotificationRegisterObserver + 248
4  FirebasePerformance            0x11d78 -[FPRNetworkTrace start] + 207 (FPRNetworkTrace.m:207)
5  FirebasePerformance            0x17c20 __InstrumentDataTaskWithRequest_block_invoke + 276 (FPRNSURLSessionInstrument.m:276)
6  Alamofire                      0x2d82c DataStreamRequest.task(for:using:) + 122 (DataRequest.swift:122)
7  Alamofire                      0xbc690 Session.didCreateURLRequest(_:for:) + 1188 (Session.swift:1188)
8  Alamofire                      0xca120 partial apply for closure #3 in Session.performSetupOperations(for:convertible:shouldCreateTask:) + 72
9  Alamofire                      0x88dc4 thunk for @escaping @callee_guaranteed () -> () + 28 (<compiler-generated>:28)
10 libdispatch.dylib              0x2248 _dispatch_call_block_and_release + 32
11 libdispatch.dylib              0x3fa8 _dispatch_client_callout + 20
12 libdispatch.dylib              0xb5cc _dispatch_lane_serial_drain + 768
13 libdispatch.dylib              0xc158 _dispatch_lane_invoke + 432
14 libdispatch.dylib              0xb42c _dispatch_lane_serial_drain + 352
15 libdispatch.dylib              0xc124 _dispatch_lane_invoke + 380
16 libdispatch.dylib              0x1738c _dispatch_root_queue_drain_deferred_wlh + 288
17 libdispatch.dylib              0x16bd8 _dispatch_workloop_worker_thread + 540
18 libsystem_pthread.dylib        0x3680 _pthread_wqthread + 288
19 libsystem_pthread.dylib        0x1474 start_wqthread + 8

Reproducing the issue

No response

Firebase SDK Version

11.6.0

Xcode Version

16.1

Installation Method

CocoaPods

Firebase Product(s)

Analytics, Crashlytics, Performance, Remote Config

Targeted Platforms

iOS

Relevant Log Output

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

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

[MichaelVerdon]

Could you please provide a minimal reproducible example?

[ValentineVV]

@MichaelVerdon Unfortunately, I have no idea about the way to reproduce it. We only have crashlytics data from our users, so I added the available stacktrace and I can't help you find the reason since there is no call to any of the app's function in that stacktrace

[MichaelVerdon]

I have a few ideas on what you can try:

• Try updating dependencies that aren't at the latest.
• If you are automatically tracing AlamanoFire requests, try creating a trace with it manually and disable automatic network tracking in your app.

Is your Podfile.lock the same in this issue?

[ValentineVV]

Try updating dependencies that aren't at the latest.

@MichaelVerdon I could try to update it to the version before 11.6.0 but it makes no sense for me since at 11.6.0 was fixed the previous crash that we were waiting for a long time =)

If you are automatically tracing AlamanoFire requests

What do you mean by this? Could you explain a little bit more?

Is your Podfile.lock the same in this #14274?

Yes it is the same for all 3 issues that I created on Dec 19th

[MichaelVerdon]

AlamanoFire uses URLSession which tends to be automatically tracked by FirebasePerformance, and I wonder if the issue is related to instrumentation issues. If we disable automatic tracking by Performance it could give us some insight if it is an instrumentation issue. Let me know if you need further clarification.

[ValentineVV]

@MichaelVerdon I got it, I will disable automatic monitoring, but we don't really have any custom monitoring, would it help you anyway?

[MichaelVerdon]

Custom monitoring was more of a workaround if you still need the monitoring involved but let me know how it goes.