Open edchaser23 opened 3 years ago
@edchaser23 Turn on Debug Mode in the extension's settings, then try to sync the account again. Afterward, open the Robinhood and Mint tabs and check the console logs to see if they show the expected values.
Appologies, I'm a bit of a layman- Where in the Console should I be looking to see if its returning the expect values?
Nevermind- I found it. It looks like the extension isn't able to pick up values from Robinhood. It's gettting Error 400. I've attached the log. robinhood.com-1612715018255.log
So I just figured out the issue. I have a partial share of an ETF and rather than showing the market value of my investment it’s show it’s showing the market cost, as if I had bought a full share.
I was also mistaken earlier when I said it was listed in other. It’s actually listed in Stocks.
On Sat, Feb 6, 2021 at 10:10 PM George W. Walker notifications@github.com wrote:
@edchaser23 https://github.com/edchaser23 Turn on Debug Mode in the extension's settings, then try to sync the account again. Afterward, open the Robinhood and Mint tabs and check the console logs to see if they show the expected values.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pkmnct/robinhood-mint-sync-chrome/issues/49#issuecomment-774582791, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASYD4PUGBWT7LJQAUNYZLSDS5YACNANCNFSM4XGQ77IA .
-- Eddie Chase
The numbers being synced to to Mint are not accurate. Cash, Crypto, and Stock are all showing 0 while "Other" is showing $69.50.
Without giving too much detail, I have money in cash, crypto, and stock- Not sure what would even be in other, however, it does not add up to 69.50. In fact my Robinhood numbers have fluctuated quite a bit but it's been syncing at about 69.50 for about a week.
This started around the time of the GME short squeeze. I had started pulling all my money out with the intention of closing my account, but not being able to find a decent alternative, I decided to return to it. I had uninstalled the extension after clearing out my account, and after reinstallation is when I started getting this issue.