This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I can’t pair my garmen with my Noom App as when accepting the terms it is showing an error code

3729079 over 4 years ago

I can’t pair my Garmin watch with Noom app as when accepting the terms it comes up with an error code

Top Replies

Garmin-Blake over 4 years ago +1 verified

This issue has been escalated and we are actively looking into the cause/a permanent resolution.

There are some questions it would be helpful to ask users who are experiencing this, and we may need to…
Drewsville over 4 years ago +1

I have the same problem, once I tap agree it goes to sync my device.com and shows error code 404 page not found
fallingrock over 4 years ago +1

I suspect you should contact the Noom support team.

All Replies

0 Boeregarde over 4 years ago in reply to Garmin-Blake

Consent given.

0 2382972 over 4 years ago in reply to Garmin-Blake

I’m having this problem too! Would love assistance. Thank you :)

0 Former Member over 4 years ago in reply to Garmin-Blake

Please send me an update too. I currently use the most recent version of the app for iOS.

0 9161401 over 4 years ago

I had same error message -404.
Disconnect your Garmin app then reinstall it. You will be able to connect to Noom.

0 9161401 over 4 years ago

I had same error-404 page not found.
Disconnect the Garmin app then reinstall it. Turn in share all data and then follow the connection steps on Noom. It will connect.

0 9161401 over 4 years ago in reply to 9161401

Turn on..

0 2431248 over 3 years ago

I have been having trouble with this forever. I tried everything and eventually Connect even disappeared as an option from Noom. I removed and reinstalled the Connect App and once it synched it was back in Noom and showed the correct steps. Hopefully it lasts.

0 Shephardscrook over 3 years ago in reply to Garmin-Blake

Please email me

0 ITS_KJH over 3 years ago in reply to Garmin-Blake

It is June 2022, have this issue been resolved?