Task/sdk 3814/user attribute triggering

[Anush-Shand]

@CTLalit @piyush-kukadiya

DeviceID null possibilitites

DeviceId not initialised yet and onUserLogin performed

• onUserLogin will return before doing any operation because of deviceID null check

DeviceId not initialised yet and pushProfile/increment etc. is called

• pushProfile will not be able to cache the guid (same behaviour as existing if deviceId is not initialised yet)
• The event will be queued as is
• New updated profile will be saved in cache but not in db as profile is not inflated yet

DeviceId initialised but pushProfile / onUserLogin called before profile is inflated in cache

• Since local cache is synchronised, it will wait for inflating and only then move to evaluation and computing new values

New deviceID will always be generated first before inflating profile for asynProfieSwitchUser

[Anush-Shand]

Reopening with another branch