[WEB-7058] Unable to redeem the 15th anniversary cape

Mod Note

This issue is most likely due to a high load on the website servers as over 1 million players attempt to claim this cape. Please try this again in 24 hours or when the server load is less.

Please only comment if your comment is adding new information. Comments such as "me too" will be removed as to not obscure those comments that are helpful

https://twitter.com/MojangStatus/status/1791532669370593585

If I go to minecraft.net and try to redeem the Minecraft 15th anniversary cape it tells me that I didn't purchase the game, even though I own both Java and Bedrock. I have already checked that I am logging in with the Microsoft account on which I own the game.

Linked issues

is duplicated by 33

MC-272134 Minecraft Cape 15 Aniversary Resolved

MC-272137 no me dejar reclamar la capa Resolved

MC-272138 Minecraft Premium Resolved

MC-272139 i own minecraft but website says that i need pay it again to have the cape Resolved

MCL-24255 显示没有我的世界 Resolved

28 more links

Attachments

Comments 27

Tintineglb 2024-05-17T15:53:08Z

I have the same problem

bth123 2024-05-17T15:56:10Z

have the same problem

cg28008 2024-05-17T16:07:57Z

Same problem with me, but I have just bedrock edition on mobile

Featherstorm208 2024-05-17T16:15:05Z

seen multiple people report the same issue over discord as well. I am also experiencing it

KR_ 2024-05-17T16:19:14Z

This is caused by high traffic, which in turn overloads Mojang's servers. You will be able to redeem your capes promptly.

17 more comments

Lucas Pereira 2024-05-17T17:09:00Z

I have the same problem

787noteswiper 2024-05-17T17:09:46Z

still can't claim this

Nazagamer20 2024-05-17T17:51:44Z

On an account that purchased minecraft before java and bedrock merging, it shows that.

On another account (My brother's one) it works and he bought it when it was bundled

nitemar88 2024-05-17T17:55:34Z

Hey, I also got the same problem with the cape claim page. I first got Minecraft using a redeem code could that in anyway be related to the problem?

Shenriqu3z 2024-05-17T17:56:52Z

Seems like everyone who bought Minecraft wayy back then before it bundled with bedrock is having this issue... So upsetting as us older players literally been supporting this amazing game for several years!

Nullicorn 2024-05-17T18:02:38Z

This is not a traffic issue. The site is specifically checking for the minecraft_bedrock entitlement key to see if the account owns the game, which those who didn't purchase Bedrock before it was bundled with Java don't have.

Cape claiming works perfectly fine when done manually, i.e. the following in the browser's console:
MinecraftUser.claim15YearCape({
javaUrlBase: 'https://api.minecraftservices.com',
capes: [],
capeId: 'ef9e95b6-48a3-4fd7-93d4-7e7d9448d2f1',
bedrockEntitlementOffer: '7118a7d5-240e-4f6d-8959-5269ba041938',
bedrockEntitlementId: 'b0bf1091-bb6b-4bd7-80f9-6e43f0d03e39',
bedrockUrlBase: 'https://net.web.minecraft-services.net'
})

Edit:

Some reassurance for anyone who has used this and is worried about their account security:

The function MinecraftUser.claim15YearCape comes from the page itself and is the one that's supposed to be run when clicking the claim button
javaUrlBase and bedrockUrlBase are URLs to Minecraft's account services. Both come from the page's source code and are the ones intended to be given there
capes is your account's current list of capes, though I found that it wasn't needed and left it blank in the snippet: []
capeId just indicates which cape is being claimed. In this case, that ID corresponds to the anniversary cape. All capes have an ID like that, and this one was also taken from the page's source
bedrockEntitlementOffer and bedrockEntitlementId identify the 15-year promotion on the Bedrock side of things, telling the server what's being claimed (and what to check to see if it's already been claimed). Again, these are straight from the page's source

For context, here's the data used to initialize the cape section of the page:

{
    "bedrockEntitlementOffer": "7118a7d5-240e-4f6d-8959-5269ba041938",
    "bedrockEntitlementId": "b0bf1091-bb6b-4bd7-80f9-6e43f0d03e39",
    "gameEntitlementKey": "minecraft_bedrock",
    "javaCapeId": "ef9e95b6-48a3-4fd7-93d4-7e7d9448d2f1"
}

Here's the portion of their code that calls MinecraftUser.claim15YearCape. I used this as a reference:

