Closed GDGRhinox closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.
Still using a local edited built instead of an official release to handle this issue internally, this issue affects other users as well as I have read on Unity user forums. Thus fixing it upstream would be preferable.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.
Description
When using the PusherSDK on a Unity .NET project, the WebSocket is created using a Unity Mono backend instead of standard .NET. Using Unity Mono websockets prevents us from connecting to a standard soketi setup of a Pusher server.
This is because the default WebSocket gets rejected and furthermore the current settings do not allow a self-signed certificate to be used. This change introduces an event which allows users of the PusherSDK to receive an event before a WebSocket connection is opened, thus allowing them to modify the supported TLS version and add custom certificates.
CHANGELOG