You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
UsersClient.View returning null, not throwing an exception #140
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).
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
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
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.
Activity
wil55n commentedon 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 commentedon Oct 11, 2018
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 commentedon Oct 11, 2018
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 commentedon Oct 11, 2018
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 commentedon Oct 11, 2018
Working with 4.7.1 and still receiving null...
mortenmoulder commentedon Oct 11, 2018
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.
sith30 commentedon Oct 12, 2018
It works! Thx