YES!

I was going to make an issue for this, and you already have a PR 💥💥

@dennisreimann

1. There isn't any UploadImage API for any other data stucture (for example store), as such, it shouldn't be expected for the app.
2. Instead, you should do like we do in Store: Use the UnresolvedUri type.

A user who wants to update will need to upload the file via the API to the file service, then reference it through an UnresolvedUri.

Hmm, but there are dedicated upload actions for the store logo as well as the user profile picture.

@dennisreimann this really sucks, we don't want to add a separate routes everytimes we want to upload a logo.

Let me think about it.

We could do it via the GreenfieldFilesController, but we'd have to relax the permission requirement. When I implemented it, I matched the original UI-based file action policies, which make it available to admins only.

Are you uploading the files base64 encoded or using HTTP form encoding? From an API POV, the base64 way may be more convenient?

HTTP form, that's also how we implemented the other upload endpoints.