Strange error while using my Trezor wallet with the RBF feature on Suite

[SFR10]

A few days back, I was exploring Trezor Suite's other features that I don't normally use ^{[e.g. exchanges and etc...]}; while I was messing around, I thought it's probably a good time to test its RBF feature as well, so intentionally, I sent a low fee transaction and after a few minutes, I proceed to choose its fee type. I clicked "Custom" ^{[instead of normal or high]}, and it gave me the following error ^[screenshot]:

Code:

cannot read property 'type' of undefined

• After that error popped out, I closed Suite > reopened > did everything exactly the same, but this time there was no error!
  ^{- I've tried my best to recreate that error, so I could report it [I know I should've done it in the first place], but had no luck.}

Does anybody know what this error is about?
^{- I've already googled and searched on their "forum", but no one seems to have encountered that error for using the RBF feature [AFAICS].}

[dkbit98]

Fees for Bitcoin have been low in recent months so I didn't have problem with sending transactions, even now it's only 1 sat/vB.
I am using Electrum in combination with Trezor so I didn't have a chance to test it myself in Trezor Suite, but you can follow instructions from their wiki page, just make sure you have latest software and firmware version:
https://wiki.trezor.io/Replace-by-fee_(RBF)

There is one RBF sending bug reported yesterday on their github page, I don't know if this is you:
https://github.com/trezor/trezor-suite/issues/4223

One more thing I don't like with Trezor Suite is that I am not able to generate new address if previous one was not used :/ so I just use Electrum.

[SFR10]

Fees for Bitcoin have been low in recent months so I didn't have problem with sending transactions, even now it's only 1 sat/vB.

I did my test on the first of September ^{["fees rose" a little bit on that day and despite that still being considered as a low fee, I intentionally used an even lower fee]}.

just make sure you have latest software and firmware version:

Yes, I always do

There is one RBF sending bug reported yesterday on their github page, I don't know if this is you:
https://github.com/trezor/trezor-suite/issues/4223

No, that wasn't me... Mine had a different type of error, but no matter what I do, I can't reproduce it.

One more thing I don't like with Trezor Suite is that I am not able to generate new address if previous one was not used :/ so I just use Electrum.

Perhaps that was the case when they first released it but at the moment, you can generate multiple addresses without having to use the previous ones ^[screenshot].

Update:

For your RBF issue you can send them feedback directly from wallet or you can create issue on their github page.

Just finished reporting it through the Trezor Suite. I'll update this thread if anything changes

[dkbit98]

Perhaps that was the case when they first released it but at the moment, you can generate multiple addresses without having to use the previous ones ^[screenshot].

Yeah it looks like they fixed it finally, I just generated few addresses for testing, and I can confirm it's working just fine now.

For your RBF issue you can send them feedback directly from wallet or you can create issue on their github page.

[Pmalek]

Seems like it's a common error that not only affects Trezor when there are issues with imperfect code. Take a look at this thread back from 2017:
https://github.com/trezor-graveyard/trezor-chrome-extension/issues/12

The user explained how he got the same type of error when he was attempting to restore his wallet from seed. That error was fixed within a few days and it was no longer happening in the newer versions.

[SFR10]

For your RBF issue you can send them feedback directly from wallet or you can create issue on their github page.

Since I didn't know my way around GitHub, I went with the former ^{[as stated in my previous update]}... Am I supposed to wait until they get back to me through the Trezor Suite ^{[a notification of some sort]} or I should do something else?
^{- It has been more than 24 hours since I've reported it as a bug and it didn't give me anything to follow up on.}

Seems like it's a common error that not only affects Trezor when there are issues with imperfect code. Take a look at this thread back from 2017:
https://github.com/trezor-graveyard/trezor-chrome-extension/issues/12

Thank you, you're right ^{[it's a common error (in general)]}... I've also seen that report prior to creating this thread yesterday and since it doesn't involve the Trezor Suite and the RBF feature, then perhaps something else might've caused it.