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

Use executeAll() instead of execute() in FileCreate/Append transactions #2693

Closed
Ivo-Yankov opened this issue Jul 10, 2024 · 0 comments · Fixed by #2698
Closed

Use executeAll() instead of execute() in FileCreate/Append transactions #2693

Ivo-Yankov opened this issue Jul 10, 2024 · 0 comments · Fixed by #2698
Assignees
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@Ivo-Yankov
Copy link
Collaborator

Ivo-Yankov commented Jul 10, 2024

Description

When creating a file with FileCreateTransaction, multiple fileAppends can be performed internally by the sdk. When using execute() only the first transactionId is returned, while using executeAll() returns a list of all possible transactionsIds, which then need to be looped over to find the sum of all fees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: Done
3 participants