Changelog Version 2.7.5

With the release of version 2.7.5, TeamViewer introduces support for Augment Session invites initiated during an embedded session. This feature allows a supporter to effortlessly invite a machine operator to an augmented session (AssistAR session). The session invite is received from a connected TeamViewer agent, and applications integrating the SDK can display the invite to the machine operator for a seamless session transition. The SDK includes a fully functional implementation, demonstrated in the qt_simulate example.
Read more on that feature on our knowledge base article.

Additionally, this update includes a compile fix for C++17, the removal of X11 headers, and a switch to xkbcommon headers, benefiting customers who do not use any X headers in their build environment.

Version 2.6.15

Changelog Version 2.6.15

With version 2.6.15 TeamViewer is releasing a bugfix where it was not possible to build the SDK when GRPC communication was turned off.

Additional various files have been removed as they moved to a new location.

Version 2.6.14

Changelog Version 2.6.14

With version 2.6, TeamViewer is releasing additional features for the C++ Agent API and the Qt plugin, which simplifies the integration into applications running on other network hosts reachable by the TeamViewer embedded Agent.

Furthermore, the Qt plugin is officially supporting Qt6. The default for the configure command is still Qt5. Please consult the documentation for the right command using Qt6.

The SDK also now supports an additional Access Control for screen recording. With that any integration can define before the session if screen recording is allowed, denied or only allowed after the integration gives the approval.

Version 2.4.8

Changelog Version 2.4

With version 2.4, TeamViewer is releasing additional features for the C++ Agent API, which simplifies integration into non-Qt-based applications. The new API provides the functionality of

• access controls for file transfer and screen control
• chatting between the operator and the supporter

Furthermore, TeamViewer is officially extending the API interfaces with Python bindings. This was already included in the previous release as experimental. All C++ examples are also available as Python scripts.

TeamViewer wants to make it as easy as possible for you to test drive the full API functionality. Therefore, we also provide prebuilt binaries for aarch64, amd64, armv5el, armv5hf, armv7 and i386 architectures attached to this release. In combination with the TeamViewer IoT Agent, you can easily test the capabilities of the Agent SDK. The prebuilt binaries are based on the code available in the examples folder.

Improvements

• Access Controls
  • With access controls, integrators can steer the capabilities of the supporter on the local machine. The application can set access permissions for individual capabilities such as file transfer or viewing the screen to allowed, after confirmation, or denied. If the permission for a particular feature is set to after confirmation, the application integrating this SDK will receive a notification when the remote supporter attempts to use the feature. Within this notification, the application can then decide whether to allow or deny the request. Refer to our examples to see how you can enrich your application and your remote support experience with improved control over individual features.
• Chat
  • In the use case of providing remote assistance to a customer, it can often be helpful to exchange text messages. Command line instructions or a predefined step-by-step guide can help the customer easily address the issue at hand. With the TeamViewer chat functionality, it is possible to chat both with the supporter assigned to the service case, as well as to the machine itself. The chat capability supports the TeamViewer chat room architecture and can be used with any client that supports standard TeamViewer chat. Refer to our examples to see how you can enrich your application with bidirectional chat capability which may sometimes be all that's needed to solve a case.
• Python Binding
  • After a concentrated phase of testing and improvements, our Python bindings are moving out of the experimental stage. You can now use instant support, session management, access controls and chat directly from within your Python application. All C++ example code is now also available in Python.

Version 2.3.0

Changelog Version 2.3

With version 2.3, TeamViewer is releasing the C++ Agent API, which simplifies integration into non-Qt-based applications. The new API provides the functionality of

• creating and reactivating service cases
• managing incoming connections
• announcing running and closing TeamViewer sessions
• terminating TeamViewer sessions

Integrators can refer to the provided code examples to build their own attended access support story around their application. You could integrate the Agent API into a web server and grant access to your web application only via preliminary approval on that page. Another example is that the approval is done through a hardware switch on your machine, etc.

Improvements

• Instant support functionality
  • Create service cases
    • This is the functionality of a typical help button. The integrator is providing a help button within their app, which will automatically create a service case via our SDK.
  • Approve / deny incoming connections
  • Activate / reactivate service cases
    • With this functionality a supporter could create a service case in the management console and share the session id with the operator. When the SDK is receiving this session code and the right access token (connected to the supporter who created the session code), the service case will go online, and the supporter would be able to connect.
• Session management
  • With the session management, the integrator can orchestrate the ongoing session. This means he can terminate all ongoing session with one SDK call. Furthermore, the SDK notifies any joining or leaving participant within the session. This capability allows then the integrator to show the operator of the embedded device if and how many supporters are currently connected to the machinery.
• Access Controls
  • The embedded solution only provides a subset of the TeamViewer access controls. Mainly used is the possibility to control the access for file transfer. The SDK provides to set it to Allow, Deny or After Confirmation. When set to After Confirmation, the SDK will notify about any request and leaves it up to the integrator to obtain the answer from the user.
• There is an experimental python binding used for internal testing.