Any further updates on this issue? I cant believe its been 12 days already and no response yet.
here is correct workflow:
1 Use Custom collection like "Images". With field "imageBase64" string type.
2 Store inside this "images" collection row with correct base64 source to image file.
3 Use read/list/query service to fetch row/rows from this collection.
4 In Success mapping link "imageBase64" response parameter to image component asset property.
Also if you can not get it to work - please show us your implementation on screen shots:
1 DB collection
2 Service response tab.
3 Service datasource "success" mapping.
4 How you invoke the service.
just to add further, the encodedBase64 string, if put in an online decoder works as expected and shows the image properly. This means the encoded string is alright.
Also, there is a 'for' loop in the server code which has been done right now as a quick and dirty solution to show the error to you. Obviously this can be avoided if the image is assigned to 1 asset only.
Anxiously waiting for a resolution to this.