-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Description
Steps to Reproduce
Device / Operating System: Google Pixel 9a, Android 16
Bluesky Release: 1.108.0
( unsure if this is reproducible on other devices such as iPhone etc )
Description of issue.
WHEN on feed, click the button to write a new skeet.
Click the Camera Icon.

Case 1 ( OS permissions not yet granted ):
- Prompted to grant app permissions
- Clicking CTA on prompt does not open correct Camera setting on OS settings
- After granting permission and going back to app, no change, Camera still not open ( see Case 2)
SHOULD:
- If Permissions not granted, show prompt, display CTA button
- Clicking CTA button opens correct permission setting in OS
Case 2 ( After OS permissions granted ):
- Nothing happens, Camera does not open to take a photo
SHOULD:
- Open Camera to take a photo
Hack to open Camera FOLLOWING Case 2:
Click "Gallery" button, then hit back and THEN Camera opens
Possibly related to a state management problem in whatever component or page manages this functionality.
SHOULD:
- Not behave like this. Clicking on gallery opens gallery. Backing out closes gallery and does not open Camera. Clicking camera opens camera. Backing out takes you back to the post and doesn't open anything else.
FINALLY. If you follow the hack, you will find that a number of Camera "instances" have opened corresponding to the number of times you clicked the camera icon ( which is intuitive behaviour after clicking the icon and seeing no changes). This seems to indicate some kind of state management issue again. Suggest an investigation using a singleton to ensure only one instance of Camera can be opened ( and this instance can be destroyed on exit and created when required, or can be stored in a store using something like zustand and shared by any other components that might need an instance depending on the state of the code ).

Attachments
No response
What platform(s) does this occur on?
Android
Device Info
Google Pixel 9a, Android 16
What version of the app are you using?
1.108.0
Additional Information
No response