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
Describe the bug
Me and the team have identified the difference between iOS and Android SDK behaviours, when we added a custom value to the traits payload using identify(traits:) interface.
Then, during using Segment Debugger, I can see traits are attached to indentify event (expected), but they're not attached to any of other events - track, lifecycle.
Android SDK has pretty much the same integration code, but we can confirm the fact we see traits for every event that follows the identify one.
To Reproduce
Steps to reproduce the behavior:
Launch the application with the valid Segment configuration
If you're looking for context.traits on non-identify events, this was by design to match analytics.js. See /examples/other_plugins/InjectTraits for an example of how to replicate the analytics-ios behavior.
Describe the bug
Me and the team have identified the difference between iOS and Android SDK behaviours, when we added a custom value to the
traits
payload usingidentify(traits:)
interface.Then, during using Segment Debugger, I can see traits are attached to
indentify
event (expected), but they're not attached to any of other events -track
,lifecycle
.Android SDK has pretty much the same integration code, but we can confirm the fact we see
traits
for every event that follows theidentify
one.To Reproduce
Steps to reproduce the behavior:
identify(userId: yourUserId, traits: ["customField": "value"])
track
events after.identify
event - you can seetraits
are attached to ittrack
eventExpected behavior
Every track events from the step three should have
traits
attached.Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: