cinder pulsar
I get TypeError: Cannot read properties of undefined (reading 'switch') when trying to sign a transaction with my generated bindings. I appended the decoded xdr. Tested it in Labratory, looks fine.
operations.auth.credentials is set in xdr but getCredentials in stellar-sdk seems to return undefined and afterwards switch() is called and result in error
median quiver
XDR has been updated in p22, are you using the most recent SDK version?
dapper parcel
Do you generate the bindings with stellar cli? If so is that on v22?
I got the same TypeError as I was running on 22.0.0-rc.1
switching to 22.0.0 stable fixed it
dapper parcel
also the bindings newly generated with the new version
I should open my eyes, but I'll keep it here if it helps someone else 😛
cinder pulsar
Do you generate the bindings with stellar cli? If so is that on v22?
I regenerated with v22 but the error remains. Did u adjust anything in the signTransaction parameters?
Something seems to be still missing when i sign xdr
cinder pulsar
It's weird that signTransaction even returns signerAddress, which is my publicKey but then can't get credentials internally
cinder pulsar
I'm wondering if the operations.auth.credentials: "source_account" refers to tx.source_account (which is set) or operations.source_account (which is null)
median quiver
it 'refers' to the source account of the operation, but the protocol considers the operation source account to be equivalent to the tx source account in case if operation source account is not set (null). however, that's nothing to do with the XDR decoding and with protocol 22.
unfortunately I can't help with js issues though
robust gust
What Node version? I saw this start popping up in v22 for some reason but haven't had time to investigate.
cinder pulsar
What Node version? I saw this start popping up in v22 for some reason but haven'...
I'm using node v23.1.0
robust gust
Can you try v20?
cinder pulsar
Can you try v20?
Tested with v20.9.0, error still persists
sly burrow
What Node version? I saw this start popping up in v22 for some reason but haven'...
Is there an issue tracking the bug, or an effort to investigate this issue happening now? cc @loud token @timber plank
Are these the same issue as the issue being discussed here?