setUserContext doesn't work

[haikov]

OS:

• Windows
• MacOS
• Linux

Platform:

• iOS
• Android

Output of node -v && npm -v && npm ls --prod --depth=0

v7.8.0
4.2.0
[email protected] ...
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Config:

Sentry.config('https://[email protected]/...', {
  logLevel: SentryLog.Verbose,
}).install();

---

I have following issue:

setUserContext doesn't work for me. After user login event in the app I call the setUserContext function:

Sentry.setUserContext({
    id: userId,
});

Then, in debug console I see

But after any crash, on my Sentry dashboard, I see userId as an ip address.

[HazAT]

Hey, so can you upgrade to the latest version.
I am pretty sure this bug has already been fixed, please be aware that in the latest version 0.32.0 uses the new @sentry/cli npm package, so you slightly have to adjust your build process.

But I think version 0.31.0 or 0.30.3 should also work.

[haikov]

@HazAT thank you for the prompt reply!

Just updated to the 0.31.0 version but it didn't help. Interesting thing that setTagsContext works and I see it in my Sentry dashboard's breadcrumbs log as

But I don't see setUserContext there (but I still see it in my local Chrome console)

[haikov]

I've found that for some reasons it's losing the userContext after application reloading. If I do the following way:

1. Do user login and call setUserContext with user id (I see setUserContext in the logs)
2. Reload an application (with CMD+R in development mode)
3. Click some button to generate an exception

I don't get userId stored in the Sentry dashboard. Is it an expected behavior (I don't think so because it was working previously)?

It works if I do the following way:

1. Use componentWillReceiveProps in App component to determine when the state gets rehydrated from redux-persist
2. Call setUserContext once it's changed

[HazAT]

@gaykov can you try to patch the RNSentry.m locally in you node_modules and see if it works:
#315

[haikov]

@HazAT didn't help, I still see an ip address as a user identifier. And the error in Sentry dashboard looks different from others:

[HazAT]

OK, there must is something weird going on in your setup.
I tried it locally and it works as expected in the example project we have
https://github.com/getsentry/examples/tree/master/react-native

Can you link me to your source somehow because I am not really able to reproduce it?!

[HazAT]

I will close this for now since I wasn't able to reproduce it.
Please feel free to reopen it whenever you are able to provide a reproducible case.