Skip to content
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

W/agora.io(24391): [STRATEGY RUNNER] strategy chain not found! timer_type type:1 #1225

Closed
jerrypaulsam opened this issue Jul 21, 2023 · 11 comments
Labels
waiting for customer response waiting for customer response, or closed by no-reponse bot

Comments

@jerrypaulsam
Copy link

After an audio call, I am getting this response in console. This runs for an infinite amount of time, until I reinstall the app (debug). and no further incoming calls are possible. The device just vibrates for a moment and this response keeps getting printed on the console.

D/CCodecBufferChannel(24391): [c2.android.aac.decoder#966] DEBUG: elapsed: mInputMetEos 6, hasPendingOutputsInClient 0, n=1 [in=0 pipeline=0 out=2]
D/PipelineWatcher(24391): [0xb400007d2b532680] elapsed: mFramesInPipeline 2, n 6
D/CCodecBufferChannel(24391): [c2.android.aac.decoder#197] DEBUG: elapsed: mInputMetEos 6, hasPendingOutputsInClient 0, n=1 [in=0 pipeline=0 out=2]
D/PipelineWatcher(24391): [0xb400007c3d7ed680] elapsed: mFramesInPipeline 2, n 6
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []
W/agora.io(24391): [STRATEGY RUNNER] strategy chain not found! timer_type type:1
D/JSON (24391): []
D/JSON (24391): []
D/JSON (24391): []

@laxkarparas1
Copy link

same issue ,but in my case when i end a video call this issue is coming
any solution

@jerrypaulsam
Copy link
Author

after I call _engine.release(), it seems to have disappeared.

@littleGnAl
Copy link
Collaborator

Call RtcEngine.release is necessary to avoid unknown issues. If calling RtcEngine.release does not work for you, I think it's better to raise a new ticket to the agora support.

@littleGnAl littleGnAl added the waiting for customer response waiting for customer response, or closed by no-reponse bot label Jul 24, 2023
@melshenawyarabapps
Copy link

In RtcEngineEventHandler
you can put this code
onError: (ErrorCodeType err, String msg) {
debugPrint(
'Error rtc engin =============================> Code = ${err.name} MSG = $msg');
},
then you will know the reason
I think this message because rtc token is not true

@laxkarparas1
Copy link

laxkarparas1 commented Jul 26, 2023

there is not any error, I tried the above-given code snippet. but still can't get the reason
it is giving this error
[STRATEGY RUNNER] strategy chain not found! timer_type type:1
and one more thing when I leave the connected channel it is still showing this error continuously , looks like agora engine running after leave channel.

below is the code which i'm using

for initialise agora engine

` // retrieve permissions
await [Permission.microphone, Permission.camera].request();

//create the engine
_engine = createAgoraRtcEngine();

try{
await _engine.initialize(const RtcEngineContext(
appId: agoraAppId,
channelProfile: ChannelProfileType.channelProfileLiveBroadcasting,
));
}catch(e){
print("initialise engine $e");
}

try{
_engine.registerEventHandler(
RtcEngineEventHandler(
onJoinChannelSuccess: (RtcConnection connection, int elapsed) {
debugPrint("local user ${connection.localUid} joined");
setState(() {
_localUserJoined = true;
debugPrint("local _localUserJoined $_localUserJoined _localUserJoined");
});

    },
    onUserJoined: (RtcConnection connection, int remoteUid, int elapsed) {
      debugPrint("remote user $remoteUid joined");
      setState(() {
        _remoteUid = remoteUid;
        remoteUserJoined = true;
      });

    },
    onUserOffline: (RtcConnection connection, int remoteUid, UserOfflineReasonType reason) {
      debugPrint("remote user $remoteUid left channel");
      setState(() {
        _remoteUid = null;
      });
    },
    onTokenPrivilegeWillExpire: (RtcConnection connection, String token) {
      debugPrint('[onTokenPrivilegeWillExpire] connection: ${connection.toJson()}, token: $token');
    },
    onError: (ErrorCodeType err, String msg) {
      debugPrint(
          'Error rtc engin =============================> Code = ${err.name} MSG = $msg');
    },
  ),
);

}catch(e){
debugPrint("local error $e");
}

await _engine.setClientRole(role: ClientRoleType.clientRoleBroadcaster);
await _engine.enableVideo();
await _engine.startPreview();

print("room id ${widget.roomID}");

try{
await _engine.joinChannel(
token: agoraToken,
channelId: agoraChannelId,
uid: int.tryParse(widget.roomID??"0")??0,
options: const ChannelMediaOptions(),
);
}catch(e){
print("_engine join $e");
}`

on dispose i'm using
await _engine.leaveChannel();

@jerrypaulsam
Copy link
Author

jerrypaulsam commented Jul 26, 2023

@laxkarparas1 on dispose add await _engine.release() and see if the error still appear.

@github-actions github-actions bot removed the waiting for customer response waiting for customer response, or closed by no-reponse bot label Jul 26, 2023
@diaaAlterh
Copy link

await engine.initialize(const RtcEngineContext( appId: kAgoraAppId, channelProfile: ChannelProfileType.channelProfileLiveBroadcasting, logConfig: LogConfig(level: LogLevel.logLevelError) ));

just change the logLevel to LogLevel.logLevelError in the log config when initializing the RTC engine

@jerrypaulsam
Copy link
Author

I am getting the same error again which is creating lots of issues. It's literally consuming a lot of memory and no further calls can be received on the device as the incoming call notifications are suppressed as this keeps on printing. The same happens with both dev and release builds.

@littleGnAl
Copy link
Collaborator

@jerrypaulsam
I think it's better to raise a new ticket to the agora support for further investigation of this issue.

@littleGnAl littleGnAl added the waiting for customer response waiting for customer response, or closed by no-reponse bot label Sep 28, 2023
@github-actions
Copy link
Contributor

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.

@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
waiting for customer response waiting for customer response, or closed by no-reponse bot
Projects
None yet
Development

No branches or pull requests

5 participants