Locked amount doesn't update in Extension and Desktop wallet, after unlocking

[314159265359879]

This address has had their STX unlocked after revoking the delegation 9 days ago but it still shows locked, it is expected to show unlocked and be transferable:
On the explorer the funds lock unlocked (as expected)
https://explorer.hiro.so/address/SP24FTYJV6N2XG5SVQPY4DHMC2DECGDAV2BRVPY0Y?chain=mainnet

API shows them unlocked too: https://stacks-node-api.mainnet.stacks.co/extended/v1/address/SP24FTYJV6N2XG5SVQPY4DHMC2DECGDAV2BRVPY0Y/balances

**locked | "0"**
lock_height | 0
burnchain_lock_height | 0
burnchain_unlock_height | 0
estimated_balance | "181369431823"

I would expect to see all the balance unlocked in the wallet too, but the user sees this in their wallet
Extension wallet (6.52.0) and desktop wallet.

The user can't send their funds because they are still registered as locked:

Desktop wallet version 4.15.1

I am trying to get console logs from the user to check for networking issues. If there was a networking issue, though, I would expect the wallet to show that the balance can't be determined, not show outdated info.

[linear]

LEA-1727 Locked amount doesn't update in Extension and Desktop wallet, after unlocking

[kyranjamie]

Can we verify whether this is an API issue or not?

[314159265359879]

The user has confirmed that they resolved it by using another computer and browser but I have not been able to determine if this is an API issue and/or connection issue or not.

[314159265359879]

No console logs from the same state. when the old data was shown and it wasn't properly updated.

They made this after sending out STX with the other computer/browser. Now the balance is updated normally (0STX is correct).

perhaps the displayed errors are helpful anyway.

[camerow]

This seems like a p2/p1 level issue, no? @kyranjamie can you help me decide on how much to prioritize this? Is it worth taking someone off what they are doing or can we push it to a future cycle?

[kyranjamie]

I am not really sure where to start here. All of this data is inferred from the one API endpoint. If this one user solved the issue, and we've had no other reports, I would hold off before investing time in it.

[314159265359879]

Linking the desktop issue here, we saw the same thing there. leather-io/desktop#1274

[314159265359879]

An other issue like this today, on the extension. The user has tried refreshing/clearing cache, reinstalling the wallet and restoring it but nothing works.

When I check the address on the explorer the funds are unlocked. The user also expects to see them unlocked in Leather, but they they remain locked.

In their wallet they still look locked. Well beyond the start of cycle 99.

The only thing I can think of is that the wallet is getting data from an outdated node. How do we check or verify that?
Is there anything else that could be causing this?

[314159265359879]

One user mentioned working around the issue installing Leather on another browser, where the locked balance status did update as expected.

[markmhendrickson]

@camerow should @alter-eggo perhaps investigate this cycle?

[camerow]

Yeah, @alter-eggo can you hop on this?

[alter-eggo]

yeah, once finish rpc send transfer

[markmhendrickson]

@alter-eggo can you jump on this now?

[alter-eggo]

guys, not sure where is the problem here tbh. stx balance data become stale each minute in the wallet, so seems cache is not a problem. and as I understand user even reinstalled the wallet.

explorer uses the same endpoint as wallet to fetch balances: https://api.hiro.so/extended/v1/address/