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
Fixed a few bugs and crashes around media interactions #929
Fixed a few bugs and crashes around media interactions #929
Conversation
Fixed a crash when trying to grant permission to access additional photos Fixed a bug where audio files would incorrectly get recognised as voice messages Replaced our custom video/audio players with the native ones (which have additional built-in controls) Updated the errors from SSKKeychainStorage to include useful information Updated layout for audio attachments
Fixes #748 |
@@ -788,13 +789,30 @@ extension Attachment { | |||
public var isText: Bool { MIMETypeUtil.isText(contentType) } | |||
public var isMicrosoftDoc: Bool { MIMETypeUtil.isMicrosoftDoc(contentType) } | |||
|
|||
public var documentFileName: String { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to localise these default file names?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea probably but they already weren't localised so I wanted to try to minimise changes - since the Strings
project is progressing separately in the background I wanted to avoid adding to much additional localisation since it's going to be re-done as it's own project in the future
Hopefully with the updated LintLocalizableStrings
it'll be a lot easier to identify all of the unlocalised strings that are missing and we can look to add them as part of the Strings
project
Some example screenshots (left is old, right is new)