silly-dinner-68354
06/03/2022, 6:58 AMsetAttributes
will be reflected. We ended up using a stable unique-per-device identifier as the user ID, but it makes LD pretty unpleasant to use.
Is this something GrowthBook has come across? Do other people handle this situation differently? Would really appreciate any battle stories. 🙂fresh-football-47124
silly-dinner-68354
06/03/2022, 7:25 AMsetAttributes
).fresh-football-47124
silly-dinner-68354
06/03/2022, 7:40 AMOS is not "android"
and I logged into the iOS device most recently, then presumably the behaviour of that condition will be affected on the Android device too.fresh-football-47124
silly-dinner-68354
06/03/2022, 7:42 AMfresh-football-47124
silly-dinner-68354
06/03/2022, 7:44 AM${userID}-${platform}
as my key, but then I end up with duplicate users in the dashboard.fresh-football-47124
silly-dinner-68354
06/03/2022, 7:45 AMfresh-football-47124
silly-dinner-68354
06/03/2022, 7:46 AMsetAttributes
is that local-only data?fresh-football-47124
silly-dinner-68354
06/03/2022, 7:50 AMsetAttributes
are also synced to a server?setAttributes({platform: currentPlatform})
on two devices with different platforms, one after the other, then each device will have the correct platform, but whatever is synced to the server will only reflect the last write?fresh-football-47124
silly-dinner-68354
06/03/2022, 8:59 AM