Knowledge Base

Setting up your Xcode Project

The TeamViewer SDK uses the camera and microphone during a remote support session.

1) Add the following keys to the Info.Plist file:

• NSMicrophoneUsageDescription
• NSCameraUsageDescription

2) Set a delegate conforming to the protocol TeamViewerSDKDelegate.

This ensures you are able to react to events happening during the lifetime of your TeamViewer connection.

3) Connect to a session code

The shared SDK provides a method for establishing a connection to a session code. This session code can be of two types:

• Remote Support or 
• Assist AR

4) Create session codes in your TeamViewer client or via the TeamViewer REST API.

The method connectToSessionCode returns a TeamViewer session.

IMPORTANT: You are responsible for keeping this variable alive, and also responsible for freeing up this variable. Failing to do so might result in the session UI being kept alive even after the remote session has ended. 

IMPORTANT: Once the SDK connects to a session code, it enters a waiting state, you get notified about the state change via the delegate method handleSessionCodeOnline.

At this point, you should not allow the user to connect to a different session code. It is only allowed to allow the user to leave the current connection.

On the supporter side, the session code will appear as being online, allowing the client to establish a connection to that session code.

Reacting to incoming connections

The SDK provides delegate methods for reacting to incoming connection events.

Once the connection is initiated on the TeamViewer side, the SDK gets notified about this connection attempt via the delegate method handleConnectionRequestWithAuthenticationData.

On the authentication data parameter there is the name of the supporter, the type of incoming connection (ScreenShare or Assist AR) and a callback function to allow or reject the incoming connection.

If the incoming connection is accepted, the corresponding TeamViewer connection is established.

• For the ScreenShare connection, a prompt for microphone and screen sharing is shown to the user.

The UI of your application is grabbed using the replay kit and there is bi-directional VoIP communication between the user and the supporter.

• For the Assist AR connection, the system permissions for camera and microphone access are shown. If the user allows this, the AR session is started. There is bi-directional VoIP communication between the user and the supporter.
• The delegate method handleConnectionRequestAbort should be implemented in order to be notified when the remote user cancels the connection request. You are responsible to clear any prompts that are shown to the user, or to cancel any CallKit incoming call notifications.

Reacting to optional SDK events

• handleSupporterConnected: This method gets called when the supporter has ended the session, it also gets called when the user has locally ended the session.
• handleSupporterDisconnected: This method gets called when the supporter has ended the session, it also gets called when the user has locally ended the session. 

Hint: You should clean the references to the session as the session is considered no longer valid at this point.

• handleError: This method gets called if the session code or the API token used for establishing a connection are not valid. 

Hint: You should clean the resources used for the current session as the session itself is considered invalid.

Reacting to optional session events

• handleSessionError: This gets called when an error has occurred during the session. For example, a feature was requested but the compatibility between client and server was not met.

Hint: This error is only informative. You can write it to a log file.

Note about CallKit support

If your application supports CallKit:

• Provide the TeamViewer SDK with information about the unique identifier of your call.
• TeamViewer asks the system if there is a running call and does not try to set up a VoIP connection if this is the case.
• Tell TeamViewer that the current call is yours so we can take over the audio pipeline and start the VoIP transmission:
  1. Call the setupCallUUID method.
  2. Tell the SDK that your call has ended by calling the clearCallUUID method.

Enabling background modes

Ensure that you have at least one of these background modes enabled in your Info.plist file:

• Audio,
• AirPlay or
• Voice over IP background mode. 

IMPORTANT: Failing to do so will cause the app to get suspended only a few seconds after being put in the background during an active TeamViewer session.

Audio setup

The mobile SDK works with the default AVAudioSession configuration values.

• If you want to override these values to support Bluetooth, Airplay mix, use loudspeakers, etc., make sure to change this before a session is established. In case your application mutes other apps, the recommended point in time to configure the audio session is right before accepting the connection.
• If your application audio mixes with other apps, you can configure the audio options at the application launch.