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

Incorrect Target Account Result Returned When Executing hedera_signAndExecuteQuery on https://wc.hgraph.app/ #119

Open
soharang opened this issue Apr 22, 2024 · 0 comments
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone.

Comments

@soharang
Copy link

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'https://wc.hgraph.app/'
  2. Input necessary field and process "Initialize WalletConnect" for both "dApp" and "Wallet" on the page.
  3. Connet dApp to Wallet
  4. Input necessary field as following and proceed "4. hedera_signAndExecuteQuery".
    • Account ID: 0.0.398606
    • Payment account id: the account connected to dApp from the wallet as a signer.
  5. Proceed request and check the query result.

Expected behavior A clear and concise description of what you expected to happen.
The account for the result from the query should be the account Id in the field named "Account ID", in this case, 0.0.398606.

Screenshots If applicable, add screenshots to help explain your problem.
The account for the result from the query is the payment account Id in the field named "Payment account id", in this case.
image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context Add any other context about the problem here.

@itsbrandondev itsbrandondev added Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone. labels Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone.
Projects
None yet
Development

No branches or pull requests

2 participants