Secrets in Local Testing unable to be found

[cookierrific]

Description

---

Hi,

I’ve been experimenting with Secrets and I found that in local testing local secrets do not function properly.

When I attempt to play test locally Can't find secret with given key is raised despite the fact I’ve specified the secrets in the secrets menu in game settings.

It’s important to note that in Production the secret is read without any issues.

Reproduce

---

Secrets Bug.rbxl (54.8 KB)

Make sure Allow Http Requests is enabled, and specify the secrets:

{"secretName": ["YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXo=", "*.example.com"]}

Play test the game and the Can't find secret with given key error will be raised.

[zipcatmax]

Good day! Thanks for the report!
Your example “works on my machine” ™. I wonder if you could describe how you Play Test the game? If possible, add a few screenshots of what button you click to start the Play Test.

[cookierrific]

Thanks for the response, I’ve also had others report that they weren’t able to replicate it, so perhaps I’m being stupid.

These are my steps:

1. Save to roblox the example place.

2. Configure game secrets, allow http requests and save

3. Press play and experience the issue.

[zipcatmax]

To me, this happens when I run the game in “Team Test” mode (which means, it’s not running locally, but on Roblox servers).

I wonder if you could create a production secret for this game, named the same way, secretName. If creating such a secret makes your game run fine, it’d mean that some intermediate step enabled team test for your game (and then it uses production secret).

[cookierrific]

Strangely it works now? I reponed my game 5 days later and the secrets field was no longer filled, filled it with {"secretName": ["YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXo=", "*.example.com"]} and now it works.

[zipcatmax]

Glad to hear that everything works!
As for what it could’ve been, I wonder if there were any Windows Updates applied after you added locally defined Secrets, and tried to use them.