Landscape orientation issues when sending or recording media

[XxBlackHatxX]

• 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

When moving the phone in landscape while sending ANY type of media or in the middle of recording a VM the action current action will stop.

Steps to reproduce

Scenario 1
Send a photo, video, or VM in portrait mode. While the media is still uploading move the device to landscape. The media will stop uploading and then start over.

Scenario 2
Start recording a voice message in portrait mode. While still recording even with recording lock on turn the device to landscape. The recording will be deleted and you will need to start from the beginning.

Actual result:
Scenario 1
The media will stop uploading and then start over.

Scenario 2
The recording will be deleted and you will need to start from the beginning.

Expected result:
Scenario 1
The media will still continue to upload no matter how many times you turn the device.

Scenario 2
If recording lock IS OFF the recording will stop but you will still be able to send or delete it.
If recording lock IS ON the recording will continue regardless of how many time you rotate the device.

Screenshots

Device info

Device: iPhone 11

iOS version: 14.1

Signal version: 3.21.0.10

Link to debug log

[4ndre4s]

I have the same problem.

iPhone 12 Pro Max
iOS 14.4
Signal Version 5.5.0

[elahmo]

I am having this issue since I started using signal, and I want to literally break my phone and stop using technology completely when this happens.

It is the MOST ANNOYING THING IN THE WORLD SPEAKING FOR 3 MINUTES AND THEN SUDDENLY TILTING PHONE A BIT AND SEEING IT VIBRATE BECAUSE SIGNAL THOUGHT I WANTED TO CHANGE TO LANDSCAPE IN A MIDDLE OF A VOICE RECORDING. HAVING TO REPEAT WHAT YOU WERE SAYING IS ONE OF THE MOST DIFFICULT THINGS IN THE WORLD

Please fix this.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[elahmo]

It is not relevant, most of the people I know have moved away from Signal due to terrible UI. It's a shame but issues like this that are open for years are a reflection of how neglected the actual app is.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[elahmo]

No one cares about Signal anymore. Bugs like this make people use any other viable option since it is obvious the foundation or developers do not care enough about a platform that has billion of users.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[NiklasBr]

Yes

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[elahmo]

Thanks bot!

It's a shame that a great project like this suffers from childish bugs, such as this one, which end up preventing mass adoption of it.

[tr1ng0]

This is fixed since version v5.47 see: #5404

[elahmo]

Great! Glad to see it fixed, a bit sad it took two years.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[EvanHahn-Signal]

Looks like this was fixed. Closing this issue.

Please open a new one if you're still running into problems.