Let me preface this with the following:
I am not a developer! Most of this stuff is arcane knowledge to me!
That said, I did a CTRL+F
for "crash" in those logs you provided, and aside from a lot of instances of the word "crashalytics", every time the logs switched to a crash, it starts with the following:
--------- switch to crash
1706962417.634 4894 4894 E AndroidRuntime: FATAL EXCEPTION: main
1706962417.634 4894 4894 E AndroidRuntime: Process: com.careem.acma, PID: 4894
1706962417.634 4894 4894 E AndroidRuntime: androidx.compose.runtime.h: Compose Runtime internal error. Unexpected or incorrect use of the Compose internal runtime API (Start/end imbalance). Please report to Google or use https://goo.gle/compose-feedback
To me, this does not look like a GrapheneOS issue. This app is using Jetpack Compose which is a new way to develop Android apps which will likely be the future, but is currently not very mature.
It sounds like something is triggering a crash that has to do with Compose and I can't currently see how the crash would be GrapheneOS-specific.
That said, I'll see if I can get someone on the development team to also take a look, because I understand that this doesn't really help you solve your issue, but it might end up being a crash of this being an app bug not specific to the OS, which will have to be reported to Careem's team.