Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

algosdk.signLogicSigTransactionObject does not work #484

Closed
soring323 opened this issue Dec 13, 2021 · 8 comments
Closed

algosdk.signLogicSigTransactionObject does not work #484

soring323 opened this issue Dec 13, 2021 · 8 comments
Labels
new-bug Bug report that needs triage

Comments

@soring323
Copy link

Subject of the issueimage

Your environment

algoSDK: 1.12.0
I'm working on solving this issue right now. I've just knew that this issue happened from algoSDK.
ulamlabs/OpenNFT#17

Here is screenshot.
in process, this part crash with this message.

image

image<!--

  • Software version: algod -v
  • Node status if applicable: goal node status
  • Operating System details.
  • In many cases log files and cadaver files are also useful to include. Since these files may be large, an Algorand developer may request them later. These files may include public addresses that you're participating with. If that is a concern please be sure to scrub that data.
    -->

Steps to reproduce

Expected behaviour

Actual behaviour

@soring323 soring323 added the new-bug Bug report that needs triage label Dec 13, 2021
@jasonpaulos
Copy link
Contributor

What type is tx.group? It should be a Uint8Array or Buffer.

@soring323
Copy link
Author

it is buffer right now.

@jasonpaulos
Copy link
Contributor

Please post an example of the contents of the tx.group buffer.

Additionally, where is the error being thrown?

@soring323
Copy link
Author

I've posted this on the discord channel.

@soring323
Copy link
Author

image

@soring323
Copy link
Author

image

@soring323
Copy link
Author

if that's possible, can we discuss on the algorand javascript sdk channel? I've asked many things to barnji there but did not solve this still.

@jasonpaulos
Copy link
Contributor

Closing this because I believe we fixed the problem on discord (wrong input for group ID hash)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-bug Bug report that needs triage
Projects
None yet
Development

No branches or pull requests

3 participants
@jasonpaulos @soring323 and others