-
Notifications
You must be signed in to change notification settings - Fork 388
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
App getting crash on Accepting Incoming Call (Android Background) #873
Comments
Can you share the full crash log? |
it's only happening in release mode so could not get many logs neither its getting recorded in Firebase Crashlytics. |
@murtazaagaz How do you get the log? |
I dont know its being logged in VS Code's console at the time of crash |
I think you can get it from Android Studio logcat. |
Here is the full Error Log from Android Studio
|
Thanks for your detailed logs. BTW, may I ask what "Incoming call" mean, does it mean that there is a phone call or just a remote user join the channel? |
The root cause is here:
I think you should check what happens with this plugin. |
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. If you find this problem please file a new issue with the same description, what happens, logs and the output. All system setups can be slightly different so it's always better to open new issues and reference the related ones. Thanks for your contribution. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please raise a new issue. |
Bug
Android App Getting Crashed after accepting Incoming call on background mode
To Reproduce
Expected behaviour
The call should run smoothly
Tested on:
Redmi Note 5.
Error Log
F/agora.io(31093): === crash(signal 6) === F/agora.io(31093): [crash_info]: crash in agora module: 0
Flutter Version: 3.3.10
Agora RTC SDK version:
agora_rtc_engine: ^6.1.0
The text was updated successfully, but these errors were encountered: