# Migrate from Video SDK 3.x (/en/realtime-media/video/reference/migration-guide/react-native) > For AI agents: see the complete documentation index at [llms.txt](/llms.txt). Agora SDK v4.0.0 is a new version of the SDK that you can use to embed real-time video and audio into your app. It supports large-scale real-time interactive activities and provides better real-time interactive effects. For details, see [Benefits and features](/en/realtime-media/video). This page introduces the main steps to upgrade the SDK from v3.x (v3.7.0 and earlier) to v4.0.0, as well as the related changes. ## Migration steps [#migration-steps-7] This section introduces the main steps to upgrade the SDK from v3.x to v4.0.0. ### 1. Integrate the SDK [#1-integrate-the-sdk-3] See [Get started](/en/realtime-media/video/get-started-sdk) for more information about integrating the v4.0.0 SDK into your project. ### 2. Update the Agora code in your app [#2-update-the-agora-code-in-your-app-3] The v4.0.0 SDK has optimized or modified the implementation of some functions, resulting in incompatibility with the v3.7.0 SDK. In order to retain Agora functionality in your app, update the code in your app according to [What has changed](#what-has-changed). ## What has changed [#what-has-changed-6] This section is based on v3.7.0 and introduces the main changes of v4.0.0 compared to v3.7.0 in the following categories. You need to update the code of your app according to your business use-case. * Breaking changes: Introduces API compatibility changes. You need to spend significant time modifying the related implementation. * Behavior changes: Introduces changes caused by reasonable optimization of the SDK default behavior and API behavior. Less time is required to modify the related implementation, if any. * Function gaps: Introduces functions that were supported in v3.7.0 but are not supported in v4.0.0. However, these functions are intended to be added in a future release. * Removed APIs: Introduces APIs that were supported in v3.7.0 but removed in v4.0.0. Most of these APIs have alternatives in v4.0.0. Modifying the related implementation should require less time. * Naming and data type changes: Introduces the naming and data type changes of the main APIs. You can update the relevant implementation according to the error message in the IDE, which is expected to take less time. ### Breaking changes [#breaking-changes-5] After upgrading from v3.7.0 to v4.0.0, the way the APIs implement some functions is different. This section introduces compatibility changes for these APIs and the logic for updating the code of your app. #### Initialize engine [#initialize-engine-1] In v3.7.0, the SDK provides the `create` and `createWithContext` method to create and initialize the `RtcEngine` instance. In v4.0.0, the SDK provides the `createAgoraRtcEngine` method to create the `RtcEngine` instance, and the `initialize` method to initialize the engine. #### Register event listener [#register-event-listener-1] Take `onError` as an example: In v3.7.0, the SDK provides the `addListener` method to register event listener. ```typescript this.engine.addListener('Error', (errorCode) => {}); ``` In v4.0.0, the SDK provides the `registerEventHandler` method to register event listener. ```typescript this.engine.registerEventHandler({ onError(err: ErrorCodeType, msg: string) {}, }); this.engine.addListener('onError', (err: ErrorCodeType, msg: string) => {}); ``` #### Multiple channels [#multiple-channels-6] In v3.7.0, the SDK provides the `RtcChannel` and `RtcChannelEvents` classes to implement multi-channel control. The v3.7.0 SDK supports subscribing to the audio and video streams of multiple channels, but only supports publishing one group of audio and video streams in one channel. v4.0.0 introduces the following changes: * The SDK provides the `IRtcEngineEx` class to join multiple channels. After calling `joinChannel` to join the first channel, call `joinChannelEx` multiple times to join multiple channels, and publish the specified stream to different channels through different user ID (`localUid`) and `ChannelMediaOptions` settings. * Added a binary group `RtcConnection` to represent the connection established by `joinChannel`. A connection is determined by the channel name (`channelId`) and `localUid`. You can control the publishing and subscribing state of different connections through `RtcConnection`. The SDK adds Ex in the name of all APIs with a `connection` parameter (corresponding to the `RtcConnection` class) to distinguish them, and gathers these APIs in the `IRtcEngineEx` class to implement more multi-stream functions. Combined with the multi-channel capability, you can also experience the following functions: * Publish multiple groups of audio and video streams to the remote user through different `localUid`s. * Mix multiple audio streams and publish them to the remote user through one `localUid`. * Mix multiple video streams and publish them to the remote user through one `localUid`. `RtcChannel` and `IRtcEngine` of v3.7.0 are partially duplicated and overlap in their functionality, so v4.0.0 hides the `RtcChannel` and `RtcChannelEvents` classes. See the [JoinMultiChannel](https://github.com/AgoraIO-Extensions/react-native-agora/tree/main/example/src/examples/advanced/JoinMultipleChannel/JoinMultipleChannel.tsx) sample project for more details on how to replace `RtcChannel` with `joinChannel` and `ChannelMediaOptions`. The expected migration cost is one day or less. If you need to continue to use the `RtcChannel` and `RtcChannelEvents` classes, contact [support@agora.io](mailto\:support@agora.io). The decision whether to maintain compatibility in a future release is based on your feedback. #### Media stream publishing control [#media-stream-publishing-control-6] In v4.0.0, the SDK gathers more channel-related settings into `ChannelMediaOptions`, including publishing of audio and video streams from different sources, automatic subscribing of audio and video streams, user role switching, token updating, and default dual stream options. You can determine the media stream publishing and subscribing behavior by calling `joinChannel` or `joinChannelEx` when joining a channel, or you can flexibly update the media options by calling `updateChannelMediaOptions` after joining a channel, such as switching video sources. See the [JoinMultiChannel](https://github.com/AgoraIO-Extensions/react-native-agora/tree/main/example/src/examples/advanced/JoinMultipleChannel/JoinMultipleChannel.tsx) sample project to update the code in your app. #### Warning codes [#warning-codes-4] In v3.7.0, the SDK returns warning codes through the `Warning` event. To facilitate locating and troubleshooting issues, v4.0.0 reports problems and causes through the return values of APIs or different callbacks for listening to states. For example: * `onConnectionStateChanged`: Reports the network connection state. * `onLocalAudioStateChanged`: Reports the local audio state. * `onLocalVideoStateChanged`: Reports the local video state. * `onRemoteAudioStateChanged`: Reports the remote audio state. * `onRemoteVideoStateChanged`: Reports the remote video state. As a consequence, v4.0.0 removes the `Warning` event. ### Breaking changes - v4.0.0 Beta to v4.0.0 [#breaking-changes---v400-beta-to-v400] This section introduces the breaking changes in upgrading the SDK from v4.0.0 Beta to v4.0.0. #### SDK package name [#sdk-package-name-1] After upgrading from v4.0.0 Beta to v4.0.0, the SDK package name has changed from `react-native-agora-rtc-ng` to `react-native-agora`, see [Integrate the SDK](/en/realtime-media/video/get-started-sdk?platform=React%20Native#set-up-your-project-6). #### Join channel [#join-channel-1] In v4.0.0 Beta, the SDK provides the `joinChannel` and `joinChannelWithOptions` methods to join a channel. ```typescript this._engine?.joinChannel(token: string, channelId: string, info: string, uid: number): number; this._engine?.joinChannelWithOptions(token: string, channelId: string, uid: number, options: ChannelMediaOptions): number; ``` In v4.0.0, the original `joinChannel` is removed, and the original `joinChannelWithOptions` is renamed to `joinChannel`. ```typescript this._engine?.joinChannel( token: string, channelId: string, uid: number, options: ChannelMediaOptions ): number; ``` * In v4.0.0, replace `publishAudioTrack` in `ChannelMediaOptions` with `publishMicrophoneTrack`. ### Behavior changes [#behavior-changes-6] This section introduces changes caused by reasonable optimization of the SDK default behavior and API behavior. #### Channel profile [#channel-profile-6] In v3.7.0, the default channel profile is `ChannelProfileCommunication` (the communication profile). Because the interactive streaming profile supports seamless switching from one-to-one calls to multi-user interaction, since v3.0.0, Agora has changed the internal transmission protocol and the ability to resist poor network conditions in the communication profile to be consistent with the interactive streaming profile. In v4.0.0, Agora also changed the default channel profile to `ChannelProfileLiveBroadcasting` (the interactive streaming profile). #### Default log file [#default-log-file-6] In v3.7.0, when the SDK creates multiple log files, the earlier files are named in a agorasdk\_x.log format, such as agorasdk\_1.log. v4.0.0 modified the naming format to agorasdk.x.log, such as agorasdk.1.log. Additionally, v4.0.0 adds the agoraapi.log file to record API logs. #### Fast channel switching [#fast-channel-switching-6] In v3.7.0, you need to call `switchChannel` to quickly switch a channel. In v4.0.0, you can achieve the same switching speed as `switchChannel` in v3.7.0 by switching a channel through `leaveChannel` and `joinChannel`. Therefore, v4.0.0 removes `switchChannel`. If you call `switchChannel` to quickly switch a channel in v3.7.0, you need to call `leaveChannel` to leave the current channel in v4.0.0 and `joinChannel` to join the second channel instead. **Agora self-developed extensions** v4.0.0 adds the feature of automatically loading self-developed dynamic libraries based on v4.0.0 Beta. As of this release, when using an Agora self-developed extension, you do not need to manually integrate the dynamic library in the project. The SDK automatically loads the dynamic library during the initialization phase of `IRtcEngine`. You can directly call the corresponding method of the extension to enable this feature. | API | Extension type | | :---------------------------------------------------------------------------------------------------------------- | :--------------------------- | | `enableVirtualBackground` | Virtual background extension | | * `setBeautyEffectOption` * `setVideoDenoiserOptions` * `setLowlightEnhanceOptions` * `setColorEnhanceOptions` | Video enhancement extension | | `enableRemoteSuperResolution` | Super resolution extension | | - `setAudioEffectPreset` - `setVoiceBeautifierPreset` - `setVoiceConversionPreset` | Voice beautifier extension | | `enableSpatialAudio` | Spatial audio extension | | `enableContentInspect` | Content moderation extension | **Local audio and video recording** In v3.7.0, if you want to enable local audio and video recording, you need to call the `startRecording` method. In v 4.0.0, if you want to enable local audio and video recording, you need to call the `getMediaRecorder` method to get the IMediaRecorder object. **Virtual metronome** When you call `startRhythmPlayer`, the SDK publishes the sound of the virtual metronome to the remote by default. If you do not want the remote users to hear the virtual metronome, refer to the following operations: In v3.7.0, call the `configRhythmPlayer,` and set `publish` to `false`. In v4.0.0, set `publishRhythmPlayerTrack` in `ChannelMediaOptions` to `false`. **Volume indication** You can call the `enableAudioVolumeIndication` method to enable the user's volume indication function. There is a difference in the definition of the `interval` parameter in the `enableAudioVolumeIndication` method between v3.7.0 and v4.0.0, as follows: In v3.7.0, Agora recommends that you set the `interval` to be greater than 200 ms. The minimum is 10 ms; otherwise, the `onAudioVolumeIndication` callback is not received. In v4.0.0, you must set the `interval `to an integer that is a multiple of 200 ms. If the value of `interval` is lower than 200, the SDK automatically adjusts it to 200. When the user's volume indication is enabled, the SDK triggers the `onAudioVolumeIndication` callback at the time interval set in this method. If the local user calls `muteLocalAudioStream` to mute themselves, the SDK behaves inconsistently between v3.7.0 and v4.0.0: In v3.7.0, the SDK immediately stops reporting the local user's volume indication callback. In v4.0.0, the SDK continues to report the local user's volume indication callback. **Device permissions** In v3.7.0, `AudioLocalError.DeviceNoPermission` in `LocalAudioStateChanged` reports that there is no permission to start the capture device, and `LocalVideoStreamError` in `LocalVideoStateChanged` reports that there is no permission to start the video capture device. In v4.0.0, the permission statuses of the audio and video capture devices are both reported in the `onPermissionError` callback. **Pre-call network test** If you need to start or stop the network connection quality test, note the following: In v3.7.0, you can call `enableLastmileTest` to start the network quality test. If you want to stop the network test, you need to call `disableLastmileTest`. In v4.0.0, you can call `startLastmileProbeTest` to enable network quality testing. If you want to stop network testing, you need to call `stopLastmileProbeTest`. #### Remote media event triggering mechanism [#remote-media-event-triggering-mechanism-6] In the following use-cases, the mechanism of triggering remote media events is changed: * Use-case 1: When the host calls `muteLocalAudioStream` or `muteLocalVideoStream` outside the channel to change the publishing status of the local audio or video stream and then joins the channel. * Use-case 2: When the host calls `muteLocalAudioStream` or `muteLocalVideoStream` within the channel to change the publishing status of the local audio or video stream, and then other users join the channel. The behavior differences of Agora SDK between v3.7.0 and v4.0.0 are listed as follow: * In v3.7.0, the local user receives the `remoteAudioStateChangedOfUid` or `remoteVideoStateChangedOfUid` callback, which reports the status changes of the remote host's audio or video streams. * In v4.0.0, instead of the `remoteAudioStateChangedOfUid` or `remoteVideoStateChangedOfUid` callback, the local user receives the `didAudioMuted` or `didVideoMuted` callback, which reports the changes in the remote host's publishing status. #### Video information change event (iOS) [#video-information-change-event-ios-1] If the video capture device is adjusted to landscape or portrait mode during video capture, in v3.7.0 and v4.0.0, the following differences exist in the video information change events reported by the SDK: * In v3.7.0, the `rotation` parameter in the `videoSizeChanged` callback displays the current device rotation information. * In v4.0.0, the `rotation` parameter in the `onVideoSizeChanged` callback is always `0`. ### Function gaps [#function-gaps-6] This section introduces functions that were supported in v3.7.0 but are no longer supported or behave inconsistently in v4.0.0. Plans exist to support them or make them consistent in a future release, however. #### Audio application scenarios [#audio-application-scenarios-5] v4.0.0 reconstructs the audio application scenarios, which can replace most of the audio application scenarios of v3.7.0. The following table shows the correspondence of audio application scenarios in the two releases: | v3.7.0 | v4.0.0 | | :----------------------------------- | :--------------------------- | | `AudioScenarioDefault` | `AudioScenarioDefault` | | `AudioScenarioChatroomEntertainment` | `AudioScenarioChatroom` | | `AudioScenarioEducation` | `AudioScenarioDefault` | | `AudioScenarioGameStreaming` | `AudioScenarioGameStreaming` | | `AudioScenarioShowroom` | `AudioScenarioDefault` | | `AudioScenarioChatroomGaming` | `AudioScenarioChatroom` | | `AudioScenarioIot` | `AudioScenarioDefault` | | `AudioScenarioMeeting` | `AudioScenarioMeeting` | ### Removed APIs [#removed-apis-6] The v4.0.0 removes deprecated or unrecommended APIs. Alternatives to the removed API or reasons for their removal are shown as follows: * `virtualBackgroundSourceEnabled`: Use the return value of `enableVirtualBackground` instead. * `UserSuperResolutionEnabled`: Use the `onRemoteVideoStats` member of the `superResolutionType` class instead. * `setAudioMixingPlaybackSpeed`: Use the relevant API under the `IMediaPlayer` class instead. * `getAudioFileInfo` and `RequestAudioFileInfo`: Use `getDuration` instead. * `setLocalPublishFallbackOption` and `LocalPublishFallbackToAudioOnly`: Rarely used in v3.7.0. * The following enumerations in `AudioMixingReason`: Rarely used in v3.7.0. * `AudioMixingReasonStartedByUser` * `AudioMixingReasonStartNewLoop` * `AudioMixingReasonPausedByUser` * `AudioMixingReasonResumedByUser` * `AudioMixingFinished`: Use `onAudioMixingStateChanged` instead. * `enableDeepLearningDenoise`: The SDK adds deep-learning noise reduction as one of its capability in a future release instead of implementing through an API. * The `channel` parameter in `takeSnapshot` and `onSnapshotTaken`: The parameter is redundant. * `setDefaultMuteAllRemoteVideoStreams: Use` `autoSubscribeVideo` in the `ChannelMediaOptions` instead. * `setDefaultMuteAllRemoteAudioStreams`：Use `autoSubscribeAudio` in the `ChannelMediaOptions` instead. * The `replace` parameter in `startAudioMixing`: Use `publishMicrophoneTrack` in the `ChannelMediaOptions` instead. ### Naming changes [#naming-changes-6] The naming changes in v4.0.0 cause error messages in the IDE when you compile your project, and you need to update the code of your app according to each error message. The main API and parameter name changes are as follows: * `FirstLocalAudioFrame` is changed to `onFirstLocalAudioFramePublished`. * The `fileSize` member in `LogConfig` is renamed to `fileSizeInKB`. * The `report_vad` parameter in `enableAudioVolumeIndication` is changed to `reportVad`.