Bugs

What is the issue? Pricing data for tokens are showing outdated values and is not syncing with real-time price feeds. Portfolio totals may also be inconsistent between the desktop site and mobile app. Who is affected? Users accessing their portfolios on both desktop and mobile apps, especially those relying on up-to-date pricing information. As a user, what should I do? Please upvote this post to indicate that you are experiencing this behavior. There currently is not a workaround for this bug and it will need a fix from the team. We appreciate your patience while we work to resolve this. Keywords: price feed discrepancy, mobile vs desktop, outdated portfolio values, sync issue, real-time pricing, wrong price

Bug Report: Inflated 2022 Capital Gains from Gemini Sync What is the issue? Some users are seeing inflated capital gains for the 2022 tax year due to incorrectly synced Gemini transactions. These appear to have decimal discrepancies or inflated values compared to expected amounts. Who is affected? Users with Gemini accounts synced to CoinTracker, particularly for the 2022 transaction history. Affected users have not modified their Gemini connection (no reimport or reauthorization). What is the workaround? Users can ignore any erroneous transactions if a fix is needed in the near term. Keywords: Gemini sync issue, 2022 capital gains, inflated balances, decimal discrepancy, Gemini transaction error

Bug Report: Only Newer Transactions (Post-Tax Year) Sync After Adding Wallets What is the issue? When users who have previously downloaded tax forms add a new wallet, exchange, or re-add a removed one, only transactions after the downloaded tax year are added. This results in missing historical transactions and incomplete reporting. Who is affected? All users who have downloaded tax forms and then add or re-add any wallet, exchange, blockchain, or CSV-based account. What is the workaround? Users can manually backfill missing transactions and/or use the re-import option to bring in historical data for the affected accounts. Keywords: only recent transactions syncing, missing older transactions, wallet re-add missing data, post-tax year sync issue

Bug Report: Gate.io SquidGrow Asset Mismapped to New Token What is the issue? Transactions from Gate.io involving the delisted SQUIDGROW token are incorrectly mapped to the new SQGROW asset. This results in significantly inflated portfolio valuations due to incorrect pricing. Who is affected? Users who held or transacted in SQUIDGROW (old token) on Gate.io , especially prior to its delisting on 9/5/2023. What is the workaround? No immediate user action is required as the incorrectly mapped asset has no price history and should not affect tax calculations. Users can monitor this post for updates. This should only be impacting portfolio, wallets and assets displays and not have a tax or transaction impact. Keywords: Gate.io SQGROW mismatch, SQUIDGROW delisting, incorrect pricing, asset mapping issue, inflated portfolio value

What is the issue? The 'Re-Import' option for wallets is not visible when using the Brave browser due to compatibility issues. Who is affected? Users accessing CoinTracker through the Brave browser. What is the workaround? Users can switch to a supported browser such as Google Chrome or Firefox. Alternatively, using an incognito/private window may help resolve the visibility issue. Keywords: Re-Import not visible, Brave browser issue, wallet integrations, UI bug, unsupported browser

Users may experience: Some Binance accounts are failing to sync to CoinTracker No error message is displayed. Expected behavior: Binance accounts should sync seamlessly, with all transactions and balances updated correctly. As a user, what should I do? If Binance fails to sync, users can try uploading their history using their CSV according to our import instructions. Users can also upload their CSV as a generic CoinTracker CSV. You can do so by following the instructions in our support article: How to Convert your Transaction History to a CoinTracker CSV . Additional Information Please upvote this post to indicate that you are experiencing this behavior. We have information on bug reports and what the status means in our help center . For further assistance or inquiries regarding this bug you can contact the support team . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Binance, sync issue, Binance not syncing

What is the issue? Multiple incorrect MATIC to POL trades are appearing for Binance US users. These entries are the result of a token swap that happened earlier this year. Who is affected? Binance US users who held or interacted with MATIC during the token swap process. What is the workaround? No action is needed at this time. The issue is being investigated by our engineering team and will be resolved automatically. Keywords: MATIC to POL, Binance US, token swap, incorrect trades

Bug Report: Balance Differences What is the issue? Significant discrepancies between calculated and reported balances are appearing for certain crypto assets when Kraken is synced via API. This is occurring for both the Auto-Earn and Staking features in Kraken. Users that enable then disable these features may see balance differences in their wallets on CoinTracker. (see screenshots below) Who is affected? Users who enable/disable the Auto-Earn and Staking features in Kraken or unstake an entire asset from their Kraken Earn wallet. What is the workaround? There is currently not a workaround, however our Engineering team is aware of the issue and are working on a fix. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly. Keywords: balance differences, auto-sync issue, crypto assets, unstaked assets, Kraken

What is the issue? Some Kraken Ledger CSV files are failing to upload to CoinTracker. Who is affected? Users attempting to import Kraken Ledger CSV files into CoinTracker. What is the workaround? Users can wait for a fix or convert their Kraken CSV into CoinTracker’s generic supported CSV format in the meantime. Keywords: Kraken CSV upload, Ledger import failure, Kraken transaction import, CSV format issue, CoinTracker CSV

Users may experience: Transfer transactions are being displayed as "send" transactions This can result in CSVs uploading with a negative balance. Expected behavior: Transfer transactions should be accurately classified as credits when applicable, ensuring they reflect correctly in the user's account as non-debit transactions. As a user, what should I do? For a large number of transactions it is recommended to wait for a fix if possible. For a smaller number of transactions, you may wish to delete the inaccurate transactions and recreate them properly as a credit. Additional Information Please upvote this post to indicate that you are experiencing this behavior. We have information on bug reports and what the status means in our help center . For further assistance or inquiries regarding this bug, you can contact the support team . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: transaction classification, transfer transactions, Celsius, CSV