claim15YearCape: (t, e, s, i) => {
    let a = 'https://api-staging.minecraftservices.com',
    n = 'https://net.stage-732c232f.web.minecraft-services.net';
    switch (this.#n.environment) {
      case 'preview':
      case 'prod':
        a = 'https://api.minecraftservices.com',
        n = 'https://net.web.minecraft-services.net'
    }
    return MinecraftUser.claim15YearCape({
      javaUrlBase: a,
      capes: t,
      capeId: e,
      bedrockEntitlementOffer: s,
      bedrockEntitlementId: i,
      bedrockUrlBase: n
    })
}

Source: https://www.minecraft.net/webui/mc-components.min.js

[MOD] Greymagic27 2024-05-17T18:17:43Z

https://twitter.com/MojangStatus/status/1791532669370593585 has now been made which can also be watched for updates.

Shenriqu3z 2024-05-17T18:21:22Z

Bro THANK YOU so MUCH! You're literally the only person who had a fix for this bs.

skky 2024-05-17T18:21:26Z

Thanks, it worked

HokiBoy8915 2024-05-17T18:36:02Z

How to solve this problem, namely, how to get cape from a mobile device, the console is not in the google mobile browser?

Daniel_Nerd 2024-05-17T18:43:36Z

here's a fix!

go to the claim page while logged in, press F12(or right click and then inspect elements), go to console, and paste this, click enter, and press the button.

MinecraftUser.claim15YearCape({
  javaUrlBase: 'https://api.minecraftservices.com',
  capes: [],
  capeId: 'ef9e95b6-48a3-4fd7-93d4-7e7d9448d2f1',
  bedrockEntitlementOffer: '7118a7d5-240e-4f6d-8959-5269ba041938',
  bedrockEntitlementId: 'b0bf1091-bb6b-4bd7-80f9-6e43f0d03e39',
  bedrockUrlBase: 'https://net.web.minecraft-services.net'
})

this code sends an https request for the cape, bypassing the current bug! (code wasn't made by me, idk who found it originally)

bladeGT0284 2024-05-17T18:54:33Z

thank you very much, it worked for me

Brorenzo 2024-05-17T19:27:27Z

Try it now folks. I just got mine without the band-aid fix below.

violine1101 2024-05-17T19:31:31Z

You may also want to try logging out and back into your account; that might resolve the issue for some users.

KR_ 2024-05-17T19:40:33Z

I've heard from a few users that using firefox instead should work.

BugTracker 2024-05-17T22:00:48Z

After a little testing, this only seems to affect some web browsers. If you're still facing this issue, try using web browsers like Microsoft Edge/Firefox.

leon123 2024-05-18T05:47:46Z

I have newest version of Minecraft Bedrock on PlayStation 4 and I'm logged in with microsoft account.

When I want to claim green cape with creeper from [Celebrate Minecraft’s 15th Anniversary with Sales & Giveaways | Minecraft|https://www.minecraft.net/en-us/15th-anniversary?mcRef=redeemCape] I see communication:

It looks like you don’t own Minecraft yet!

Click the link below to get Minecraft and come back here to claim your cape!

PURCHASE MINECRAFT

Learn more

[MOD] Greymagic27 2024-05-18T08:03:52Z

Please check if this is still an issue for you

leon123 2024-05-18T08:51:36Z

Now I can claim cape thanks

Pablopr3 2024-05-23T00:46:15Z

I'm facing a similar issue. For me, I get the correct "claim the cape" button, the website correctly identifies that I have purchased Minecraft. But after I click on the button, I get the "Cape could not be redeemed, please try again" error. I am logged in, I own the game, and the cape is not redeemed.
This has been going on since May 18th, when I first tried to redeem it.

If it's of any help identifying the issue, the request my browser makes to redeem the cape gets a "401 Unauthorised" error every time (I've attached a screenshot). This happens at least on Chrome, Safari, and Firefox (macOS), and Chrome (Android)

Pablopr3 2024-05-23T19:43:11Z

At this moment, trying the same, no longer yields a "401 Unauthorised" error, but a "500 Server Error".

The body of the response is:

{
    "namespace": "ServiceRuntime",
    "code": "InternalServerError",
    "message": "Bad Request\n\nStatus: 400\nResponse: \nTitle not activated",
    "customData": {}
}

I do own the game(s), but I was gifted Minecraft Bedrock when it first released, because I owned the Java version. Maybe that has something to do with the issue

Pablopr3 2024-05-28T15:55:34Z

Please do note that the issue I'm describing is still happening. I tried to open another issue, but it was marked as a duplicate of this one. I do not believe they are similar, but it was marked as so.