Key Error when calling polkadot.js api balances.transfer

[edwardmack]

Describe the bug

• Using polkadot/api (v4.6.2) calling const transfer = await api.tx.balances.transfer(bobKey.address, 12345).signAndSend(aliceKey); causes error:

Error: Detected -Infinity in Keys, should be >= 2 and <= 11
    at assert (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/@polkadot/util/assert.cjs:34:11)
    at mapCapabilities (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/@polkadot/api/base/capabilities.cjs:52:24)
    at MapSubscriber.project (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/@polkadot/api/base/capabilities.cjs:118:555)
    at MapSubscriber._next (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/operators/map.js:49:35)
    at MapSubscriber.Subscriber.next (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/Subscriber.js:66:18)
    at CombineLatestSubscriber.notifyNext (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/observable/combineLatest.js:97:34)
    at InnerSubscriber._next (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/InnerSubscriber.js:28:21)
    at InnerSubscriber.Subscriber.next (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/Subscriber.js:66:18)
    at CombineLatestSubscriber.notifyNext (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/observable/combineLatest.js:97:34)
    at InnerSubscriber._next (/home/emack/projects/chainsafe/gossamer/tests/polkadotjs_test/node_modules/rxjs/internal/InnerSubscriber.js:28:21)

• It seems that the transaction still completes.
• signAndSend is a multi part call, so need to determine what is causing the key error.
• Some transactions fail with error failed to validate signatures, this may be related.

Expected Behavior

• Call should not cause error.

Current Behavior

Possible Solution

To Reproduce

Steps to reproduce the behavior:

Log output

Log Output

paste log output...

Specification

• go version:
• gossamer version:
• gossamer commit tag:
• gossamer commit hash:
• operating system:
• additional links: