1

I've been using stellar-dotnet-sdk for months; today, I get an error while trying to instantiate an AccountResponse object. AccountResponse.cs, line 147 (AccountId = accountId ?? throw new ArgumentNullException(nameof(accountId), "accountId cannot be null");). My code hasn't changed - I see this error when hitting both the Test and Prod network.

Something is happening while it is trying to parse the JSON returned from horizon-testnet.stellar.org/accounts/…. As I step through the code, the returned JSON looks fine - but the accountID being passed into the Signer object constructor is null (haven't stepped back further to see the root of all of this).

Any ideas?

3

You must update your SDK since we didn't have support for horizon 0.17.0 that was released 2 / 3 days ago.

Also with the new SDK you should use keyPair.AccountId instead of only keyPair.

Apologies, let us know if that works for you.

| improve this answer | |
  • Thanks - that looks to be it. I went ahead and download/compiled latest source, will wait for Nuget package to be released at some point in the future. – tylerc Mar 1 '19 at 17:51
  • 1
    Latest NuGet is out, I also changed how we release. I use to manually deploy NuGet, now NuGet package is built from master source and immediately deployed so you won't have to build from source again. Sorry about that pain there I hope doing it this way alleviates it in future. – emalamisura Mar 5 '19 at 22:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.