What's New in this Release?
What's New in This Release?
Release 25.10 of the Client SDK for macOS contains bug fixes and stability enhancements.
Release 25.10 of the Client SDK for macOS contains bug fixes and stability enhancements.
The SDK package comes with a sample command line pre-session client called the Collaboration Broker Client Example, which calls the included broker client libraries and enables you to join a PCoIP collaboration session. The Collaboration Broker Client API Example demonstrates the success path for joining a PCoIP collaboration session.
Once you have successfully established a session between a Anyware Client and an Anyware host, you can start developing your own Anyware client. To begin, set up your client development environment, as discussed next.
To set up your client development environment:
In order to customize your session client, you must create a client branding package using the HP Custom Branding Package Utility. The HP Custom Branding Package Utility is located in the following location:
To create a custom branding package:
This example calculates a certificate hash that is intended to be added to the Windows registry for the USB driver configuration. This example is meant for SDK users that need to allow their own signed applications to access USB functionality in Windows. For more information see the PCoIP SDK USB Windows driver documentation.
The steps below are meant as a quick start guide for developers.
You can customize the branding of your custom session client in several ways by creating a client branding package. These customizations affect the user’s experience once they have connected to their PCoIP session. The following elements can be customized in the session client:
Invoking the Broker Client API is a two-step procedure, where as a first step, the Broker Client Example is built. The second step consists of running either a prebuilt PCoIP binary, or a prebuilt AWS binary.
Finding the Latest Information
The steps below are meant as a quick start guide for developers.
The online SDK user guide has detailed information on this example. A description of the PCoIP Core Library is also available in the administrator's guide.
Transferring non-HID USB devices from the client to the host is called bridging. Both the Anyware agent on the host machine and the Anyware client must enable bridging before devices can be transferred. Administrators can globally disable USB bridging support, or enforce device whitelists or blacklists, using GPO variables on the host machine. Clients cannot bridge devices that are disallowed by the agent.
The macOS has elements which are part of the operating system user interface and cannot be modified programmatically, as described in the following sections.
The following run-time limitations are enforced by macOS on the application menu (beside the menu apple icon menu):