AgoraIO-Extensions / Agora-Flutter-SDK

Flutter plugin of Agora RTC SDK for Android/iOS/macOS/Windows

Home Page:https://pub.dev/packages/agora_rtc_engine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

agora rtc: when joinChannel and passing a uid it return random aid

Mo0Khaled opened this issue · comments

commented

i am trying to add uid to the joinChannel but it returns random id

what is written on the docs is:

[uid] The user ID. This parameter is used to identify the user in the channel for real-time audio and video interaction. You need to set and manage user IDs yourself, and ensure that each user ID in the same channel is unique. This parameter is a 32-bit unsigned integer. The value range is 1 to 2 32 -1. If the user ID is not assigned (or set to 0), the SDK assigns a random user ID and returns it in the onJoinChannelSuccess callback. Your application must record and maintain the returned user ID, because the SDK does not do so.

so i passed the id but not return back as expected any idea?

await agoraEngine.joinChannel(
        token: currentSessionCredential.rtcToken,
        channelId: channelName!,
        options: options,
        uid: myUserId,
      );

I think you can get the myUserId when onJoinChannelSuccess is received.

commented

nope it returns a random id instead of the actual id i passed to the function!

Can you share more logs, and what uid you get from the onJoinChannelSuccess callback.

commented

it returns the id but it's random one !

Can you share the logs that run into this issue?

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.