{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/18/2020 5:56:26 PM
18
[quote] To ensure everyone has a chance to redeem their code or a friend’s code for the “In the Valley” Crimson Days emblem, the deadline to redeem has been extended until tomorrow’s daily reset. Players need to already have the code to redeem it.[/quote]
https://twitter.com/bungiehelp/status/1229826677582135296?s=21
English
-
I never got an email that the reward was available to submit in order to get the code, and it never showed up on my rewards feed. I checked multiple times, and figured maybe there was an issue which would be fixed at reset. I’m not too worried about it since it’s an emblem that I will never use, but it irks my completionist nature.
-
If you have the Redeem Page where you kept getting the Error Code while trying to enter your code it saves it in your cache data so long as you didn't delete your cache it is still there. I thought I was boned myself but went to my phone that I tried to redeem it from and lo an behold I reloaded the redeem page for my code. To clarify it is NOT the redeem page with the LIST of redeemable items, but the next page when you click to redeem a code. Lemme know if that didn't make sense.
-
Alright I'll step by Step what I did. Opened my Browser (Not the App) Opened a new tab and scrolled through my history to find 'Code Redemption | Bungie.net' It opened my session from then and I redeemed it successfully. I don't really trust the App with how slowly it tends to load sometimes so whenever I redeem rewards I usually do it via a web browser. So the App probably doesn't save any of that, you kinda may be S.O.L. Still, if you tried it on a browser on any device you may still have hope.
-
Based on your suggestion, I hit ctrl-H in my browser to view history. I tried clicking a few different Bungie links in my history, and the one that was titled "Reward" actually worked! I'm just sorry that I figured this out too late to help anyone else. But I thought you might like to know that your post helped me. Thank you!
