populateAppCallResources inconsistent transaction composition

[Kozer4]

Problem

Problem in:
populateAppCallResources from @algorandfoundation/algokit-utils

inside:
executionInfo.groupUnnamedResourcesAccessed (boxes, accounts, etc.)
in a different order on each run — apparently as a result of simulation.

This leads to non-deterministic behavior, which in turn causes:

• inconsistent transaction composition,
• and potential failures when resource limits depend on order.

Solution

Resources (boxes, accounts, assets, apps) should be returned(or used in population) in a deterministic order to ensure reproducibility.

Proposal

Resources (boxes, accounts, assets, apps) should be returned(or used in population) in a deterministic order to ensure reproducibility.

Pros and Cons

Pros: deterministic behavior, reproducible simulations, stable tests.
Cons: maybe slight performance overhead

Dependencies

Maybe No external dependencies.

[joe-p]

The non-deterministic behavior was addressed in #443. If you run into failures with this change, I recommend creating a new ticket. I imagine the solution at that point would be some sort of retry mechanism that uses a different order.