[BUG] Dapper Wallet problems with Newer Releases

[jacob-tucker]

Current Behavior

When I go to execute a multi-signed transaction with Dapper Wallet, I get the following error using @onflow/fcl 1.9.0:

However will older releases like 1.0.1, it works totally fine.
This is the transnaction I'm running:

import EmeraldIdentityDapper from 0x39e42c67cc851cfb

    transaction(discordID: String) {
        prepare(admin: AuthAccount, user: AuthAccount) {
            let administrator = admin.borrow<&EmeraldIdentityDapper.Administrator>(from: EmeraldIdentityDapper.AdministratorStoragePath)
                                        ?? panic("Could not borrow the administrator")
            administrator.createEmeraldID(account: user.address, discordID: discordID)
        }

        execute {
            log("Created EmeraldID")
        }
    }

It's a multi-signed transaction where the DW user signs as well as a backend admin.

Expected Behavior

No error

Steps To Reproduce

Run a multi-signed transaction using @onflow/fcl 1.9.0

Environment

- OS: Mac
- Node: 18.18.0
- npm: 9.8.1

What are you currently working on that this is blocking?

No response

[jimwheaton]

I'm also encountering this error. My project uses @onflow/fcl@1.3.2, which will install @onflow/sdk@1.5.1. It seems like a change in @onflow/sdk is causing the issue. When I step through the code, FCL does not call the custom authorization function during the pre-authz phase, so it does not send over the authorizer address (from the custom authz function) to Dapper Wallet. Dapper Wallet will then error on the authz phase with expected 2 authorizers, but got 3.

This issue does not occur with @onflow/sdk@1.2.2. To workaround this, I used npm overrides to restrict @onflow/sdk to 1.2.2.

example in package.json:

"overrides": {
  "@onflow/sdk": "1.2.2"
}