Release/rtc ng/4.4.0 #3703
Merged
Release/rtc ng/4.4.0 #3703
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ource into release/rtc-ng/4.4.0
…ource into release/rtc-ng/4.4.0
…ource into release/rtc-ng/4.4.0
Cilla-luodan
commented
Jul 15, 2024
| <li props="android">This version removes the <codeph>buffer</codeph>, <codeph>uid</codeph>, and <codeph>timeStampMs</codeph> parameters of the <apiname keyref="onMetadataReceived"/> callback. You can get metadata-related information, including <codeph>timeStampMs</codeph> (timestamp of the sent data), <codeph>uid</codeph> (user ID), and <codeph>channelId</codeph> (channel name) through the newly-added <codeph>metadata</codeph> parameter.</li> | ||
| <li props="ios">Before v4.4.0, when a user role was set to audience and called <codeph><apiname keyref="setAudioScenario"/></codeph> to set the audio scenario to chatroom (<codeph><apiname keyref="AUDIO_SCENARIO_CHATROOM"/></codeph>), the user would see a microphone permission request popup. As of v4.4.0, the SDK uses native iOS APIs to control the microphone, so audience members in a chatroom scenario will no longer receive the microphone permission request popup.</li> | ||
| <li props="apple">This version renames the <codeph>receiveMetadata</codeph> callback to <codeph><apiname keyref="onMetadataReceived"/></codeph> and removes the <codeph>data</codeph> and <codeph>timeStamp</codeph> parameters. You can get metadata-related information, including <codeph>timeStamp</codeph> (timestamp of the sent data), <codeph>uid</codeph> (user ID), and <codeph>channelId</codeph> (channel name) through the newly-added <codeph>metadata</codeph> parameter.</li> | ||
| <li props="android">This version removes the <codeph>buffer</codeph>, <codeph>uid</codeph>, and <codeph>timeStampMs</codeph> parameters of the <codeph><apiname keyref="onMetadataReceived"/></codeph> callback. You can get metadata-related information, including <codeph>timeStampMs</codeph> (timestamp of the sent data), <codeph>uid</codeph> (user ID), and <codeph>channelId</codeph> (channel name) through the newly-added <codeph>metadata</codeph> parameter.</li> |
There was a problem hiding this comment.
android 和 ios 废弃的 destroyMusicPlayer 在中文发版说明和 sunset 里没有加，需要排查一下
Cilla-luodan
commented
Jul 15, 2024
jinyuagora
reviewed
Jul 15, 2024
…ource into release/rtc-ng/4.4.0
…ource into release/rtc-ng/4.4.0
…ource into release/rtc-ng/4.4.0
Cilla-luodan
commented
Jul 15, 2024
| </ul></li> | ||
| <li props="windows">在 v4.4.0 之前，音视频设备已插入、已就绪均会通过 <codeph><apiname keyref="MEDIA_DEVICE_STATE_TYPE"/></codeph> 中的 <codeph><apiname keyref="MEDIA_DEVICE_STATE_IDLE"/></codeph> 状态报告。为进一步区分设备状态，自 v4.4.0 起，SDK 会通过新增的 <codeph><apiname keyref="MEDIA_DEVICE_STATE_PLUGGED_IN"/></codeph> 报告设备已插入。</li> |
There was a problem hiding this comment.
因为回调返回的是 int，需要在枚举后面加数字
…ource into release/rtc-ng/4.4.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.