Address shows no Urbit IDs after L1 planet spawn to own address

[tinnus-napbus]

Describe the bug
While connected to Bridge with Metamask which itself was connected to my Trezor HW wallet, I spawned an L1 planet from one of my stars and specified "use my address" for the target eth address. Upon completion I returned to "home" where it lists my IDs and saw the new planet wasn't there. I logged out and logged back in and it said there were no IDs in my account at all, despite there being over 70. It also showed no transactions in history.

Logging out & in again didn't work. Incognito mode didn't work. Clearing all browser history and data didn't work. Unplugging & replugging the trezor didn't work. Switching to an entirely different browser didn't work. Uninstalling & Reinstalling Metamask and reconfiguring it from scratch didn't work.

Some time later (maybe an hour or more) after the millionth trezor replug & relogin attempt it randomly started working again.

To Reproduce
Don't know if it's reproducible but:

1. Login with Metamask & Trezor wallet
2. Got to a star
3. Spawn an L1 planet, setting self eth address as target
4. Go back to home, look at list of IDs, see new spawned one's not there
5. logout then log back in again
6. See that it appears you have no IDs in your wallet

Expected behavior
The newly spawned planet should have appeared in the list of IDs in the first place, but more importantly it should not have shown there were no IDs in the wallet after logout/login.

Screenshots

There was this error in the console, idk if it's related:

Desktop (please complete the following information):

• OS: Arch Linux
• Browser: It initially happened in Chromium but persisted when I switched to Firefox too. I was using Metamask in both browsers, connected to a Trezor HW wallet.

Login method (please complete the following information):
How you were logged into bridge when the error occured: Metamask /w Trezor HW wallet.

What Ethereum address were you logged in with: 0xe2e765fA00584cD787dC184019FAe071a63c6E50

Additional context
@thelifeandtimes has also encountered this error before

[thelifeandtimes]

For context from my end, I had this error on Desktop, MacOS using Brave and connecting a Ledger via Metamask. I have heard rumors of this happening to others so it is doubtful that it is an OS/Browser/Extension/Wallet related issue.

[thelifeandtimes]

I get a similar issue in the console. Screenshot above.