We are developing an WinRT, Windows Phone 8.1 app and are using the TElHTTPSClient for posting data to our backend via SecureBlackBox.

However, about 1 in 10 calls result in a NullReferenceException located at SBSocket.TElSocket.HandleRecvCompleted.

We started out using your Async libraries to use PostAsync on the TElHTTPSClient, however this resulted in 7 in 10 calls to execute badly and throwing the NullReferenceException.

So switching to the default synchronous implementation was an improvement, but still the problem persists.

Could you please look into this ? This is crucial for the performance and reliability of our app.

We'd also like to point out that the implementation of your Async libraries are useless in large sequential network calls.
Since these just wrap the sync calls in a Task.Factory.Run awaitable Task.
We strongly recommend you to refactor your Async libraries.

I believe we've managed to localize the NullReferenceException issue and are working on a solution at the moment. The patch will go to the next SecureBlackbox product update, which is going to be released within three weeks.

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.