- TypeScript 92.1%
- Kotlin 2.9%
- Swift 2.7%
- JavaScript 0.9%
- Ruby 0.6%
- Other 0.8%
mohlec
aeed7f68f2
All checks were successful
Build Slash Android APK / build-android (push) Successful in 7m55s
DEV-ONLY tool for the current testing phase - not intended for production, see inline warnings and PRD Phase 5 notes on where to disable/remove before release. No Sentry or other 3rd-party crash reporting was wired up, leaving zero diagnostic trail for issues like the recent Android background-crash bug (root-caused entirely from code review + user reports, no stack trace available). This adds a minimal in-house alternative reusing existing infra - no new servers, no new HAProxy routes: - A private 'Crash Reports' Mattermost channel + incoming webhook receive reports (webhook already tested working: POST to https://chat.ncwcom.com/hooks/zgbotadhbintjps66d7erbqgte) - app/utils/crash_report.ts: shared JS logic - ErrorUtils.setGlobalHandler hook for JS-level errors, posts device info + stack trace to the webhook - Android (MainApplication.kt): Thread.setDefaultUncaughtExceptionHandler writes crash details to a local file synchronously (safe during process teardown) rather than attempting a network call mid-crash, then chains to the previous handler to preserve normal crash/termination behavior - iOS (AppDelegate.mm): NSSetUncaughtExceptionHandler does the same for Objective-C/Swift exceptions. Hard native crashes (signals) are intentionally out of scope - correctly catching those requires a real signal handler, which is fragile to hand-roll and not worth it for a dev-only tool - On next app launch, JS checks for a pending native crash file and uploads it if present (app/init/app.ts) - New GLOBAL_IDENTIFIERS.CRASH_REPORTING_ENABLED WatermelonDB flag (app/queries+actions/app/global.ts), default on, absent record treated as enabled - Settings toggle added to Advanced Settings screen, off switch persists immediately Known limitation: webhook URL is embedded in the client config (assets/base/config.json), same exposure model as the existing SentryDsn*/RudderApiKey fields already in that file - extractable from the compiled app, but only grants write access to one private channel. Acceptable for the dev/test phase per user sign-off; flagged for removal before production. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| .husky | ||
| android | ||
| app | ||
| assets | ||
| build/notice-file | ||
| detox | ||
| docs | ||
| eslint | ||
| fastlane | ||
| ios | ||
| libraries/@mattermost | ||
| patches | ||
| scripts | ||
| share_extension | ||
| test | ||
| types | ||
| .buckconfig | ||
| .editorconfig | ||
| .flowconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .node-version | ||
| .npmrc | ||
| .nvmrc | ||
| .ruby-version | ||
| .solidarity | ||
| .watchmanconfig | ||
| app.json | ||
| babel.config.js | ||
| CHANGELOG.md | ||
| CLAUDE-IOS-SIMULATOR.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| env.d.ts | ||
| eslint.config.mjs | ||
| Gemfile | ||
| Gemfile.lock | ||
| index.ts | ||
| ISSUE_TEMPLATE.md | ||
| jest.config.js | ||
| jsconfig.json | ||
| LICENSE.txt | ||
| metro.config.js | ||
| NOTICE.txt | ||
| package-lock.json | ||
| package.json | ||
| PULL_REQUEST_TEMPLATE.md | ||
| react-native.config.js | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.json | ||
| tsconfig.test.json | ||
Mattermost Mobile v2
- Minimum Server versions: Current ESR version (10.11.0+)
- Supported iOS versions: 16.0+
- Supported Android versions: 7.0+
Mattermost is an open source Slack-alternative used by thousands of companies around the world in 21 languages. Learn more at https://mattermost.com.
You can download our apps from the App Store or Google Play Store, or build them yourself.
We plan on releasing monthly updates with new features - check the changelog for what features are currently supported!
Important: If you self-compile the Mattermost Mobile apps you also need to deploy your own Mattermost Push Notification Service.
Android 16KB Page Size Support
Temporary Requirement: To comply with Google Play's 16KB page size requirement for Android devices, this project includes a compatibility patch that must be applied before building for Android.
When to Apply the Patch
- CI/CD Builds: The patch is automatically applied in GitHub Actions for Android builds
- Local Development: If you're building Android locally and encounter 16KB page size related issues, run:
npm run apply-16kb-pagesize-patch
This script will:
- Update package dependencies to compatible versions
- Apply necessary code changes for 16KB page size support
- Update patch files for modified dependencies
- Regenerate
package-lock.json
⚠️ Important Warnings
- DO NOT commit the changes applied by this patch to the repository
- These changes will break iOS builds if committed
- The patch is designed to be applied only during Android CI builds
- For local development, revert all changes after building Android
Note: This is a temporary solution until all dependencies natively support 16KB page sizes.
How to Contribute
Testing
To help with testing app updates before they're released, you can:
- Sign up to be a beta tester
- Install the
Mattermost Betaapp. New updates in the Beta app are released periodically. You will receive a notification when the new updates are available. - File any bugs you find by filing a GitHub issue with:
- Device information
- Repro steps
- Observed behavior (including screenshot / video when possible)
- Expected behavior
- (Optional) Sign up for our team site
- Join the Native Mobile Apps channel to see what's new and discuss feedback with other contributors and the core team
You can leave the Beta testing program at any time:
- On Android, click this link while logged in with your Google Play email address used to opt-in for the Beta program, then click Leave the program.
- On iOS, access the
Mattermost Betaapp page in TestFlight and click Stop Testing.
Contribute Code
- Look in GitHub issues for issues marked as [Help Wanted]
- Comment to let people know you’re working on it
- Follow these instructions to set up your developer environment
- Join the Native Mobile Apps channel on our team site to ask questions
Frequently Asked Questions
How is data handled on mobile devices after a user account is deactivated?
App data is wiped from the device when a user logs out of the app. If the user is logged in when the account is deactivated, then within one minute the system logs the user out, and as a result all app data is wiped from the device.
I need the code for the v1 version
You can still access it! We have moved the code from master to the v1 branch. Be aware that we will not be providing any more v1 versions or updates in the public stores.
Troubleshooting
I keep getting a message "Cannot connect to the server. Please check your server URL and internet connection."
This sometimes appears when there is an issue with the SSL certificate configuration.
To check that your SSL certificate is set up correctly, test the SSL certificate by visiting a site such as https://www.ssllabs.com/ssltest/index.html. If there’s an error about the missing chain or certificate path, there is likely an intermediate certificate missing that needs to be included.
Please note that the apps cannot connect to servers with self-signed certificates, consider using Let's Encrypt instead.
I see a “Connecting…” bar that does not go away
If your app is working properly, you should see a grey “Connecting…” bar that clears or says “Connected” after the app reconnects.
If you are seeing this message all the time, and your internet connection seems fine:
Ask your server administrator if the server uses NGINX or another webserver as a reverse proxy. If so, they should check that it is configured correctly for supporting the websocket connection for APIv4 endpoints.