intercom / intercom-dotnet

Intercom API client library for .NET
https://developers.intercom.io/reference
Apache License 2.0
63 stars 54 forks source link

UsersClient.View returning null, not throwing an exception #140

Open mzammitkg opened 5 years ago

mzammitkg commented 5 years ago

As of this morning, the following call to UsersClient seems to be returning null:

var usersClient = new UsersClient(new Authentication(AccessToken));
var user = usersClient.View(new Intercom.Data.User() { user_id = user_id.ToString() });

There is no exception thrown, which will be a breaking change for many apps (including ours).

wil55n commented 5 years ago

Yes, we are experiencing the same issue as of today. Basically any userclient call is returning null. We are on version 1.0.31 of the SDK. If we update to 2.x of the SDK the call returns the correct data BUT we can not use 2.x right now because of the dependancy on .NET Standard

abentabet commented 5 years ago

The problem comes from the API and not the SDK, i've tried manual http request, it works by Id but not by userid, hope intercom fix that soon

abentabet commented 5 years ago

When using "ContactsClient.View" with .NET Framework 4.5.2 (same SDK version : 1.0.31) I have "null" but when using .NET Framework 4.7 it works ! ... we can't update .net framework because it impacts all our code

mortenmoulder commented 5 years ago

We're experiencing the exact same thing here. Works on 4.7.1 but not on 4.5.1. Using version 1.0.31.

I'm talking to Intercom as we speak. They are aware of the issue now, at least. Let's hope they fix this.

RebliNk17 commented 5 years ago

Working with 4.7.1 and still receiving null...

mortenmoulder commented 5 years ago

Seems like we have a temporary fix: .NET Framework 4.5 does not have TLS 1.2 enabled by default. If you set it, it should work for .NET Framework 4.5 applications as well.

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
sith30 commented 5 years ago

It works! Thx