Closed ihijazi closed 1 month ago
Fixed it by adding headers manually for authorization.
Weird thing it used to work fine with just setting AccessToken.
Also documentation doesn't mention this.
Here is what I did:
var appConfig = new Configuration();
appConfig.BasePath = oneSignalApiUrl;
//appConfig.AccessToken = oneSignalAccessToken;
appConfig.DefaultHeaders.Add("Authorization", "Basic " + oneSignalAccessToken);
Closing this.
What happened?
I'm using the latest .NET SDK, version 2.0.2. The DeleteUser was working fine (and still), but recently it's giving an excpetion.
Notes:
This problem just started to happen, nothing changed really from our end.
Can you please advise on what might be wrong here?
Steps to reproduce?
Code of Conduct