Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mzammitkg opened this issue Oct 10, 2018 · 7 comments
Open

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

mzammitkg opened this issue Oct 10, 2018 · 7 comments
Labels

Comments

@mzammitkg
Copy link

mzammitkg commented Oct 10, 2018

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
Copy link

wil55n commented Oct 11, 2018

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
Copy link

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
Copy link

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
Copy link

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
Copy link

Working with 4.7.1 and still receiving null...

@mortenmoulder
Copy link

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
Copy link

sith30 commented Oct 12, 2018

It works! Thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants