Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Null values have different behavior based on platform (Android, IOS) #221

Open
ianvasco opened this issue Jan 25, 2024 · 2 comments
Open

Comments

@ianvasco
Copy link

I'm trying to unify the implementation and all of the analytics to match the web data. It turned out that the properties sent from Android with a null value are showing (not set), which is expected (the same as the web). On the other hand, properties that are sent from iOS with a null value are showing <null>,

In the following image you can see Arranged For property is (not set) -> this is Android and this is the expected ✅
image

This image shows that the same property shows a different value when coming from iOS -> ❌
image

package.json:
"react-native": "0.73.1" "mixpanel-react-native": "^2.1.0",

@zihejia
Copy link
Contributor

zihejia commented Mar 2, 2024

hi @ianvasco , sorry for the late response. if you need 100% parity, you can our latest beta version and use the Javascript mode. Please refer to the release notes at Mixpanel React Native v3.0.0-beta.1. welcome to report any issues or provide feedback! 🙏

@johnpkennedy
Copy link

johnpkennedy commented May 15, 2024

We also encountered this problem. Like @ianvasco, we're also trying to unify our analytics to make it easy for people to use.

Our application also uses the React Native SDK. We confirmed that our application code correctly passes the value null on Android and IOS platforms.

However, based on what we see in the Mixpanel interface, the null event properties that are captured on iOS are converted into a string and displayed as '<null>'.

As a result of this problem, we find non-technical users struggle to use filters and understand breakdowns because null (not set) is not the same as '<null>'.

When will this be fixed?

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

No branches or pull requests

3 participants