Last updated: 2021-06-17 19:23:55

    TRTC supports two screen sharing schemes on iOS:

    • In-application sharing
      With in-application sharing, sharing is limited to the screens of the current application. It is supported on iOS 13 and above. As screens outside the current application cannot be shared, the scheme is suitable for scenarios with high requirements for privacy protection.
    • Cross-application sharing
      Based on Apple's ReplayKit scheme, cross-application sharing allows the sharing of screens across the system, but the steps required to implement the scheme are more complicated than those for in-application sharing because the application must provide an additional extension.

    Please note that the mobile editions of the TRTC SDK do not support "substream sharing" as the desktop editions do, for both iOS and Android ban the use of the camera by applications running in the background. It’s therefore of little point for the mobile editions to support the feature.

    Supported Platforms

    iOS Android macOS Windows Electron Chrome

    In-application Sharing

    You can implement the in-application sharing scheme simply by calling the startScreenCaptureInApp API provided by the TRTC SDK, with the encoding parameter TRTCVideoEncParam passed in. If the parameter is set to nil, the SDK will use the values set before the screen sharing.

    We recommend the following encoding settings for screen sharing on iOS:

    Item Parameter Name Recommended Value for Regular Scenarios Recommended Value for Text-based Teaching
    Resolution videoResolution 1280 × 720 1920 × 1080
    Frame rate videoFps 10 FPS 8 FPS
    Highest bitrate videoBitrate 1600 Kbps 2000 Kbps
    Resolution adaption enableAdjustRes No No
    • As screen content generally does not change drastically, it is not economical to use a high FPS. We recommend setting it to 10 FPS.
    • If the screen you share contains a large amount of text, you can increase the resolution and bitrate accordingly.
    • The highest bitrate (videoBitrate) refers to the highest output bitrate when a shared screen changes dramatically. If the shared content does not change a lot, the actual encoding bitrate will be lower.

    Cross-application Sharing

    Sample code

    You can find the sample code for cross-application sharing in the ScreenShare directory of this GitHub page, which contains the following files:

    ├─ TRTC-API-Example-OC              // TRTC API examples 
    |  ├─ Basic                   // Demonstrates the cross-application screen sharing feature
    |  |  ├─ ScreenShare                   // Demonstrates the cross-application screen sharing feature
    |  |  |  ├── ScreenAnchorViewController.h
    |  |  |  ├── ScreenAnchorViewController.m       // Screen recording view for anchor
    |  |  |  ├── ScreenAnchorViewController.xib
    |  |  |  ├── ScreenAudienceViewController.h
    |  |  |  ├── ScreenAudienceViewController.m     // Screen recording watching view for audience
    |  |  |  ├── ScreenAudienceViewController.xib
    |  |  |  ├── ScreenEntranceViewController.h
    |  |  ├─ ScreenEntranceViewController.swift    // Screen sharing starting view
    |  |  |  ├── ScreenEntranceViewController.xib
    |  |  |  ├── TRTCBroadcastExtensionLauncher.h
    |  |  |  ├── TRTCBroadcastExtensionLauncher.m   // Supplementary code for starting screen recording
    |  |  |  ├── TXReplayKit_Screen   // Code for the screen recording process Broadcast Upload Extension. For details, see step 2.
    |  |  |  │   ├── Info.plist
    |  |  |  │   ├── SampleHandler.h
    |  |  |  │   └── SampleHandler.m                // Code for receiving screen recording data from the system

    You can run the demo as instructed in README.


    For cross-application screen sharing on iOS, you need to add a screen sharing extension to work with the host application for push. The screen sharing extension is created by the system when screen sharing needs to be started and is used to receive the captured screen image; therefore, you need to perform the following steps:

    1. Create an application group (App Group) and configure it in Xcode (optional) to enable communication between the Broadcast Upload Extension and host application.
    2. Create a target of Broadcast Upload Extension in your project and integrate into it TXLiteAVSDK_ReplayKitExt.framework from the SDK package, which is tailored for the extension module.
    3. Make the host application wait to receive screen recording data from the Broadcast Upload Extension.
    4. Use a helper class (RPSystemBroadcastPickerView) already implemented in the demo to make it possible to start screen sharing by tapping a button (optional), as in VooV Meeting for iOS.

    If you skip step 1, that is, if you do not configure an App Group (by passing in nil to the API), you can still enable screen sharing, but its stability will be compromised. Therefore, to ensure the stability of screen sharing, we suggest that you configure an App Group as described in this document.

    Step 1. Create an App Group

    Log in to and do the following (please download the corresponding provisioning profile again afterwards.)

    1. Click Certificates, IDs & Profiles.
    2. Click "+" next to Identifiers.
    3. Select App Groups and click Continue.
    4. In the form that pops up, fill in the Description and Identifier boxes. For "Identifier", you need to pass in the AppGroup parameter in the API. After this, click Continue.
    5. Return to the Identifiers page, select App IDs, and click your App ID (you need to configure the AppID of the host application and extension in the same way).
    6. Select App Groups and click Edit.
    7. In the form that pops up, select the App Group you created, click Continue to return to the edit page, and click Save to save the settings.
    8. Download the provisioning profile again and import it to Xcode.

    Step 2. Create a Broadcast Upload Extension

    1. In the Xcode menu, click File > New > Target... > Broadcast Upload Extension.
    2. In the dialog box that pops up, enter the information required. You don't need to check Include UI Extension. Click Finish to complete the creation.
    3. Drag TXLiteAVSDK_ReplayKitExt.framework in the SDK package into the project and select the target created.
    4. Click + Capability, and double-click App Groups, as shown below:
      A file named target name.entitlements will appear in the file list as shown below. Select it, click "+", and enter the App Group created earlier.
    5. Select the target of the host application and configure it in the same way as described above.
    6. In the new target, Xcode will automatically create a SampleHandler.m file. Replace the file content with the following code. You need to change APPGROUP in the code to the App Group Identifier created earlier.
    #import "SampleHandler.h"
    @import TXLiteAVSDK_ReplayKitExt;

    #define APPGROUP @""

    @interface SampleHandler() <txreplaykitextdelegate>

    @implementation SampleHandler
    // Note: replace `APPGROUP` with the App Group Identifier created earlier.
    - (void)broadcastStartedWithSetupInfo:(NSDictionary<nsstring *,nsobject *> *)setupInfo {
    [[TXReplayKitExt sharedInstance] setupWithAppGroup:APPGROUP delegate:self];

    - (void)broadcastPaused {
    // User has requested to pause the broadcast. Samples will stop being delivered.

    - (void)broadcastResumed {
    // User has requested to resume the broadcast. Samples delivery will resume.

    - (void)broadcastFinished {
    [[TXReplayKitExt sharedInstance] finishBroadcast];
    // User has requested to finish the broadcast.

    #pragma mark - TXReplayKitExtDelegate
    - (void)broadcastFinished:(TXReplayKitExt *)broadcast reason:(TXReplayKitExtReason)reason
    NSString *tip = @"";
    switch (reason) {
    case TXReplayKitExtReasonRequestedByMain:
    tip = @"Screen sharing ended";
    case TXReplayKitExtReasonDisconnected:
    tip = @"Application disconnected";
    case TXReplayKitExtReasonVersionMismatch:
    tip = @"Integration error (SDK version mismatch)";

    NSError *error = [NSError errorWithDomain:NSStringFromClass(self.class)
    [self finishBroadcastWithError:error];

    - (void)processSampleBuffer:(CMSampleBufferRef)sampleBuffer withType:(RPSampleBufferType)sampleBufferType {
    switch (sampleBufferType) {
    case RPSampleBufferTypeVideo:
    [[TXReplayKitExt sharedInstance] sendVideoSampleBuffer:sampleBuffer];
    case RPSampleBufferTypeAudioApp:
    // Handle audio sample buffer for app audio
    case RPSampleBufferTypeAudioMic:
    // Handle audio sample buffer for mic audio


    Step 3. Make the host application wait to receive data

    Before screen sharing starts, the host application must be put on standby to receive screen recording data from the Broadcast Upload Extension. To do this, follow these steps:

    1. Make sure that camera capturing has been disabled in TRTCCloud; if not, call stopLocalPreview to disable it.
    2. Call the startScreenCaptureByReplaykit:appGroup: API, passing in the AppGroup set in step 1 to put the SDK on standby.
    3. The SDK will then wait for a user to trigger screen sharing. If a button is not added as described in step 4, users need to press and hold the screen recording button in the iOS Control Center to start screen sharing.
    4. You can call the stopScreenCapture API to stop screen sharing at any time.
    // Start screen sharing. You need to replace `APPGROUP` with the App Group Identifier created earlier.

    - (void)startScreenCapture {
    TRTCVideoEncParam *videoEncConfig = [[TRTCVideoEncParam alloc] init];
    videoEncConfig.videoResolution = TRTCVideoResolution_1280_720;
    videoEncConfig.videoFps = 10;
    videoEncConfig.videoBitrate = 2000;
    // You need to replace `APPGROUP` with the App Group Identifier created earlier.
    [[TRTCCloud sharedInstance] startScreenCaptureByReplaykit:videoEncConfig

    // Stop screen sharing
    - (void)stopScreenCapture {
    [[TRTCCloud sharedInstance] stopScreenCapture];

    // Event notification for the start of screen sharing, which can be received through `TRTCCloudDelegate`
    - (void)onScreenCaptureStarted
    [self showTip:@"Screen sharing started"];

    Step 4. Add a screen sharing triggering button (optional)

    In step 3, users need to start screen sharing manually by pressing and holding the screen recording button in the Control Center. To make it possible to start screen sharing by tapping a button in your application as in VooV Meeting, follow these steps:

    1. Find the TRTCBroadcastExtensionLauncher class in the demo and add it to your project.
    2. Add a button to your UI and call the launch function of TRTCBroadcastExtensionLauncher in the response function of the button to trigger screen sharing.
      // Customize a response for button tapping
      - (IBAction)onScreenButtonTapped:(id)sender {
      [TRTCBroadcastExtensionLauncher launch];

    • Apple added RPSystemBroadcastPickerView to iOS 12.0, which can show a picker view in apps for users to select whether to start screen sharing. Currently, RPSystemBroadcastPickerView does not support custom UI. Nor does Apple provide an official triggering method.
    • TRTCBroadcastExtensionLauncher works by going through the subviews of RPSystemBroadcastPickerView, finding the UI button, and triggering its tapping event.
    • Please note that this scheme is not recommended by Apple and may become invalid in its next update. We have therefore made step 4 optional. You need to bear the risks arising from implementing the scheme yourself.

    Viewing Shared Screens

    • Watch screens shared by macOS/Windows users
      When a macOS/Windows user in a room starts screen sharing, the screen will be shared through a substream, and other users in the room will be notified through onUserSubStreamAvailable in TRTCCloudDelegate.
      Users who want to watch the shared screen can start rendering the substream image of the remote user by calling the startRemoteSubStreamView API.

    • Watch screens shared by Android/iOS users
      When an Android/iOS user starts screen sharing, the screen will be shared through the primary stream, and other users in the room will be notified through onUserVideoAvailable in TRTCCloudDelegate.
      Users who want to watch the shared screen can start rendering the primary stream of the remote user by calling the startRemoteView API.