[Solved] Gitlab SSO with custom built of the App

I’ve built an Android and iOS app from the source and connected it to the self-hosted server. Gitlab login works on the web app. It also partially works from the mobile app up to the point when you get redirected back to the app. If Mattermost App is installed on the device it opens this one, otherwise, nothing happens or the error Safari cannot open the page because the address is invalid is displayed. Do I need to configure custom app name+location+id for this to work?

Greetings matthaios,

Welcome back to the Mattermost Forums! I’ll be glad to assist you with the issue you’re facing. It seems like you’ve encountered a problem with the GitLab login functionality on the mobile app after being redirected back to the app. Let’s troubleshoot the situation and find a solution together.

The behavior you described indicates that there might be an issue with the deep linking configuration on the mobile app. Deep linking allows the app to handle specific URLs or redirects to bring users to specific screens or actions within the app. To ensure a smooth experience for users, it’s crucial to configure the deep linking settings correctly.

Regarding your question about configuring a custom app name, location, and ID, Mattermost does provide options to customize these settings. However, the issue you’re facing is likely not related to those specific configurations. Instead, we should focus on the deep linking setup.

To resolve this problem, please follow these steps:

  1. Verify that you have set up the deep linking settings correctly in your Mattermost mobile app. This typically involves configuring the associated URL schemes or Universal Links for iOS and Android Intents for Android.
  2. Double-check that the redirect URL specified in your GitLab configuration matches the deep linking configuration you set in the Mattermost app. Make sure it includes the correct URL scheme or Universal Link for iOS, and Intent for Android.
  3. Test the deep linking functionality by opening a web browser on the mobile device and attempting to access the redirect URL directly. This will help identify any potential issues with the deep linking configuration.
  4. If the direct access to the redirect URL works correctly, try clearing the cache and data of the Mattermost mobile app on your device. Then, attempt the GitLab login again to see if the issue persists.
  5. If the issue still persists, please provide more specific details about your Mattermost server version, the steps you followed during the installation, and any relevant error messages or logs you encountered. This information will be helpful for further investigation.

I hope these steps help you resolve the issue with GitLab login on the mobile app. If you have any further questions or encounter any difficulties, please don’t hesitate to reach out. Our team is here to provide you with the necessary assistance.

Best regards,
~Matterbot 1.0

[Disclaimer: This is a new automated response feature we’re testing powered by ChatGPT. Please be aware that this response should be considered as a simulated suggestion and may not always reflect official Mattermost recommendations or support. Use the information provided at your own discretion. Were any of the above suggestions inaccurate? Please feel free to reply with any suggested corrections!]

Had the same problem
After auth page with “Back to GitLab Mattermost” had a link pointing to “mmauth://callback”,
while the ios app was built with mmauthbeta:// URL scheme.

Setting fastlane setting BETA_BUILD to “false” allowed to build an iOS app with mmauth://callback, which registers in iOS and works correctly with after auth redirects.