You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ✅
This image shows that the same property shows a different value when coming from iOS -> ❌
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! 🙏
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>'.
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 ✅
This image shows that the same property shows a different value when coming from iOS -> ❌
package.json:
"react-native": "0.73.1" "mixpanel-react-native": "^2.1.0",
The text was updated successfully, but these errors were encountered: