Unable to confirm transaction request on devnet

[Aman-zishan]

unable to confirm transaction, gets a fee estimation error in extension console

• browser - chrome
• network - devnet
• contract call used to work until yesterday noon

[314159265359879]

Hi @Aman-zishan this looks a lot like your extension and dapp are not connecting to the same network. Try signing out on the dapp. Setting your extension to the devnet and selecting the account you want to sign in with.
Then connect to the dapp again, and try to confirm the transaction again.

[Aman-zishan]

Hi @314159265359879 , i followed your steps and i'm getting the same error, i am using micro-stacks in most of my contract calls, so im setting the network directly then and i also checked if it is pointing to the right network. seems like it is, the dapp network switch is working fine as i tried with testnet as selected network option and wallet shows testnet in the confirmation page. Although i did not check if the tx is being confirmed in testnet / mainnet and if this is an issue with only the devnet

[314159265359879]

@Aman-zishan does the wallet still allow you to proceed with a custom fee?

[Aman-zishan]

@314159265359879
this is the screen

[314159265359879]

@kyranjamie we expect the fee options to still appear, when fee can't be determined, right? so the user can at least set a custom fee or is that different when operating on devnet?

I guess if none of the devnet API's can be reached it will not matter much because then the wallet will error on "insufficient balance to cover fees" next.

[Aman-zishan]

@kyranjamie we expect the fee options to still appear, when fee can't be determined, right? so the user can at least set a custom fee or is that different when operating on devnet?

I guess if none of the devnet API's can be reached it will not matter much because then the wallet will error on "insufficient balance to cover fees" next.

@314159265359879 i agree on this, in given scenario a fee field could make matters much easier rather than a dead end, how can i fix this issues i have been stuck at this and cannot proceed with my development

[314159265359879]

I am not sure how to resolve this.
@Aman-zishan can you work around this issue by using the public Hiro testnet instead?

[Aman-zishan]

@314159265359879 testnet is extremely slow for vigorous development flow atleast for now, so unless i have developed the entire flow i dont think testing via testnet is a great idea, that's why devnet development was much easier for such development practices, at this point we particularly depends on devnet

[obycode]

I have seen this issue as well. As a workaround, I have been submitting transactions via stacks.js instead of through the wallet, for my testing.

[ryanwaits]

I have seen this issue as well. As a workaround, I have been submitting transactions via stacks.js instead of through the wallet, for my testing.

im starting to get this error when using stacks.js as a workaround

[natebuch]

Experiencing the same issues. Confirmation window has sBTC devenv selected and unable to change. Extension is set to devnet.

[sabbyanandan]

@markmhendrickson: At your convenience, please have a look at this. Any education would be helpful.

[obycode]

im starting to get this error when using stacks.js as a workaround

In stacks.js, you can hard-code a fee in the options object so that it doesn't rely on the fee estimation endpoint.

[sabbyanandan]

@fbwoolf: Thank you for the fix!

@Aman-zishan: Perhaps you can try out the extension built off of the PR and share your findings here or in the PR for validation.

[Aman-zishan]

@sabbyanandan the fix works well thanks!, thank you for the fix @fbwoolf , i'll keep an eye here to see when it is going to be merged so that i can switch to production version

[fbwoolf]

Merging this into our dev branch today, but we still need to release it to the app stores. Watch for the new release for the fix.