Hi Team,
I’m working on Adobe Experience Platform Mobile SDK and I’m observing that the ECID’s authenticatedState always remains “ambiguous”, even when I explicitly update it using Identity.updateIdentities().
Identity.getIdentities { adobeIdentityMap ->
val identityMap = IdentityMap()
val ecidItem = adobeIdentityMap
.getIdentityItemsForNamespace("ECID")
?.firstOrNull()
ecidItem?.id?.let { ecid ->
identityMap.addItem(
IdentityItem(ecid, AuthenticatedState.LOGGED_OUT, true),
"ECID"
)
}
identityMap.addItem(
IdentityItem("8772242737", AuthenticatedState.LOGGED_OUT, true),
"customer_id"
)
Identity.updateIdentities(identityMap)
}
n the Edge logs (Griffon / AEP Debugger), I see:
"identityMap": {
"ECID": [{
"id": "50671253568725123056684606969133922995",
"authenticatedState": "ambiguous"
}],
"customer_id": [{
"id": "8772242737",
"authenticatedState": "loggedOut"
}]
}
My questions are:
Why does the ECID remain ambiguous even after explicitly setting AuthenticatedState.LOGGED_OUT?
Is the ECID’s authentication state controlled internally by the SDK and not meant to be changed manually?
Is there any official documentation stating that ECID’s authenticatedState should always remain “ambiguous” in mobile SDKs, while user-specific IDs (like customer_id) should carry the login/logout state?
This is critical for ensuring we send accurate identity data in login/logout flows.
Thanks in advance!