Fresh Issue : EventHandler::OnEvent(char const*, char const*)

[nizwar]

Happened on iPhone 13 Pro Max 15.6.1 Using your master branch with #700 fixes

  agora_rtc_engine: 
    git:
      url: https://github.com/AgoraIO/Agora-Flutter-SDK.git
      rel: master

As user log said, it happend once user minimize the app

[littleGnAl]

Is possible to share the stack trace of the 0xb59c?

[nizwar]

I'm not sure what you mean, but i paste the text here

Crashed: AgoraEvent
0  Flutter                        0x12c54 (Missing UUID b5f419596300357c85f161f5e6e0920d)
1  agora_rtc_engine               0xb59c EventHandler::OnEvent(char const*, char const*) + 324
2  AgoraRtcWrapper                0x63540 agora::iris::rtc::RtcEngineEventHandler::onApiCallExecuted(int, char const*, char const*) + 1748
3  AgoraRtcKit                    0x3d73ac agora::rtc::RtcEngineParameters::setInEarMonitoringVolume(int) + 50652
4  AgoraRtcKit                    0x3d6fac agora::rtc::RtcEngineParameters::setInEarMonitoringVolume(int) + 49628
5  AgoraRtcKit                    0x36b42c (Missing UUID 1ec6daa1d1f23e3dae9a2685ee010cd3)
6  AgoraRtcKit                    0x36b39c (Missing UUID 1ec6daa1d1f23e3dae9a2685ee010cd3)
7  AgoraCore                      0xc9d0 ahpl_perf_set_callback + 1500
8  AgoraCore                      0xdae0 ahpl_mpq_itc_ack + 340
9  AgoraCore                      0xd6b4 ahpl_mpq_loop + 84
10 AgoraCore                      0xcc78 ahpl_perf_set_callback + 2180
11 AgoraCore                      0x18358 ahpl_profile_clear_registered + 2488
12 libsystem_pthread.dylib        0x19ac _pthread_start + 148
13 libsystem_pthread.dylib        0xe68 thread_start + 8

[littleGnAl]

I think it will show the accurate line number if the dYSMs have been uploaded to the Firebase. It should be more helpful if we can know which line causes the issue.

[littleGnAl]

It's worth trying agora_rtc_engine: ^6.1.0

[github-actions[bot]]

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.