I was trying to be precise since we are dealing with 'money'.
One or two satoshis may not seem much now but may worth much more in the future.
Beside, the code is pretty simple once we are clear about the structure of a tx.

will not be needed after we introduce State Management library such as Redux

Respond to feedback
remove google fonts caches
remove status code 0 from CacheableResponsePlugin

put the scriptSig classifying logic in a try catch block

found a way to classify the scriptSig,
hence updated the diff to parse the tx data based on the type of scriptSig

fix lint warnings

rebase to the latest master and update replyAddress feature implementation

It works, no error.

• Weird. I just retest and can confirm that sending tx will remove the hydratedUtxoDetails from from both the sending and receiving wallets.
• The test plan should have more details (my bad, sorry)
• Here are the steps I did
  • inspect localstorage and verify that hydratedUtxoDetails exists
  • send some xec to another wallet
  • wait for utxos to refresh (10s)
  • refresh the localstorage
  • verify that hydratedUtxoDetails was removed
  • switch to the receiving wallet
  • wait for utxos to refresh (10s)
  • refresh the localstorage
  • verify that hydratedUtxoDetails was removed

• app was successfully installed
• icon on home screen appears fine, the "e" appears bigger compare to PWA

getting "invalid command code ."

rebase to the latest master - that fixes the unit test failure

The same, on both LAN and Netlify

tested on

• Samsung S20 FE, Android 11
  • Chrome 96.0.4664.45
  • Firefox 94.1.2
  • Edge 96.0.1054.36

The failure in "Migrating legacy wallet on testnet" was caused by different returned data on Path145 and Path245. Path1899 has the correct data as expected (except additional publicKey).

update per feedback

rebase to latest master
revert previous fix to 'Mirgrating legacy wallet on testnet' unit test

update snapshots test

rebase to the latest master branch

fix unit test failure on testnet

fix unit test failure in "Migrating legacy wallet on testnet"

add @generated to the first line of updated snapshots

rebase to the latest master

Address unit test failture

• fix Migrating legacy wallet on mainnet test failure
• failure in "Migrating legacy wallet on testnet" caused by previous update

as well as this update. Should I wait or go ahead and fix the test with
Path's details on test net?

I notice that you are accessing the app through a LAN IP, make sure that it support HTTPS, (or you can accessing it through localhost,). Web Authentication requires HTTPS.
Alternatively, you can build and deploy it to Netlify or Heroku. Here is a link to my Netlify deployment cashtab.netlify.app

fix error when PublicKeyCredential is undefined. PublicKeyCredential requires https.

update snapshots (now have @generated added to the end of first line)

update snapshots

• Tested on Samsung S20 FE, Samsung J7 Prime, Iphone SE, Ipad, Surface 5, Surface Pro 5, Desktop with Windows 10, Laptop with Windows 11
• I did notice the test failures and working the address that.
• About the New unit tests for this feature, should it be included in this diff? should it be another diff after this?