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
The native iOS permissions dialog for photo access opens as soon as the _PickerWidget state is created. This is too soon, as permissions should only be requested once the user wants to send a photo/file.
Steps to reproduce
1. Use the StreamMessageInput widget in a detail page
2. Navigate from overview to detail page
3. Native iOS dialog for photo/gallery permissions appears, instead of only appearing once the user clicks the attachment button
Supporting info to reproduce
cause of the bug:
this shoud occur when the attachments icon is clicked the first time
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@imtoori Hey, I've just updated to 4.3.0 but unfortunately, the permission alert view is still being displayed as soon as the StreamChannel widget is being displayed. It shouldn't happen until the user wants to add an attachment.
Which packages are you using?
stream_chat_flutter, stream_chat_persistance, stream_chat_localizations
On what platforms did you experience the issue?
iOS
What version are you using?
stream_chat_flutter: ^4.2.0
stream_chat_localizations: ^3.1.0
stream_chat_persistence: ^4.1.0
What happened?
The native iOS permissions dialog for photo access opens as soon as the
_PickerWidget
state is created. This is too soon, as permissions should only be requested once the user wants to send a photo/file.Steps to reproduce
Supporting info to reproduce
cause of the bug:
this shoud occur when the attachments icon is clicked the first time
Relevant log output
No response
Flutter analyze output
No response
Flutter doctor output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: