stellar-ios-mac-sdk: Error on parsing payment operation's response

Payment operation’s response is not getting parsed. This used to work, so there might something changed on Horizon APIs. Tested with 1.1.5.

Error description:

HorizonRequestError: parsingResponseFailed : “The operation couldn’t be completed. (stellarsdk.XDRDecoder.Error error 6.)”

User code:

var memo: Memo

if let memoID = memoID {
    memo = Memo.id(memoID)
} else {
    memo = Memo.none
}

let paymentOperation = PaymentOperation(sourceAccount: keyPair, destination: try KeyPair(accountId: destinationAccountID), asset: asset, amount: amount)
let transaction = try Transaction(sourceAccount: accountResponse, operations: [paymentOperation], memo: memo, timeBounds: nil)
try transaction.sign(keyPair: keyPair, network: MPConfig.STELLAR_NETORK)
try StellarSDK(withHorizonUrl: MPConfig.URL_HORIZON).transactions.submitTransaction(transaction: transaction) { (transactionPostResponse) -> (Void) in
    
    switch transactionPostResponse {
//                    case .success(let submitTransactionResponse):
    case .success(_):
        fulfill(())
    case .failure(let horizonRequestError):
        reject(horizonRequestError)
    }
    
}

Response: { “_links”: { “transaction”: { “href”: “https://horizon-testnet.stellar.org/transactions/89e43763c72331af432fb3db241b723e82370e0802d4a17c5c32d6284a9124d2” } }, “hash”: “89e43763c72331af432fb3db241b723e82370e0802d4a17c5c32d6284a9124d2”, “ledger”: 10642164, “envelope_xdr”: “AAAAAN1u4nbfMpcFr71wNt1ViTlk/hS59jD0pMcyXzm3pfBFAAAAZACdq+gAAAARAAAAAAAAAAAAAAABAAAAAQAAAADdbuJ23zKXBa+9cDbdVYk5ZP4UufYw9KTHMl85t6XwRQAAAAEAAAAAv3PZYYqz1lB5qjK5R7Kn7MyHfHTIYxjTLqqSYEtjQ7QAAAABT0cAAAAAAAB8CTr1M3808ueF/pik9o3XLuo85lEv/PQVDVgGdMxkxAAAAAABCGO3AAAAAAAAAAG3pfBFAAAAQOTIsPSPYGnyrvEwGfsLChKiddgrA3YOf8ayHZr4tCavUXLRHh3UgxG3ncoiqDIY7sFTME+5pt9gAoKwLb7WnQo=”, “result_xdr”: “AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=”, “result_meta_xdr”: “AAAAAQAAAAIAAAADAKJi9AAAAAAAAAAA3W7idt8ylwWvvXA23VWJOWT+FLn2MPSkxzJfObel8EUAAAAA2F1ihgCdq+gAAAAQAAAAAQAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAKJi9AAAAAAAAAAA3W7idt8ylwWvvXA23VWJOWT+FLn2MPSkxzJfObel8EUAAAAA2F1ihgCdq+gAAAARAAAAAQAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMAomLmAAAAAQAAAAC/c9lhirPWUHmqMrlHsqfszId8dMhjGNMuqpJgS2NDtAAAAAFPRwAAAAAAAHwJOvUzfzTy54X+mKT2jdcu6jzmUS/89BUNWAZ0zGTEAAAAGuuJGGAG8FtZ07IAAAAAAAEAAAAAAAAAAAAAAAEAomL0AAAAAQAAAAC/c9lhirPWUHmqMrlHsqfszId8dMhjGNMuqpJgS2NDtAAAAAFPRwAAAAAAAHwJOvUzfzTy54X+mKT2jdcu6jzmUS/89BUNWAZ0zGTEAAAAGuyRfBcG8FtZ07IAAAAAAAEAAAAAAAAAAAAAAAMAomLmAAAAAQAAAADdbuJ23zKXBa+9cDbdVYk5ZP4UufYw9KTHMl85t6XwRQAAAAFPRwAAAAAAAHwJOvUzfzTy54X+mKT2jdcu6jzmUS/89BUNWAZ0zGTEAAAAEqAibDYCf30L25IAAAAAAAEAAAAAAAAAAAAAAAEAomL0AAAAAQAAAADdbuJ23zKXBa+9cDbdVYk5ZP4UufYw9KTHMl85t6XwRQAAAAFPRwAAAAAAAHwJOvUzfzTy54X+mKT2jdcu6jzmUS/89BUNWAZ0zGTEAAAAEp8aCH8Cf30L25IAAAAAAAEAAAAAAAAAAA==” }

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 16 (7 by maintainers)

Most upvoted comments

This should be fixed in 1.4.1