I didn't get the skin from the 'Ash Free Unlock Bundle' on the Epic Games Store
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number AMD Ryzen 5 4600H with Radeon Graphics NVIDIA GeForce GTX 1650
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? Tsunidayo
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)?
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In the lobby (waiting area before the match)
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Lobby
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. I loaded up the game to check out the skin I got
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 8th November 2024. I don't know what time of day it was (GMT)
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? I got the 'Ash Free Unlock Bundle' from the Epic Games Store because I wanted to get the Ash skin that comes with it. I already had Ash but assumed I would still get the skin. I opened Apex after getting the bundle and I got the 'Rewards Unlocked' screen telling me I got Ash and Ash's Burning Chrome skin. I have not received the skin.
What should be happening instead? I should get the skin
Steps: How can we find the bug ourselves? Try getting the bundle on an account with Ash unlocked and see if it works. Note: I got the bundle through the Epic Games store, but I opened Apex using Steam because my Steam, Epic and EA Apex accounts are all connected.
The attached picture shows the Rewards Unlocked screen I referred to. It is from my second account, which I used to ensure the bug was only on my main account.