Thanks for reporting, @sspogra. Based on the info you shared, it seems like there are lots of missing stack traces. To have a better understanding of the issue, could you provide the complete symbolicated stack trace?

@rizafran We don't have full stack traces in firebase crashlytics.

We are also seeing the same crashes.
We can not reproduce locally, but several hundred appeared on the volumes among users. Approximately for 1% of users.

Appeared in recent versions of Firestore, this problem did not exist before.

I have poured over the code and talked with the team and we cannot figure out what could have caused this crash. And without symbolicated stack traces it's nearly impossible to guess what's going wrong. So to help with future debugging, I've improved the error message to include more information (#9305). When you start getting crash reports with this new message, please post the updates here.

@dconeybe We can get crash reports with this new message without update firebase sdk in app or need to update it?

You will need to update your app to point to a version of the Firebase SDK that contains the fix. Unfortunately, an official release that contains the fix won't be available for another month.

What you could do for now is to manually patch Firestore/core/src/core/order_by.cc with the changes in #9305. If you're using CocoaPods, then open Pods/FirebaseFirestore/Firestore/core/src/core/order_by.cc and patch in the change from #9305 (it's a straight-forward patch).

ok thanks. I will do that and provide you feedback.

@sspogra The improvement of the error message has been incorporated into version 8.12.1 of the iOS SDK, released on February 10, 2022. When you get a chance, upgrade your dependency to this new version and provide updated stack traces and error messages.

Thanks for the update @dconeybe

Closing as this was fixed in a previous release.

The issue is NOT fixed. I merely improved the error message to help diagnose the root cause.

@sspogra Once you have updated stack traces with the new version, please open a new GitHub issue for it.

@dconeybe Here is the stack traces with new firebase version 8.12.0....

Fatal Exception: NSInternalInconsistencyException
FIRESTORE INTERNAL ASSERTION FAILED: Trying to compare documents on fields that don't exist; field_path=name, lhs=users/17380, rhs=users/17380, value1.has_value()=false, value2.has_value()=false
0
CoreFoundation
__exceptionPreprocess
1
libobjc.A.dylib
objc_exception_throw
2
Foundation
-[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:]
3
FirebaseFirestore
(Missing UUID c66ef36ca3fb349ab4cd0db34c5750dd)
25
libsystem_pthread.dylib
start_wqthread
Crashed: com.google.firebase.crashlytics.ios.exception
0x0000000000000000
0
FirebaseCrashlytics
FIRCLSProcessRecordAllThreads + 184
17
libsystem_pthread.dylib
start_wqthread + 8

Fatal Exception: NSInternalInconsistencyException
FIRESTORE INTERNAL ASSERTION FAILED: QueryComparator needs to have a key ordering. (expected has_key_ordering)
0
CoreFoundation
__exceptionPreprocess
1
libobjc.A.dylib
objc_exception_throw
2
Foundation
-[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:]
3
FirebaseFirestore
(Missing UUID c66ef36ca3fb349ab4cd0db34c5750dd)
20
libsystem_pthread.dylib
start_wqthread

@sspogra Are you able to share the contents of the document users/17380 from the stack trace? If no, could you tell me if that document has its name field set to some value?

@sspogra Forget that last comment. The field is __name__ but the underscores got replaced in the markdown formatting. That's the document name, which should ALWAYS have a value.

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

Since there haven't been any recent updates here, I am going to close this issue.

@sspogra if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

@sspogra Have you had a chance to test out the fix? I'm anxious to hear if it's fixed for you or if you're still experiencing this crash.

@dconeybe I will check this only when app release to app store. Our app will be release within 10 days. After that i can provide you feedback.

Sounds good. Thanks for the update.

@sspogra Are you still experiencing this crash?

@dconeybe App still not updated on app store with new firebase version. For now you can close this issue, I will comment here when my app was live on store.

Hello @dconeybe ,

On Firebase 8.15.0 crash is still persist, but stack trace changed and here is the new one:

