As a user I understand that some tokens may be imported into CoinTracker that are unsupported tokens. Unsupported tokens are common for DeFi and NFT activity, in some cases CoinTracker begins to support a token which requires me to change an unsupported token with the support version as seen in this guide.

Users report the ability to change an unsupported asset in a transaction to a supported asset from the edit transaction page but when selecting save the change does not persist on the actual transaction.

Users can workaround this by ignoring the unsupported token in the edit transactions page and recreating the token entry using the 'add asset' feature to add the supported version of the token (Image 1). Repeat the process of replacing your unsupported asset with supported version by ignoring the unsupported asset and creating an entry with the supported asset.

We have escalated this behavior to our engineering team and will update this post once a fix is deployed.