We have confirmed the cause to this issue and it is expected to be resolved with the launch of Destiny 2 Update 2.1.4 scheduled for January 29. https://t.co/rWrFizXWeH— Bungie Help (@BungieHelp) January 23, 2019
We have confirmed the cause to this issue and it is expected to be resolved with the launch of Destiny 2 Update 2.1.4 scheduled for January 29. https://t.co/rWrFizXWeH