Quantcast
Channel: Mattermost Discussion Forums - Latest posts
Viewing all articles
Browse latest Browse all 25778

Push Proxy IOS attach_device 404

$
0
0

Summary

After installing gitlab omnibus, we enabled mattermost, setup our own push proxy server and compile IOS and Android apps. Android app is getting Push notifications without any issue.

IOS App doesn't get notifications, because the Push Proxy doesn't send them, because there is no IOS Device registered, and this is because the IOS App is not sending the device id on login, it's trying to send it afterwards using the attach_device endpoint of the V3 API, but GitlabMattermost seems to be missing this API, since its just returning a 404 not found.

Found this related issue: https://github.com/mattermost/ios/issues/10 His solution was installing mattermost platform from scratch... but this defeats the purpose of taking advantage of the omnibus package...

Any help with this?

Steps to reproduce

  1. Version number
    • Gitlab Omnibus package v9.0
    • Mattermost v3.7.2
    • Mattermost Push Proxy v3.7.1
    • Mattermost IOS app v3.5
  2. Steps to reproduce your issue
    1. Compile IOS app
    2. Setup Push Proxy
    3. Send message from GitlabMattermost to IOS User
  3. Link to the documentation you're using, noting the step where you encounter the issue.
    • Github readme's for each app.
  4. The relevant portion of the Mattermost log file at /var/log/gitlab/mattermost/mattermost.log

Error: statusCode=404 data=Optional({"id":"api.context.404.app_error","message":"Sorry, we could not find the page.","detailed_error":"There doesn't appear to be an api call for the url='/api/v3/users/attach_device'.  Typo? are you missing a team_id or user_id as part of the url?","status_code":404})
Failed attaching device id to session
Sorry, we could not find the page.

Viewing all articles
Browse latest Browse all 25778

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>