Skip to content

Conversation

imlucas
Copy link
Contributor

@imlucas imlucas commented Oct 25, 2016

The below started appearing when intercom messenger was upgraded
several weeks ago. The root cause is user resource would send
email:‘’ which fails validation on Intercom's API server. If we
instead allow email to default to undefined, no empty string is sent to
intercom’s server and validation passes. After this is merged, we’ll
also need to change models/user.js in Compass.

Failed to load resource: the server responded with a status of 400 (Bad
Request)
Uncaught (in promise
{"type":"error.list","request_id":"anscsvqg0eamtn7i98t0","errors":[{"cod
e":"parameter_invalid","message":"Email can't be blank"}]}

The below started appearing when intercom messenger was upgraded
several weeks ago.  The root cause is user resource would send
`email:‘’` which fails validation on Intercom's API server.  If we
instead allow email to default to undefined, no empty string is sent to
intercom’s server and validation passes.  After this is merged, we’ll
also need to change models/user.js in Compass.

```
Failed to load resource: the server responded with a status of 400 (Bad
Request)
Uncaught (in promise
{"type":"error.list","request_id":"anscsvqg0eamtn7i98t0","errors":[{"cod
e":"parameter_invalid","message":"Email can't be blank"}]}
```
@durran
Copy link
Member

durran commented Oct 25, 2016

LGTM

@imlucas imlucas changed the title Fix Intercom email can't be blank error COMPASS-132: Fix Intercom email can't be blank error Oct 25, 2016
@imlucas imlucas merged commit 258ce02 into master Oct 25, 2016
@imlucas imlucas deleted the fix-intercom-email-cant-be-blank branch October 25, 2016 16:25
imlucas added a commit that referenced this pull request Oct 25, 2016
The below started appearing when intercom messenger was upgraded
several weeks ago.  The root cause is user resource would send
`email:‘’` which fails validation on Intercom's API server.  If we
instead allow email to default to undefined, no empty string is sent to
intercom’s server and validation passes.  After this is merged, we’ll
also need to change models/user.js in Compass.

```
Failed to load resource: the server responded with a status of 400 (Bad
Request)
Uncaught (in promise
{"type":"error.list","request_id":"anscsvqg0eamtn7i98t0","errors":[{"cod
e":"parameter_invalid","message":"Email can't be blank"}]}
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants