DEVNET - Token Unknow and couldn't fetch network fee

[BlumpSol]

Summary

I can't get the transaction fees or the token name when testing on DEVNET (I've been testing for several days).

Example

No response

Steps to Reproduce

Hi,
I can't get the transaction fees or the token name when testing on DEVNET (I've been testing for several days). However, the transaction is correct and sent when I click on confirm.
I tested with a spl token created on the DEVNET network but also with USDC DEVNET. Always the same result.
Can anyone tell me more about this?

Thx !

Phantom Version

24.11.0

Is there an existing discussion for this?

• I have searched the existing discussions

[adamdelphantom]

Hello @BlumpSol,

We are investigating an issue with simulation and fee estimation on devnet.

[elemanhillary]

Same issue here.

[wmemon]

Hi, did anyone find the error? I have been facing the same issue..

[Slitthe]

Any updates on this? I'm also getting this error

[elemanhillary]

Mine worked with custom RPC url

[adamdelphantom]

Fix on this issue should be available in the coming weeks. Thanks for everyone's patience!

@BlumpSol @elemanhillary @Slitthe @wmemon

[Harushii18]

This occurs on testnet as well, just to add to it @adamdelphantom

[salmandayal]

Facing the same issue. Are you facing the same issue on the mainnet as well with your custom contract? @Harushii18 @Slitthe

[adamdelphantom]

Hey @salmandayal,

This specific issue is isolated to devnet. If you're seeing this on main net please start a new thread with all relevant info, so we can try to help.

[Harushii18]

Haven't been able to test with mainnet, only testnet and devnet. This happens for both networks on the phantom desktop extension for me. I'm using solana wallet adapter to trigger the extension to pop up, and the payment goes through however it does as the earlier screenshot posted shows: does not want to show the network fee and gives that warning that the transaction may fail.

[geoshak]

Similar issue here.

[adamdelphantom]

@BlumpSol @elemanhillary @wmemon @Slitthe @Harushii18 @geoshak Thanks for your patience. This should be resolved on version 24.19. Please let me know if not.

[Harushii18]

Thank you for your prompt responses!

[tony-yyj]

still facing the same issue
Phantom version: 24.19

[adamdelphantom]

@tony-yyj What network is this on, please?

[tony-yyj]

devnet

[adamdelphantom]

@tony-yyj, Would you mind providing some of your code, please? Our sandboxes example app which was previously exhibiting the same error is now working.