bitbound/ControlR v0.30.10.0

v0.30.10.0 Release

on GitHub

Breaking Changes

• The ControlR.ApiClient package no longer exposes the internals used to sign in and keep sign-in tokens alive. Custom integrations or automation built directly against the old sign-in types must be updated to use the sign-in session interface.
  • See Internal notes for details.
• The remote control message types in the shared contracts packages were renamed. Custom integrations or automation compiled directly against the contracts or relay client packages must be updated to the new type names. Remote control wire compatibility is unaffected.
  • See Internal notes for details.

Enhancements

• Added a permission check to the remote control privacy screen. The web app and the Avalonia viewer do not offer the toggle unless the viewer has the permission.
• Custom branding now supports SVG files for the icon and logo.

Fixes

• Fixed ControlR.ApiClient renewing the sign-in token before every request when the token's lifetime was shorter than the configured refresh lead time.
• Improved the reliability of the remote control client at the Linux X11 login screen.
• Saving a duplicate permission assignment is now rejected with a clear "already exists" error.

Removals

None.

Internal

• ControlR.ApiClient bearer auth rework. IControlrAuthSession is the only sign-in surface. IBearerTokenRefresher, BearerTokenRefresher, BearerTokenRefreshResult, AuthState, BearerRefreshContext, the bearer setters and BearerRefreshLock on ControlrApiClientAuthState, and the public ControlrAuthSession constructor are gone. The public ControlrApi constructor no longer takes an IBearerTokenRefresher; build clients through AddControlrApiClient, ControlrApiClientBuilder, or ControlrApiClientFactory.
• Bearer token renewal is now on-demand and keyed to the exact token the failed request carried, replacing the background refresh loop.
• The new permission device.remote-control.privacy-screen gates the privacy screen toggle. The DeviceSuperUser preset role grants it. Other roles do not get it automatically. DeviceAccessPermissionsDto.CanTogglePrivacyScreen carries the grant to the viewers.
• IViewerHub.RequestRemoteControlSession2 is marked [Obsolete] in favor of RequestRemoteControlSession3.
• ControlR.Libraries.Api.Contracts exposes one RemoteControlDtoType/RemoteControlDtoWrapper pair for remote control messages, replacing the released DtoType/DtoWrapper. Tag values and the serialized envelope are unchanged. Mixed client, agent, and relay versions keep interoperating on the wire. The relay client package's send and message-handler signatures use the same wrapper.
• Selecting the VPX encoder on the desktop client now fails fast. No viewer decodes VideoStreamPacket frames, so the option only produced unsupported-DTO warnings.
• CI: per-platform build steps extracted into reusable composite actions, published release tags sync to the private mirror repo, and signing secrets were renamed to the BBB_ scoped scheme.