Hi, @xtanion This is working for me on the latest develop branch to date. Could you please post the log also in the issue of what you are getting when clicking on create icon?
I had tested this on pixel 3a.

I guess the error is org.oppia.android E/ProfileManagementController: Failed to store user submitted avatar image and hence it can't access the profile pic from internal storage open failed: ENOENT (No such file or directory)

Might be a permission issue specific to this device, or maybe an SD card image was selected (the app doesn't have read SD card permissions). It seems like more investigation is needed here.

Seems like it was a MIUI specific issue, I tried recreating the same issue on the same device with a custom ROM and it worked fine.

@Tejas-67, PTAL.

hey @adhiamboperes, tried reproducing this error and it worked on all the devices in my case. Maybe this is a device-specific issue.

Unable to reproduce this issue on a Redmi device with the same specs as the reporting device

Actually, never mind, I found a way to repro this issue. In my previous video, I selected the pictures using google photos app, but the issue occurs when using the MIUI gallery app(com.miui.gallery apk).

With the MIUI gallery app, the image path is device image path content://com.miui.gallery.open/raw/%2Fstorage%2Femulated%2F0%2FDCIM%2FCamera%2FIMG_20240804_134024.jpg.

With google photos, the path is content://com.google.android.apps.photos.contentprovider/1/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F1000423837/ORIGINAL/NONE/image%2Fjpeg/1045458194

Now I have to choose an image that is on device only, using both apps:

miui content://com.miui.gallery.open/raw/%2Fstorage%2Femulated%2F0%2FDownload%2F1%20(13).png

google photos content://com.google.android.apps.photos.contentprovider/-1/1/content%3A%2F%2Fmedia%2Fexternal%2Fimages%2Fmedia%2F1000049236/ORIGINAL/NONE/image%2Fpng/210299334

Key Differences:

MIUI Gallery is accessing the image directly from the device's file system.
Google Photos is accessing the image from its own content provider.
MIUI Gallery's URI is simpler and more directly related to the file path.
Google Photos' URI is more complex.

Due to these, when accessing the image file name via avatarImageUri.lastPathSegment, the MIUI uri returns /storage/emulated/0/DCIM/Camera/IMG_20240803_194219.jpg(we are actually only interested in the "IMG_20240803_194219.jpg" bit), while google will return210299334`.

To solve this, we need to only get the last substring from the uris. Instead of using pathSegments.last() or avatarImagePath.lastPathSegment, avatarImagePath.path?.substringAfterLast("/") is a more definite way of getting the last path segment, and this does solve this issue.

This can get pretty complicated, I think, since content providers can basically format their paths in any way that they want (meaning there isn't a guarantee the path ends with the image filename), as better indicated by Google Photos here.

There might be a way to get a proper display name by querying the image content provider directly, but I do wonder: how much does it matter? Could we just come up with an internal name, instead, when saving the image?