Failed to Parse Secrets: Can't Parse JSON Bug from accessing Experience Settings in Studio

Bug Reports Studio Bugs
,
1

I am currently having an issue where I can’t set the Experience Settings such as Enable Studio Access to API Services or any other ones…
It keeps warning me with a warning “Failed to parse secrets: Can’t parse JSON”.
I can’t enable those settings at all & they are currently blocking me.

Game: https://www.roblox.com/games/110347948598369/Up-We-Grow

System Information:
OS: Microsoft Windows 11 Pro
CPU: 13th Gen Intel(R) Core™ i7-13650HX (2.60 GHz)

DirectX Version: DirectX 12

GPU 0: Intel (R) UHD Graphics
GPU 1: NVIDIA GeForce RTX 4060 Laptop GPU

GPU 0 Driver Version: 32.0.101.6790
GPU 1 Driver Version: 32.0.15.7283

RAM: 16.0 GB

2 Likes
2

Hi @DevAwesomely,

Does the Experience Settings window appear at all for you, or does it appear but not respond when you click on it?

To help us reproduce the issue, could you please help provide:

  • A screen recording or couple of screenshots showing the issue.
  • Roblox Studio log.

Please refer to this guide for instructions on how to get the Studio logs: https://en.help.roblox.com/hc/en-us/articles/360016022492-How-to-Retrieve-Roblox-Studio-Logs. If there are multiple log files in the log folder, please refer to the “identify the correct log file to send you can either” section in the guide.

1 Like
3

Hi. It does appear for me. It just couldn’t respond. It was not updating few of the buttons. I realized it fixed this issue by Publishing to Roblox, but the warning was still showing up.

1 Like
4

Glad to hear it’s working for you now!

For a new experience, you’ll need to Save to Roblox first in order for the full Experience Settings becomes available.

The warning is informational and non-blocking. While it may still appear, it should not prevent you from accessing Experience Settings.

Please let us know if you need any further assistance.

1 Like
5

Yeah well maybe I didn’t clarify correctly.

My Experience already was Published multiple times before. It’s just that at the time when I was trying to enable the Studio Access to API Services or any of the other options, I tried publishing again. The moment I did that, Studio saved that change. Before it just didn’t want to commit the change, whenever I look at the Experience Settings, that setting I tried to Enable was still Disabled.

That was the problem. Now it works, but this is just a heads up related to this bug.

1 Like
6

Thanks for clarifying. This appears to be a bug where changes in Experience Settings were not saved until you published the experience again.

We’ll keep an eye out for similar reports to determine whether this is a broader issue. Thanks for letting us know!

2 Likes