Hiya
We experienced an engine bug last night wherein the EditableImage API seemingly lost its’ permissions mid-flight in server.
The API is enabled on our experience and has been for several months. We have never toggled it off.
We have a guard to ensure EditableImage is accessible BEFORE we try to use it:
local can_use_editable_image, error_message = pcall(function()
local test_image = AssetService:CreateEditableImage({ Size = Vector2.new(1, 1) })
end)
which was passing, but on attempts to mutate created image (ei:DrawRectangle), we consistently errored out throughout the rest of server lifetime:
Our game falls back to a dummy if the EditableImage API is not enabled for that experience (ie on test servers). Inconsistent permission grants on different methods at different times was unexpected.
The period in which failing servers were spun up appears to correlate with a period (per downdetector) of Roblox platform instability last night.
We found that while this issue was reported back in June, but was closed as fixed here. EditableImage:DrawRectangle() is not documented as an asynchronous API method and we would not expect it to fail due to underlying network issues, such as Roblox outage.
The only band-aid for this would be wrapping every EditableImage call in a pcall, which feels inappropriate given the nature of the API.
Thanks