Bugs

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

What is the issue? Some Abstract Wallet transactions are showing duplicate asset movements (2–3 incoming or outgoing entries) when there should only be a single receive or send amount for the transaction. Who is affected? Users syncing transactions from Abstract wallets. What is the workaround? No immediate workaround is available. Users can manually delete duplicate amounts while we work on a fix. Keywords: Abstract Wallet, duplicate transactions

Users may experience: Some LTC wallets are failing to sync to CoinTracker. Users will experience the red 'Failed to sync wallet' error message or have a synced wallet with zero transactions. As a user, what should I do? 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. Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: LTC wallet, sync issue, no transactions, sync failure, failed to sync, litecoin

Users may experience: Users will see an erroneous negative balance in the outgoing wallet during a transfer where both the outgoing and incoming wallets have associated fees. The outgoing wallet is reflecting both the outgoing and incoming fees, creating an insufficient balance. Expected behavior: Only the outgoing fee should be deducted from the outgoing wallet, and the incoming fee should be deducted from the incoming wallet. As a user, what should I do? Users with fees on both the incoming and outgoing side of the transaction should deduct the amount of the fee from the receiving/incoming side of the transaction and ignore the second fee so there's no double fee on transfer. 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 . Keywords: transfer fee, insufficient balance, negative balance

What is the issue? The Robinhood API sync completes without error, but returns 0 balance and 0 transactions, even though the account has activity. What is the workaround? Users can manually import their Robinhood transaction history using a CSV. Instructions are available in the Help Center . Keywords: Robinhood API, zero balance, missing transactions, sync issue

What is the issue? UK and Canadian users with a qualified paid plan are still being paywalled when trying to view tax lots on the Tax Loss Harvesting page. Additionally, the currency is incorrectly displayed as USD instead of the home currency, such as GBP or CAD. Who is affected? UK-based or Canada-based users who have an eligible paid CoinTracker subscription and access the Tax Loss Harvesting feature. What is the workaround? There is no direct workaround for the paywall issue. Please wait for a fix from our team. Keywords: UK tax loss harvesting, paywall issue, incorrect currency, tax lots not visible, GBP vs USD

What is the issue? When importing a native Robinhood CSV two tokens are created when there should only be one. For example, for BTC - BTC and BITCOIN are both created. For ETH - ETH and ETHEREUM are both created. Who is affected? Users importing Robinhood CSVs that use the blockchain name in the network column. What is the workaround? Users can manually edit the CSV to replace the network column before importing. For BITCOIN replace with BTC. For ETHEREUM replace with ETH. Keywords: Robinhood CSV import, BTC mislabeled, wrong token mapping, network column, balance discrepancy

Bug Report: SOL Wallet Syncing Shows Balance Discrepancies What is the issue? Users are reporting a mismatch between their calculated SOL balance and the value reported for the SOL address. Who is affected? Potentially any user with a SOL address added. If you are impacted you will see an unexplainable balance difference in SOL. What is the workaround? There is currently no automated workaround. Users can manually review their transaction history or import missing data via CSV if they identify gaps. Keywords: SOL wallet sync, SOL balance mismatch, Solana discrepancy, reported vs calculated balance, missing SOL transactions

Bug Report: SOL Limit Order Close Not Categorized, Causing Cost Basis Loss What is the issue? Some SOL limit order close transactions are not being categorized in CoinTracker, even though the open order is correctly classified. This results in the loss of cost basis, causing incorrect gain/loss calculations. Who is affected? Users executing SOL limit orders using Jupiter Limit Order V2 on the Solana blockchain. What is the workaround? There is currently no workaround. Users cannot manually adjust the close order in a way that restores the correct cost basis. Additional Details The affected program ID is: j1o2qRpjcyUwEvwtcfhEQefh773ZgjxcVRry7LDqg5X (Jupiter Limit Order V2). Both the open and close transactions should be categorized to maintain accurate cost basis tracking. Keywords: SOL limit order, cost basis issue, transaction classification, gain/loss discrepancy, Jupiter Limit Order V2

Bug Report: eToro Transaction Report Upload Fails What is the issue? Users attempting to upload their eToro transaction reports encounter an error: "Failed to find all required column headers in eToro transaction report column headers." Who is affected? Any users trying to upload their eToro transaction reports. What is the workaround? Users can manually convert their eToro .xlsx report to a CoinTracker-compatible CSV before uploading: Follow the instructions in this guide to convert your file. Upload the newly formatted CSV file to CoinTracker. Keywords: eToro upload error, transaction report, column headers issue, CoinTracker CSV conversion