You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
From my expo app, I follow @dabit3's instruction in which a section teaches how to pick an image with expo ImagePicker and upload the image blob to AWS Amplify Storage. Even though I am able to upload the image blob (I can tell from the image's timestamp), the image on S3 is not the one I uploaded.
This is not an amplify-js issue actually. It turns out that react-native fetch doesn't assign "blob" mime-type to the xhr properly. Please find details at expo/firebase-storage-upload-example#13.
Describe the bug
From my expo app, I follow @dabit3's instruction in which a section teaches how to pick an image with expo
ImagePicker
and upload the image blob to AWS Amplify Storage. Even though I am able to upload the image blob (I can tell from the image's timestamp), the image on S3 is not the one I uploaded.To Reproduce
Steps to reproduce the behavior:
expo start --ios
)Expected behavior
The image on S3 should be the image I upload from my IOS simulator / my IOS phone.
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: