Summary

This PR allows the user to see their "custom" categories in the sidebar; bringing the mobile app further inline with the web/desktop clients.

It also respects the EnableLegacySidebar setting - when enabled, it displays the existing sidebar. For server versions less than or equal to 5.31.0, the ExperimentalSidebarCategories displays the new sidebar.

Currently UnreadsOnTop is permanently set to true but can now be used to follow user preferences on the mobile app.

To-Do

• [x] Unable to create channels in categories via the latest build
• [x] "More unreads" banner always visible
• [x] Category collapsing multiple triggers
• [x] Sort order not respecting user pref on mobile

Ticket Link

Resolves https://mattermost.atlassian.net/browse/MM-28474

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes
• [x] Includes text changes and localization file updates

Device Information

This PR was tested on:

• iPhone 12 (Simulator) / iOS14
• Google Nexus 4 (Simulator) / Android 29

Screenshots

https://user-images.githubusercontent.com/456511/126950557-ac732cc1-bece-4562-89fc-a848f9de8cc9.mov

Release Note

App now displays custom categories in the sidebar.

Summary

• Mobile Custom User Statuses

Ticket Link

• Development Spec - https://mattermost.atlassian.net/wiki/spaces/CS/pages/1096810497/Development+Spec
• Figma design: https://www.figma.com/file/9OsvCq4z83xH0Vd6e68Ls9/MM-24340-Custom-Statuses?node-id=810%3A23968
• JIRA - https://mattermost.atlassian.net/browse/MM-34586

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes
• [x] Includes text changes and localization file updates

Device Information

This PR was tested on:

• iPhone 11 Pro Simulator - iOS 14.4
• Android Emulator - Pixel_3a_API_30_x86 - Android 10

Screenshots

Release Note

Added the custom status feature support for the RN mobile apps. Mattermost server v5.36+ is required to access custom statuses on mobile.

Summary

This PR removes auto-scrolling to the new message line on channel load and adds a "More Messages" button when there are unread posts. The unread post count is calculated on channel switch from the difference channel.total_msg_count - member.msg_count and with the addition of any inserted non-message posts (ie, date line) by makePreparePostIdsForPostList. On press of the button the user is scrolled to the index of the new message line or to the index of the highestMeasuredFrameIndex if the new message line post has not yet been measured. If there are no more unread messages the button is hidden, otherwise the unread count is updated and pressing again will scroll to the updated index of the new message line or the next highestMeasuredFrameIndex.

Because we don't want a new message line to be added when a user submits their own post either in the current channel or in another channel from separate client, there was a previous condition added in makeFilterPostsAndAddSeparators to not add the new message line if the post's user_id is the current user's ID. This was problematic for this feature as the index of the final new message line would not coincide with the index of the last unread message and so in this case the "More Messages" button would never hide. To get around this I added an ownPost property to Post. When RECEIVED_POST or RECEIVED_NEW_POST actions are handled, if the post is the current user's post then the channel's lastChannelViewTime is updated to be the post's created_at value + 1, ensuring that the new message line is not added since the existing condition post.create_at > lastViewedAt will be false.

Ticket Link

https://mattermost.atlassian.net/browse/MM-23761 https://mattermost.atlassian.net/browse/MM-25766

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes
• [x] Includes text changes and localization file updates

Device Information

This PR was tested on:

• iOS 13 simulator and iPhone SE
• Android Q emulator and Mi A3 running Android 9

Summary

Since upgrading my S20 plus to the new android 11 update, the app appears to perform super slow. I have also attached a view, and the low fps you will see is not from the recording, but from only the mattermost app.

Environment Information

• Device Name: Samsung Galaxy S20 Plus
• OS Version: Android 11
• Mattermost App Version: 1.38.0
• Mattermost Server Version: 5.26.0

Steps to reproduce

Have an S20 with the latest update, install mattermost app and try to use anything, you will notice the sluggish behaviour

Expected behavior

Before the upgrade, the app used to work very fast and was performing well.

Observed behavior

Doesn't matter which channel or team, once I open the app every thing is very low performance Video the online preview makes it a bit hard to see the difference, try to download the file to best see the issue

Possible fixes

If you can, link to the line of code that might be responsible for the problem.

Summary

Adds dark and light themes to server select, login options, and login screen.

I couldn't find all the colours listed in the mock, so I just used the Digital Color Meter to get the approximate colours and created a colours file to keep them all together and hopefully simplify the scheme. If you'd like to change the the colours to use opacities instead, could you please describe the new colours relative to app/styles/colors.js?

Instead of updating the theme, which has different keys from the ones needed for these few pages, I created objects filled with colours for light and dark schemes in app/styles/colors.js. In the future, maybe these can be integrated with themes, but I don't know enough about the themes to do that yet.

There's a lot to be updated still! I could really use some fresh eyes and expertise to finish this up. Thanks in advance!

Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/11947

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes

Device Information

This PR was tested on: iPhone X and Android Nexus_5X_API_29_x86 simulators

Screenshots

Summary

After login, signal 11 (null) message appears and closes the app.

Environment Information

• Device Name:
• OS Version: 10.3.2
• Mattermost App Version: 1.9.0
• Mattermost Server Version: 5.0.0

Summary

I think the iOS build process does not always take into account the variables from .env file for the signing part. I have an error during signing, since the build is trying to use the default profile instead of mine.

Environment Information

I'm using macOS Sierra, latest version of Fastlane (2.85.0) and I cloned the project at this commit : https://github.com/mattermost/mattermost-mobile/commit/1f7ec077860a040e23303481d086939b90e60f75

Observed behavior

When I want to build the app, the process will fail when signing with these errors :

[16:05:47]: ▸ Code Signing Error: Provisioning profile "iOS Team Provisioning Profile: *" doesn't include signing certificate "iPhone Developer: Nicolas furno (********)".
[16:05:47]: ▸ Code Signing Error: Provisioning profile "iOS Team Provisioning Profile: *" doesn't support the App Groups capability.
[16:05:47]: ▸ Code Signing Error: Provisioning profile "iOS Team Provisioning Profile: *" doesn't support the group.******.mattermost App Group.
[16:05:47]: ▸ Code Signing Error: Provisioning profile "iOS Team Provisioning Profile: *" doesn't include the com.apple.security.application-groups entitlement.
[16:05:47]: ▸ Code Signing Error: Code signing is required for product type 'App Extension' in SDK 'iOS 11.2'

When opening the project in Xcode just after these error, here's what I noticed : the default app ID is used, instead of the one I used in my .env file.

If I edit manually the project.pbxproj file to search all default values and replace these with mine, the build is working fine.

I guess there is a bug somewhere, that prevents the build process to extract the correct values during the build ?

Let me know if you need more information.

Summary

Add a text setting widget, refactor menu action selector to be more reusable and add interactive dialogs.

Ticket Link

https://mattermost.atlassian.net/browse/MM-12845

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes
• [ ] Includes text changes and localization file updates

Device Information

iOS Simulator Galaxy S9

Summary

This PR adds support for dark mode and light mode syncing with OS theme setting

Ticket Link

https://github.com/mattermost/mattermost-server/issues/15975

Checklist

• [x] Added or updated unit tests (required for all new features)
• [x] Has UI changes
• [x] Includes text changes and localization file updates

Device Information

This PR was tested on: iPhone 8 (device), iOS 14.6 iPad Pro 12.9-inch 4th gen. (device), iOS 14.6 iPhone 12 (emulator), iOS 14.5 iPhone 6 (emulator), iOS 12.4 Pixel XL (emulator), Android 10.0 API 29

Also added e2e tests.

Screenshots

