Skip to content

Cloudinary Media Library does not refresh after cropping image (requires manual refresh) #1276

Description

@herbicus

Describe the bug

When applying a crop to an image via the Cloudinary Media Library inside the Sanity Studio plugin, the updated asset is not reflected immediately in the Media Library UI.

The crop operation completes successfully, but the Media Library list requires a user to manually click the “refresh list” icon to see the new asset.

This results in stale UI state and no immediate feedback after editing an image.

To Reproduce

Steps to reproduce the behavior:

Open Sanity Studio

Open a document with a Cloudinary image field

Click “Select image” to open the Cloudinary Media Library (plugin UI)

Select an existing image and apply a crop using the Cloudinary editor

Save/confirm the crop

Observe that the Media Library requires you to exit out of the editing view by clicking "Discard" to get back to the list of images.

Notice the image is not in the list.

Click the “refresh list” icon in the Media Library

The updated image is now reflected

Expected behavior

After applying and saving a crop, the Cloudinary Media Library UI should automatically reflect the updated asset without requiring manual refresh.

Ideally, the plugin should:

Automatically re-fetch the asset list after edits, or

Optimistically update the affected asset in the UI

Screenshots

Which versions of Sanity are you using?

Sanity: ^5
@sanity/cli: ^5

What operating system are you using?

macOS: Tahoe 26.3.1

Which versions of Node.js / npm are you running?

Latest LTS versions

Additional context

Plugin version: sanity-plugin-cloudinary@^1.4.1

This issue appears isolated to the Cloudinary Media Library UI within the plugin, not the Sanity document itself

The crop is correctly persisted in Cloudinary

The issue seems related to the plugin not invalidating or re-fetching its asset list after a mutation

This can be confusing for editors, as it appears the crop did not apply until manually refreshing

Security issue?

No

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions