-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account links to google drive but doesnt pull info #134
Comments
I would lkke to comment saying i am experiencing the same issue, all of a sudden most of the gear i have dismantled is no longer tracked. Edit After searching through the debug i have discovered that for some reason on 07/12/18 the google drive file for my account was wiped, went from 1558 items tracked on 07/05/18 to 0 files tracked on 07/12/18. This wipe would be the culprit for losing tracked data of dismantled items but i see no reason for it having happened? |
Same issue here, the api page shows some items as dismantled so it must be working in some aspect, but there are gunsmith weapons for example that I have acquired multiple times just in the past week that I always dismantle that do not show up as acquired. |
Hey - sorry about the silence on this one. Honestly, I don't know what's causing this. The best I can tell is that Google Drive has, for some reason, dropped/wiped this file for a bunch of people. But even that I find hard to believe. The bad news is that I'm not sure if ill be able to find a solution to get anything back. The good news is that hopefully there will be a 'consolation prize' solution in the coming week, which may actually be better than what we had before... Stay tuned. |
Hi, i love the site, its amazing, but the google drive link seems to fail every now and again (at least for me). Today the account looks linked but doesn't show any of my collection that has previously been deleted. Just what I currently have in vault / on character. This has happened once before also and I ended up having to start again. Is it user error or a bug? thanks!
The text was updated successfully, but these errors were encountered: