Video capture fails to present stop button

[BrendanGrant]

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• This isn't a feature request or a discussion topic

Bug description

There seems to be a timing issue related to trying to record a video from within the app, where it can be locked on to record, but cannot actually stop and send. Killing the app or taking a single picture with a button seems to be the only way out of the situation.
A short tap on the on-screen shutter button takes a picture. A long press sees some animations go on, converting the button to a stop button, and showing a lock icon on the right side. It seems that a medium press, long enough to get it to start recording, but not so long for the animations to complete and UI elements to change is behind this issue.

Steps to reproduce

• Open up a chat on iOS
• Click the camera icon
• Press and hold on on-screen shutter button and quickly drag finger to right to lock recording on for video.
• Tap on-screen shutter button again a time or three to try to stop recording and send video
• Realize futility

Actual result:

Incomplete button, missing stop element at bottom of the screen which prevents stopping of the recording.

Expected result:

Tapping the on-screen shutter button results in stopping of recording and normal behavior.

Screenshots

Buggy recording UI:

Expected recording UI:

Device info

Device: iPhone 12 Pro Max

iOS version: 15.5

Signal version: 4.42.0.12

Link to debug logs

https://debuglogs.org/ios/5.42.0/24c78b72c53582ec3acd9bd9ff36dd52a1b3d2f2baf26dcdccb729cc6692ea16.zip

[EvanHahn-Signal]

Sorry you're running into this. We're making some changes to this screen that should fix your bug. Please let us know if you still experience it after updating to Signal 5.45 or 5.46.

[BrendanGrant]

This eve I noticed some UX changes in Signal on my iPhone and noticed it finally was running 5.46..0.12, and was able to reproduce this issue with it as well, a few times.

[BrendanGrant]

This is still an issue in 5.51.2.0 on iOS 16 on the same device.