Activity feed / pending tx "speed up" has been broken for months

Description:

First reported back in August when you guys changed the order making the functionality useless. 4+ months later and it’s still not fixed!

The transaction that shows as “pending“ and can be sped up - is the last tx / highest nonce. Speeding this transaction up does absolutely nothing, because you still have an earlier transaction (!!!) stuck. That earlier transaction is what’s holding it back. That means that you can set up 10 ETH as you gas limit, but it still won’t go through. OBVIOUSLY!
It will only go through once the oldest transaction goes through - which means that you’re basically overpaying for gas on later transactions. FOR NO REASON. And you still cannot do anything about the transaction that’s actually stuck because the interface HAS NO OPTION FOR THE OLDEST TRANSACTIONS!!!

The transaction that shows as “queued“ is actually the earliest transaction/lowest nonce - the one that is actually ‘pending‘ and holding the later transactions back.
Speeding up this transaction is what you should do in case it’s stuck. BUT IT CANNOT BE SPED UP!!! THAT OPTION HAS BEEN REMOVED FROM THE INTERFACE MONTHS AGO.

The only thing you can do is manually resubmit the same transaction and manually select the nonce + add a higher gas limit. Either that or self-transact zero value to replace the transaction.

You guys changed this order months ago (IT USED TO WORK CORRECTLY!!!), got a detailed report about it, and haven’t managed to fix this MONTHS later.

I don’t think anyone at your company actually uses the product you’re working on. Seriously. How is anything passing quality control at MetaMask?

I don’t know who did the change back in August, but that person obviously has never used a wallet / never had to deal with stuck transactions. I don’t know WHY this hasn’t been fixed in the past 4+ months, it’s ridiculous.
That was one of the VERY FEW things that actually used to work properly. You reversed the order, making it useless, and haven’t bothered to actually fix it. IT’S BEEN MONTHS.

I said it before, and I’m going to say it again:

It doesn’t even make sense to actually bother reporting things because nothing is even getting fixed (!!!)

Background 'getState' call exceeded timeout

Has been a Chrome specific bricking issue for MONTHS now. It’s an endless brick-restart–brick loop. This “getState“ brick issue replaced the previous “No response from RPC” restart loop happening since 13.3 - we’re at 13.13.1 AND THIS SHIT IS STILL BRICKED.

Even if you do a clean browser install and setup MM again - IT WILL BRICK AGAIN.

SERIOUSLY, WHAT ARE YOU GUYS GETTING PAID FOR?

Please tell me if you already contacted the live chat support for MetaMask support to have the instructions on this situation