Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions are still not requested during profile photo setting (Android) #17849

Closed
Tracked by #17241
pavloburykh opened this issue Nov 8, 2023 · 5 comments
Closed
Tracked by #17241
Assignees

Comments

@pavloburykh
Copy link
Contributor

This one is related and should be fixed is scope of RN upgrade PR #17241

Reproducing on Android 12, Samsung Galaxy A52

Preconditions: media permissions are not granted

Steps:

  1. Proceed to "Create profile" onboarding step
  2. Open gallery to set up profile photo
  3. See if permission pop up appeared when opening gallery

Actual result: permissions are not requested. Gallery is opened all the images are available for selection. User can set up gallery image as profile photo.

telegram-cloud-document-2-5355054534202769532.mp4

Expected result: permissions should be requested. User should not have access to gallery images until permissions are granted.

Additional Information

@siddarthkay
Copy link
Contributor

Logging my findings below,

In case of profile picture we rely on react-native-image-crop-picker library to show us a native image picker with cropping capabilities ref : https://github.com/ivpusic/react-native-image-crop-picker
In case of showing image picker from chat screen we rely on react-native-cameraroll library ref : https://github.com/react-native-cameraroll/react-native-cameraroll

In case of react-native-cameraroll (used in chatview) we explicitly ask for user permissions before invoking any of the camera/gallery related functions, however in case of react-native-image-crop-picker we don't.

There would be good reasons for having 2 separate libraries for this purpose in the past I assume.

@siddarthkay
Copy link
Contributor

Explicitly asking for media permissions for consistent behaviour here : fe7d021

@pavloburykh I verified this on 2 android emulators, API 29 and 33.

Could you pls verify?
Thank you.

@pavloburykh
Copy link
Contributor Author

Could you pls verify?

Hi @siddarthkay! Quickly checked, the issue is gone for me. Thank you!
Currently we are busy with release testing, will be able to continue more deeply testing after we finish with the release.

@siddarthkay
Copy link
Contributor

Thanks for checking @pavloburykh !

we are busy with release testing, will be able to continue more deeply testing after we finish with the release.

Awesome! Sure, take your time :)

@siddarthkay
Copy link
Contributor

fixed here : #17241

@ilmotta ilmotta removed the bug label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants