{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/9/2019 4:38:35 PM
5
It's been 14 days since my Destiny 1 account was lost to Tapir. "Actively investigating" no longer a valid response.
I've posted about this repeatedly. Occasionally I’ll get a reply stating that Bungie is “actively investigating” the issue. Zero progress. I’ve tried all kinds of ways to ask for more information but all I get is silence.
Please stop ignoring us. This isn’t going away. I have over 1,000 hours in this account, and others have similar investments. Tell us something more than you’re actively investigating, because after two weeks, this is just insulting.
-
2 RepliesHey Robot, check and see if you can get in now. I can confirm that both my PS4 and XB1 accounts are working now!
-
Same. After a D2 raid we wanted to private match pvp in D1 for grins. This was days ago. They all got in. I got Tapir. Just tried again and am still unable to sign in.
-
3 RepliesExactly the same issue here. Happened when I linked Stadia to cross-save. I am getting Tapir on both my Xbox and PS4 D1 accounts, so it is definitely related to cross-save, even though D1 should not be affected. Bungie, please communicate with us. Like TC, I have put thousands of hours and hundreds of dollars into Destiny, and would really like to play the game that I have put such an investment into.
-
1 ReplyIt's sad to say, but I'm a little relieved to see that I'm not alone in this situation and waiting for Bungie's response. Could the maintenance of tomorrow solve the problem? @Bungie, please keep us informed!
-
7 RepliesHi there, Thanks for reaching out. Your account is not lost, and we are actively investigating players receiving TAPIR error codes when attempting to log into Destiny.
