Updating the plugin

Roblox does not update Studio plugins automatically. There is no silent background update and nothing happens on restart — a person has to press a button. That is platform behaviour, not an Apple choice, and it is why this page exists at all.

How to update

1. In Studio, open the plugin management window — Roblox's documentation calls itPlugin Management; the Plugins tab opens it viaManage Plugins.
2. Find Apple and press its Update button.

There is also an Update all Plugins button. Roblox staff confirmed in April 2026 that the bulk button was broken and a fix was coming, and that the individualUpdate buttons still work. If the bulk button does nothing, use the per-plugin one.

How you'll know

You do not have to check. The plugin tells the server which build it is on every time it polls, and the server answers.

• An amber line in the panel when a newer build is published — for example“Apple 1.1.0 is available. Update it in Studio → Plugins → Manage Plugins → Update.”It is also written to Studio's Output window once per message, not on every poll.
• A red line in the rare case where a build is genuinely too old for the server to work with. That one blocks builds and is not advisory.
• Silence the rest of the time, which is the normal state.

Which build am I on?

The Apple panel prints it at the bottom, as Apple Studio · 1.0.0 · independent preview. The web workspace shows the same version under Studio in the project rail once the plugin has reported in. What changed between builds is on thechangelog.

Two numbers, because they answer different questions. Version is the build you have, and it moves on every release including cosmetic ones. Protocol is the contract the plugin and the server speak, and it almost never moves.

Running an old build is fine

Apple's server decides whether to talk to a plugin by protocol, never by version. A plugin several releases behind is served normally as long as it still speaks a contract the server supports — and today the server supports every protocol that has ever shipped, so nothing in the wild is refused.

This is deliberate. Because updates require you to notice a message and click a button in a different window, a server that refused old clients would strand people with no self-service way out. Version skew is the expected steady state here, not an error to be stamped out. What you miss by staying behind is new capability and fixes, not access.