React-Native iOS - Error in loginUserWithUserAttributes

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.

We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.

A short stack-trace for the error we receive:

code: 102,
domain: io.intercom.ios.error.network,
message: Error in loginUserWithUserAttributes,
name: Error,
NSLocalizedDescription: HTTP Error: 400 bad request

We send email and userId to the method call, like this:
Intercom.loginUserWithUserAttributes({ email, userId })

Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

Be the first to reply!

Hey @Dev Planable, Emily here from Support Engineering at Intercom 👋🏼

A 400 Bad Request error with code 102 when calling Intercom.loginUserWithUserAttributes in the React Native SDK can be caused by several factors:

If you send both email and userId, you must calculate the HMAC (user hash) for identity verification using the userId value, not the email. If the HMAC is calculated incorrectly, authentication will fail.
Both email and userId must be valid, non-empty strings. Double-check that neither is undefined or null.
Ensure all attribute values match the expected types and formats. For example, if a field is defined as a number or date, sending a string or incorrectly formatted value can cause a 400 error.

To resolve:

Confirm both userId and email are valid, non-empty strings.
If using identity verification, ensure the HMAC is generated from userId if both are present.
Check that all attribute values match the expected types and formats.

Hope this helps! 💪🏼

Hey @Emilygav -- this is happening to us a ton as well and is polluting our Bugsnag. In our case however, we are just passing userId: `await Intercom.loginUserWithUserAttributes({ userId });`

And then we get an error that looks like this

code
102

domain
io.intercom.ios.error.network

userInfo
{
"NSLocalizedDescription": "HTTP Error: 400 bad request"
}

As I mentioned, it’s happening a ton and is quite frustrating, so any help on the matter would be very much appreciated!

A 400 Bad Request in loginUserWithUserAttributes usually means Intercom expects either userId or email but not both in some configurations. Make sure your Intercom app is set to identify users by the field(s) you’re sending. Also, check for:

email format correctness (no extra spaces)
userId uniqueness and length (<255 chars)
SDK initialization completed before login call

Try calling Intercom.registerIdentifiedUser({ userId }) or just { email } depending on your setup to see if that resolves the 400 error.

Hi @richardcole

I can confirm that were are *just* passing userId

`await Intercom.loginUserWithUserAttributes({ userId });`

Can I please get this escalated to someone on the development team, it’s killing us.

Bump on this please

We are running into the same issue, with no explicit error in production other than the 400, and unable to reproduce in development.

We do not have JWT or Identity Verification enabled, so that shouldn’t be causing the 400. Please advise.

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded