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

Invalid JSON filename on multisignature registration transaction save #3787

Closed
MichalTuleja opened this issue Sep 14, 2021 · 0 comments
Closed
Assignees
Milestone

Comments

@MichalTuleja
Copy link
Contributor

MichalTuleja commented Sep 14, 2021

Expected behavior

The filename should follow a pattern: tx-<transaction_id>.json.

Actual behavior

The proposed JSON filename is always tx-undefined.json on transaction save.

Steps to reproduce

  1. Sign-in as a regular (non-multisig) account.
  2. Create a multisig account and download the transaction in the JSON format.

Which version(s) does this affect? (Environment, OS, etc...)

2.0.1

@ManuGowda ManuGowda assigned isalga and ManuGowda and unassigned isalga Sep 15, 2021
@sridharmeganathan sridharmeganathan added this to the Sprint 58 milestone Sep 15, 2021
ManuGowda added a commit that referenced this issue Sep 16, 2021
Invalid JSON filename on multisignature registration transaction save - Closes #3787
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants