Error: Error creating IDL account: invalid type: map, expected a string

[Yolley]

Whenever I try to run anchor idl init on mainnet I get an error:

Error creating IDL account: invalid type: map, expected a string. Retrying...
Error creating IDL account: invalid type: map, expected a string. Retrying...
Error creating IDL account: invalid type: map, expected a string. Retrying...
Error creating IDL account: invalid type: map, expected a string. Retrying...
Error: Error creating IDL account: invalid type: map, expected a string

It repeats the same error several times until eventually it stops retrying. On the blockchain I see that IDL account was created, but it seems that Anchor failed to write the actual IDL to the account. On devnet the very same IDL works correctly.

Versions:

anchor-cli 0.30.1
solana-cli 1.18.23 (src:aeb3a2e1; feat:4215500110, client:SolanaLabs)
rustc 1.81.0 (eeb90cda1 2024-09-04)

[Yolley]

It seems like an issue when using the default RPC, I managed to reproduce the same issue with solana program write-buffer - and mitigated it by providing a custom RPC node url with --url parameter. I guess I just need to figure out now how to provide a custom cluster url to anchor idl init.

[acheroncrypto]

On devnet the very same IDL works correctly.

There is no specific implementation based on the cluster for the idl init command.

It seems like an issue when using the default RPC, I managed to reproduce the same issue with solana program write-buffer - and mitigated it by providing a custom RPC node url with --url parameter. I guess I just need to figure out now how to provide a custom cluster url to anchor idl init.

You can either set the [provider.cluster] value in Anchor.toml or pass in --provider.cluster.

[Yolley]

For some strange reason when I try to supply a custom RPC node (tried triton and shyft) I get this

Error creating IDL account: RPC response error -32002: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x0 [7 log messages]. Retrying...

Are you sure that just providing a custom URL in provider.cluster is enough? The same RPC urls works correctly with solana cli.