Crashed: com.google.firebase.firestore.rpc
0  grpc                           0xc0038 grpc_core::ParsedMetadata<grpc_metadata_batch>::KeyValueVTable(absl::lts_20211102::string_view)::'lambda'(grpc_core::Slice*, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>, grpc_core::ParsedMetadata<grpc_metadata_batch>*)::__invoke(grpc_core::Slice*, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>, grpc_core::ParsedMetadata<grpc_metadata_batch>*) + 137 (slice_refcount_base.h:137)
1  grpc                           0xc04e0 grpc_core::ParsedMetadata<grpc_metadata_batch>::WithNewValue(grpc_core::Slice, absl::lts_20211102::FunctionRef<void (absl::lts_20211102::string_view, grpc_core::Slice const&)>) const + 184 (parsed_metadata.h:184)
2  grpc                           0xb926c absl::lts_20211102::optional<grpc_core::ParsedMetadata<grpc_metadata_batch> > grpc_core::HPackParser::Parser::ParseIdxKey<grpc_core::HPackParser::String::Intern>(unsigned int) + 1145 (hpack_parser.cc:1145)
3  grpc                           0xb813c grpc_core::HPackParser::Parser::Parse() + 1004 (hpack_parser.cc:1004)
4  grpc                           0xb7f04 grpc_core::HPackParser::ParseInputInner(grpc_core::HPackParser::Input*) + 1334 (hpack_parser.cc:1334)
5  grpc                           0xb7da8 grpc_core::HPackParser::ParseInput(grpc_core::HPackParser::Input, bool) + 1308 (hpack_parser.cc:1308)
6  grpc                           0xb7adc grpc_core::HPackParser::Parse(grpc_slice const&, bool) + 1302 (hpack_parser.cc:1302)
7  grpc                           0xb84c8 grpc_chttp2_header_parser_parse(void*, grpc_chttp2_transport*, grpc_chttp2_stream*, grpc_slice const&, int) + 1381 (hpack_parser.cc:1381)
8  grpc                           0xf53a4 parse_frame_slice(grpc_chttp2_transport*, grpc_slice const&, int) + 626 (parsing.cc:626)
9  grpc                           0xf4f44 grpc_chttp2_perform_read(grpc_chttp2_transport*, grpc_slice const&) + 228 (parsing.cc:228)
10 grpc                           0x48374 read_action_locked(void*, grpc_error*) + 2415 (chttp2_transport.cc:2415)
11 grpc                           0x64e34 grpc_combiner_continue_exec_ctx() + 259 (error.h:259)
12 grpc                           0x884c4 grpc_core::ExecCtx::Flush() + 167 (exec_ctx.cc:167)
13 grpc                           0x84ee4 pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) + 1096 (ev_poll_posix.cc:1096)
14 grpc                           0x86a10 pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) + 323 (ev_posix.cc:323)
15 grpc                           0x69da0 cq_next(grpc_completion_queue*, gpr_timespec, void*) + 1047 (completion_queue.cc:1047)
16 grpcpp                         0x1a46c grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) + 147 (completion_queue_cc.cc:147)
17 FirebaseFirestore              0x2d89c firebase::firestore::remote::Datastore::PollGrpcQueue() + 141 (datastore.cc:141)
18 FirebaseFirestore              0x13422c firebase::firestore::util::Task::ExecuteAndRelease() + 491 (function.h:491)
19 libdispatch.dylib              0x3db0 _dispatch_client_callout + 20
20 libdispatch.dylib              0xb10c _dispatch_lane_serial_drain + 580
21 libdispatch.dylib              0xbc5c _dispatch_lane_invoke + 408
22 libdispatch.dylib              0x15d78 _dispatch_workloop_worker_thread + 708
23 libsystem_pthread.dylib        0x3804 _pthread_wqthread + 276
24 libsystem_pthread.dylib        0xa75c start_wqthread + 8

P.S.

Perhaps this is a completely new crash not related to the one we are talking about, but after the update, the crash we were talking about disappeared, and this one appeared. From this I concluded that the problem did not go away, just the stack trace changed.

@igorvoytovich Thanks for the updated stack trace. My guess is that my fix #9550 fixed the original crash, and now it's gotten past the point where it was previously crashing and is now crashing in a different place. Since it's not clear, I'd like to treat it as a new issue. Would you mind opening a new issue with this new stack trace? Even if it's related, it's going to require its own investigation.

Also, you mentioned in your older comment (#9258 (comment)) that you were getting "hundreds" of reports of the old crash. Do you still get any reports of the old stack trace after upgrading to 8.15.0? Or are all of your crashes this "new" stack trace since upgrading to 8.15.0?

Hi @dconeybe ,

Thanks for your response.

The old crash (Trying to compare documents on fields that don't exist.) completely disappeared. Yes, all of our crashes is now with this "new" stack trace.

I will open a new issue now.

Thank you for your help!

@igorvoytovich Thanks for the info. That gives a pretty strong indicator that the crash is fixed. I'll wait for @sspogra to reply to see if the crash resolution is confirmed.

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

Since there haven't been any recent updates here, I am going to close this issue.

@sspogra if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.