Bug: Dispatch sometimes crashes when falling back to BASE

[Silanael]

Calling window.arweaveWallet.dispatch frequently crashes with an uncaught "r.every is not a function" error when falling back to base layer. When this happens, the transaction is posted but the data it contains isn't, potentially leading to financial loss if an upload of a large file fails.

This fault was observed when using Wander 1.29.1 and arweave-js from https://unpkg.com/arweave@1.15.5/bundles/web.bundle.js on Chromium 136.0.7103.113 with gateway https://arweave.net:443 and bundler https://turbo.ardrive.io set in Wander, running the code from a local python3 web server (python3 -m http.server) on an address that has sufficient AR-balance but (presumably) no bundler-balance, and 'transaction.data' was set to the result of 'await file.arrayBuffer ();'.

The issue seems to only affect base layer transactions (ones larger than 100KB that the bundler doesn't do for free) - dispatch appears to work for small files that it's able to bundle. Prior to crashing, it presents the sign transaction -dialog for the same transaction twice.

Sample transactions:

W-ndNkSjaKoVIVFDGvwKKlu8kuLR2zh4QU0SvxxLBx4
tM0hSCCIUCDPISNltWY6fzjE5um0Cy4IQA5G0Zjhn7Q
8L4dxLUlPxjQ7YKrydrQM3ZBUskSVU7r4dYOpVahU_8

[t8]

Thanks for reporting this @Silanael. We will take a look!

[Silanael]

When it displays the sign transaction dialog twice, it first asks signature for an empty transaction, then for the actual one immediately after accepting the first, posting the transaction as BASE when not crashing even when the data is smaller than 100KiB. This seems to be related to the issue.