I submitted my app today but I have gotten the crashlog. I tried to analyze the code but I used the flutter to make app. someone knows what is the issue? I am also using the firebase.
Thanks
I submitted my app today but I have gotten the crashlog. I tried to analyze the code but I used the flutter to make app. someone knows what is the issue? I am also using the firebase.
Thanks
Consider this:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Your app crashed trying to access unmapped memory. Look at the crashing thread’s backtrace:
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 nanopb … pb_enc_bool + 0
1 nanopb … encode_field + 436
2 nanopb … pb_encode + 172
3 FirebaseSessions … FIRSESEncodeProto + 64
4 FirebaseSessions … SessionStartEvent.transportBytes() + 232
5 FirebaseSessions … @objc SessionStartEvent.transportBytes() + 28
6 GoogleDataTransport … -[GDTCOREvent setDataObject:] + 68
7 GoogleDataTransport … -[GDTCOREvent copy] + 72
8 GoogleDataTransport … -[GDTCORTransport sendEvent:onComplete:] + 44
9 FirebaseSessions … protocol witness for GoogleDataTransportProtocol.logGDTEvent(event:completion:) in conformance GDTCORTransport + 176
10 FirebaseSessions … EventGDTLogger.logEvent(event:completion:) + 224
11 FirebaseSessions … protocol witness for EventGDTLoggerProtocol.logEvent(event:completion:) in conformance EventGDTLogger + 20
12 FirebaseSessions … closure #1 in SessionCoordinator.attemptLoggingSessionStart(event:callback:) + 176
13 FirebaseSessions … closure #1 in SessionCoordinator.fillInFIID(event:callback:) + 180
14 FirebaseSessions … partial apply for closure #1 in FIRInstallations.installationID(completion:) + 48
15 FirebaseSessions … thunk for @escaping @callee_guaranteed (@guaranteed String?, @guaranteed Error?) -> () + 96
16 FirebaseInstallations … __49-[FIRInstallations installationIDWithCompletion:]_block_invoke + 56
17 FBLPromises … __56-[FBLPromise chainOnQueue:chainedFulfill:chainedReject:]_block_invoke.18 + 52
18 libdispatch.dylib … _dispatch_call_block_and_release + 32
This is the main thread. Frame 18 shows that this code is running because someone scheduled a block on the main queue. All the rest of the code is in your third-party runtime. That’s not something I maintain expertise in. I recommend that you escalate this via the support channel for that runtime.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"