First what is StellarSDKError 0?

Second, how did you find the answer? As far as I can see, error documentation is basically nonexistent:


How is it logical for Stellar to return error codes without documentation so developers can figure out why code fails?

  • 2
    What about posting here the code sample that caused an error, and detailed error stack trace? Which SDK are you using (JS, Go, .Net)? Code 0 clearly stands for an unhanded internal error. – Orbit Lens May 22 '18 at 23:13
  • Yes, please add more detail. Sample code will be especially helpful. – Synesso May 22 '18 at 23:49
  • Sample code lets others help you out. Or you may try to figure out what went wrong by searching Stellar repository on Github with the exact error message. – cesarm May 23 '18 at 1:23
  • Thanks for the replies. I'm using the iOS SDK. The error occurred because I wasn't signing the transaction with the secret seed (tried to generate keypair from public key). I was able to catch this in Xcode. I'm not sure how code 0 "clearly" stands for an unhandled internal error. If stellar returns numeric codes for error, why isn't there a table in the documentation to look up the number & find the associated error? – WhyDoTheErrorDocsSuck May 23 '18 at 2:53
  • iOS SDK is created and supported by the community, not the Stellar Developer Foundation itself.So you should address your question to the maintainers. In all systems and frameworks I've been working with, there is a standard approach for numeric error codes. Meaningful error codes start at least with 1 (in some systems with arbitrary numbers like 1000 or 105, it doesn't matter) and have some basic description. If you see 0 and a vague error description, then it means that system/framework/module couldn't process that specific error, that's an unhandled error. – Orbit Lens May 23 '18 at 7:14

Browse other questions tagged or ask your own question.