Issue: Files created using the fileCreate mutation return a global Shopify ID, but this ID is rejected as “invalid” when used in the image field of collectionCreate or collectionUpdate mutations.
Impact: Combined with a separate error ({src=> "Error updating collection with this image"}), developers currently lack a reliable method to update collection images through the Admin API.
Context: The user references two related community posts experiencing similar problems with collection image updates.
Status: The issue remains unresolved with no workaround provided.
Calling fileCreate results in a global Shopify id value being returned for the file. However, when using the id value within the image field of the mutations collectionCreate and collectionUpdate, the error “invalid id” is returned.
Combined with the error {src=> “Error updating collection with this image”} described in the following two posts and there is simply no reliable way to update collection images via the Admin API.