Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 15 days ago
    Edited by Carl Hansen 15 days ago

    Hi Team,

    We have been running an Azure Function App for roughly 4 years without issue until 30/01/2026.

    The issue lies within registering a WebSocket connection for notification of Contact List Export endpoint. We get intermittent failures where some contact lists export without issue and some fail. On failure we run into the following error:

    Inner exception System.PlatformNotSupportedException handled at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw:
   at System.Action`1.BeginInvoke (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at WebSocketSharp.WebSocket.open (websocket-sharp, Version=1.0.2.59611, Culture=neutral, PublicKeyToken=5660b08a1845a91e)
   at WebSocketSharp.WebSocket.Connect (websocket-sharp, Version=1.0.2.59611, Culture=neutral, PublicKeyToken=5660b08a1845a91e)
   at PureCloudPlatform.Client.V2.Extensions.Notifications.NotificationHandler.ConnectSocket (PureCloudPlatform.Client.V2, Version=165.0.0.0, Culture=neutral, PublicKeyToken=null)
   at PureCloudPlatform.Client.V2.Extensions.Notifications.NotificationHandler..ctor (PureCloudPlatform.Client.V2, Version=165.0.0.0, Culture=neutral, PublicKeyToken=null)
   at App.Export.Run (App, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: C:\Export.cs:43)

    The function app is running .NET Framework 4.8 on a Windows App Service Plan.

    I have tried:

    • Restart the function app - did not work.
    • Check for Azure update to function app - no update in last 30 days.
    • Check for environment variables/configuration change - no change in last 30 days.
    • Check for changed code - no change for 2 years.
    • Check for expired credentials - did not expire.
    • Check change to role/permissions - no change.
    • Check for change to contact list IDs - no change.
    • Check PureCloud SDK for code updates - affected code not changed in SDK.

    I cannot figure out what is going on.

    Has there been any change on Genesys' side? Any assistance would be great please.

    The affected code is below:

    using System;
using System.Net;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
using Microsoft.WindowsAzure.Storage;
using Microsoft.WindowsAzure.Storage.Blob;
using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Extensions.Http;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;
using Newtonsoft.Json;
using PureCloudPlatform.Client.V2.Api;
using PureCloudPlatform.Client.V2.Client;
using PureCloudPlatform.Client.V2.Extensions;
using PureCloudPlatform.Client.V2.Model;
using PureCloudPlatform.Client.V2.Extensions.Notifications;
using WebSocketSharp;
using System.Threading;

namespace App
{
    public class Export
    {
        [FunctionName("Export")]
        public static HttpResponseMessage Run(
            [HttpTrigger(AuthorizationLevel.Function, "GET", Route = null)]
            HttpRequest req,
            ILogger logger)
        {
            PureCloudRegionHosts region = PureCloudRegionHosts.ap_southeast_1;
            Configuration.Default.ApiClient.setBasePath(region);

            var clientId = Environment.GetEnvironmentVariable("Id");
            var clientSecret = Environment.GetEnvironmentVariable("Secret");
            var accessTokenInfo = Configuration.Default.ApiClient.PostToken(clientId, clientSecret);

            Configuration.Default.AccessToken = accessTokenInfo.AccessToken;

            var accessToken = Configuration.Default.AccessToken;
            var apiInstance = new OutboundApi();
            var contactListId = req.Headers["contactListId"];
/* fail */  var handler = new NotificationHandler(); // This is where the exception triggers

            // Get the contact list object
            var contactList = GetOutboundContactList(apiInstance, contactListId, logger);

            ResponseObject response = new ResponseObject();

            response.contactListId = contactList.Id;
            response.contactListName = contactList.Name;
            response.contactListSize = contactList.Size ?? 0;

            // Check if contact list is empty don't need to export if it is
            if (contactList.Size == 0)
            {
                response.result = "Contact list is empty!";

                return new HttpResponseMessage(HttpStatusCode.OK)
                {
                    Content = new StringContent(JsonConvert.SerializeObject(response, Formatting.Indented), Encoding.UTF8, "application/json")
                };
            }

            // This is so we get notified when the Contact List Export is complete
            // API user doesn't have a user context, so we can't programatically get
            // the user ID so it's hard-coded below
            handler.AddSubscription($"v2.users.oauth-id-abc-def.outbound.contactlists.{contactListId}.export", typeof(ContactlistDownloadReadyExportUri));

            PostOutboundContactListExport(apiInstance, contactListId, logger);

            string exportUri = null;
            // Wait until we get the notification that the export is complete

            int numOfAttempts = 1;
            do
            {
                handler.NotificationReceived += (eventData) =>
                {
                    if (eventData.GetType() == typeof(NotificationData<ContactlistDownloadReadyExportUri>))
                    {
                        var typedEventData = (NotificationData<ContactlistDownloadReadyExportUri>) eventData;
                        exportUri = typedEventData.EventBody.Uri;
                    }
                };

                numOfAttempts++;
                // Delay for 5 seconds;
                Thread.Sleep(5000);

            } while (exportUri.IsNullOrEmpty());

            var data = GetOutboundContactListExportData(accessToken, exportUri, logger);

            var fileName = $"{contactList.Name} Export {DateTime.Now.ToString("yyyyMMddHHmmss")}.csv";
            UploadFileToBlobStore(data, fileName, logger);

            response.blobContainerName = Environment.GetEnvironmentVariable("BlobContainerName");
            response.blobFileName = fileName;
            response.result = "Great success!";

            return new HttpResponseMessage(HttpStatusCode.OK)
            {
                Content = new StringContent(JsonConvert.SerializeObject(response, Formatting.Indented), Encoding.UTF8, "application/json")
            };
        }

        /* More code... */
}


    #PlatformSDK

    ------------------------------
    Carl Hansen
    ------------------------------



  • 2.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 14 days ago
    Edited by Chris Anderson 14 days ago

    I'm getting the same error.  This also started for us on January 30th.  It doesn't happen every time I try to open a notification handler, though, which makes it equally frustrating.  This is the 

    System.PlatformNotSupportedException: Operation is not supported on this platform.
   at System.Action`1.BeginInvoke(T obj, AsyncCallback callback, Object object)
   at WebSocketSharp.WebSocket.open()
   at WebSocketSharp.WebSocket.Connect()
   at PureCloudPlatform.Client.V2.Extensions.Notifications.NotificationHandler.ConnectSocket(String uri, String proxyURI, String proxyUsername, String proxyPassword)
   at PureCloudPlatform.Client.V2.Extensions.Notifications.NotificationHandler..ctor(NotificationsApi notificationsApi)

    My application has been running without issues for quite some time and we haven't done any deployments since June 2025, nor have we made any changes to our architecture.

    My application is deployed as an Azure App Service running on .NET 8 on Windows.

    I would love to get some feedback from Genesys on what could be causing this.



    ------------------------------
    Chris Anderson
    Senior Consultant
    ------------------------------

    Original Message


  • 3.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 14 days ago

    I'm supporting a customer as well with the exact same issue. They are also using .NET application and receive System.PlatformNotSupportedException: 'Operation is not supported on this platform.' on new PureCloud.Platform.Client.V2.NotificationHandler() since Monday morning.

    Opened up support case and at the moment the last feedback is that no changes were made on the end of Genesys and support is now requesting to following:

    Open the legacy Control Panel, go to Programs and Features, and click "Turn Windows features on or off". Uncheck .NET Framework 3.5 and 4.8, restart the PC, and then re-enable them.

    Waiting for customer now to provide feedback but I'm not sure if this will solve the issue at hand as now updates were pushed to the client machines in this timeframe.

    Let's keep each other posted I would say :-)



    ------------------------------
    Domien De Cleyn
    na
    ------------------------------

    Original Message


  • 4.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 14 days ago

    Just got word back from my customer that this morning all returned to normal, everything is working again without changes on their end. So I would guess something changed on Genesys end.



    ------------------------------
    Domien De Cleyn
    ------------------------------

    Original Message


  • 5.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 13 days ago

    Today looks to be working again for us too, but it's too early to confirm everything is back to normal.

    I have been in contact with Microsoft who claim their platform has not changed recently. They advise to update everything and look to rearchitect our solution... very helpful.

    Seeing that this issue impacted various users, it would be great if Genesys Team could confirm if there were any issues/changes on their end.



    ------------------------------
    Carl Hansen
    ------------------------------

    Original Message


  • 6.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 13 days ago

    Carl, thank you for updating this thread. 

    Our issues also seem to be resolved, through no action of our own.

    I also would like to have a response from Genesys regarding this issue.  It's too much of a coincidence that all three of us had the same issue all starting on the same day.  And with all of us running on different platforms (Desktop app, Azure Function, Azure App Service), the main commonality is the Genesys NotificationHandler.



    ------------------------------
    Chris Anderson
    Senior Consultant
    ------------------------------

    Original Message


  • 7.  RE: NotificationHandler Exception - WebSocketSharp leads to System.PlatformNotSupportedException

    Posted 12 days ago

    This is from our Genesys intermediatory representative:

    Genesys has advised that the recent disruption was related to a deployment update involving the WebSocketSharp library used within their SDK. They have confirmed that a fix has been deployed, and services are expected to be restored.

    Wondering if Genesys will provide a direct update here or on their status page as an incident.

    Either way, guess all we can do is be thankful it's fixed and cross our fingers it doesn't happen again. :D



    ------------------------------
    Carl Hansen
    ------------------------------

    Original Message


Related Content