https://user-images.githubusercontent.com/8155563/130352095-ad45e4ac-a972-471a-8dcb-5d7f3c98000f.mp4

https://user-images.githubusercontent.com/8155563/130353114-5359e133-4c2a-4031-852c-61ad9fb2aa83.mp4

When OS not supports dark theme, app fallbacks to light:

Release Note

Added support for dark mode and light mode syncing with OS theme setting

Summary

Add multiselect support to Mobile

Ticket Link

https://mattermost.atlassian.net/browse/MM-34194

Screenshots

Release Note

Add multiselect support for Apps Forms

Summary

When createPost is called all the emojis would be extracted Emojis available with mattermost will be filtered. Update recent reactions with filtered emojis.

Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/12750

Device Information

This PR was tested on: RedmiNote 8, Android

Screenshots

Used an emoji in a post.

Recent emojis got updated

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.

For troubleshooting see: http://forum.mattermost.org/. For feature proposals see: http://www.mattermost.org/feature-requests/

If you've found a bug--something appears unintentional--please follow these steps:

1. Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
2. Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
3. File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary

Bug report in one concise sentence

Environment Information

• Device Name:
• OS Version:
• Mattermost App Version:
• Mattermost Server Version:

Steps to reproduce

How can we reproduce the issue (what version are you using?)

Expected behavior

Describe your issue in detail

Observed behavior (that appears unintentional)

What did you see happen? Please include relevant error messages, screenshots and/or video recordings.

Possible fixes

If you can, link to the line of code that might be responsible for the problem

Summary

Hi everyone, I'm downloading source code from Mobile Version 1.55.1 released, but I'm can't build android app. Can anyone help me? Thank for all

Environment Information

• Device Name: Macbook pro M1
• OS Version: Macos Monterey
• Mattermost App Version: 1.55.1

Steps to reproduce

Step 1: Dowload source code from Mobile Version 1.55.1 released Step 2: run: npm install Step 3: run: react-native run-android

Expected behavior

Can run android app on simulator

Observed behavior (that appears unintentional)

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
   > The minCompileSdk (31) specified in a
     dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
     is greater than this module's compileSdkVersion (android-30).
     Dependency: androidx.appcompat:appcompat:1.4.1.
     AAR metadata file: /Users/hungnguyen/.gradle/caches/transforms-3/f6cf9637d2f604e9f80955c01bd68647/transformed/appcompat-1.4.1/META-INF/com/android/build/gradle/aar-metadata.properties.

If manual fix with remove minCompileSdk = 31 from aar-metadata.properties after that re-run react-native run-android command and another file will encounter the same problem.

added a letter

Summary

Ticket Link

Checklist

• [ ] Added or updated unit tests (required for all new features)
• [ ] Has UI changes
• [ ] Includes text changes and localization file updates
• [ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information

This PR was tested on:

Screenshots

Release Note

Summary

• Use RTCPeer (as close as possible -- some changes needed: importing types from react-native-webrtc package, and being explicit about some types to make typescript happy).
• Stop using our fork of react-native-webrtc and use the up-to-date upstream release.
• Everything works after multiple tests: muting-unmuting, sharing-resharing screens.
• This lets us easily move to glare-free negotiation 🎉 (I have it in another branch, just have to setup calls/rtcd to the right versions and test).

Ticket Link

• https://mattermost.atlassian.net/browse/MM-46312
• https://mattermost.atlassian.net/browse/MM-42553

Checklist

• [ ] Added or updated unit tests (required for all new features)
• [ ] Has UI changes
• [ ] Includes text changes and localization file updates
• [ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information

• Android: 13, Pixel 6
• iOS: 15.7, iPhone 7 plus

Release Note

Calls: update react-native-webrtc to most recent version

Summary

Clean several todos in the code, and add relevant tickets.

Ticket Link

https://mattermost.atlassian.net/browse/MM-43482 https://mattermost.atlassian.net/browse/MM-43487

Release Note

NONE