[BUG] Problem with parsing TX broadcast response

[LNow]

Every now and then after submitting transaction instead of proper success information I get an error like to the one below:

Broadcast error: "SyntaxError: Unexpected token b in JSON at position 1 - undefined"

Transactions are submitted successfully and they can be found in explorer.
This problem affects STX transfer transactions and contract calls.

Unfortunately I can't reproduce it at will.

Wallet version: v2.20.3
Browser: Firefox Nightly v94.0 (64-bit)

[LNow]

Another occurrence:

[egtalbot]

Similar error for me on both stackswap and arkadiko swaps
Broadcast error: "SyntaxError: Unexpected token a in JSON at position 2 - undefined"

Wallet version: 2.21.0
Browser: Brave V1.32.106

[aulneau]

I've also received this error in the desktop wallet

[314159265359879]

I have also seen this error when deploying contracts to mainnet using the explorer sandbox.

[obycode]

I just saw this error today as well. Not sure if these are related or helpful, but checked the console after seeing the error and found:

o204651.ingest.sentry.io/api/5963881/envelope/?sentry_key=XXXXXXXX&sentry_version=7:1 Failed to load resource: the server responded with a status of 429 ()
stacks-node-api.stacks.co/v2/transactions:1 Failed to load resource: the server responded with a status of 524 ()
stacks-node-api.stacks.co/extended/v1/address/XXXXXXXXXXX/balances:1 Failed to load resource: the server responded with a status of 524 ()

[obycode]

Interestingly, it does appear that the transaction did go through, despite this error.

[egtalbot]

I just saw this error today as well. Not sure if these are related or helpful, but checked the console after seeing the error and found:

o204651.ingest.sentry.io/api/5963881/envelope/?sentry_key=XXXXXXXX&sentry_version=7:1 Failed to load resource: the server responded with a status of 429 ()
stacks-node-api.stacks.co/v2/transactions:1 Failed to load resource: the server responded with a status of 524 ()
stacks-node-api.stacks.co/extended/v1/address/XXXXXXXXXXX/balances:1 Failed to load resource: the server responded with a status of 524 ()

Without looking at the code, I would think those would be errors from after the transaction is posted

[BowTiedMooneeb]

I can confirm that these broadcast errors occur frequently when executing CityCoins mining operations over at syvitamining.com. In almost all cases, the transaction actually goes through and shows up in the mempool.

This is a particularly impactful problem when MiamiCoin mining pool participants are submitting STX to the smart contract for mining. We do not have the ability to send STX back from the smart contract, so if someone thinks their transaction failed and they submit it again, they might unintentionally send in twice the amount they intended, which is unfortunately an irrevocable transaction.

[markmhendrickson]

I'm closing and will reopen upon receipt of further reports.