[akhiljain1907]

Description

Adds Identity.updateOperationalData(_:). It sends operational data, such as the timezone, push token and Live Activity push-to-start tokens, to the Edge Network whatever the collect consent. Only values allowed by a Tags rule are sent, and only when they changed. Behavior matches Edge Identity Android (adobe/aepsdk-edgeidentity-android#155).

Public API

• Swift: Identity.updateOperationalData(_ attributes: [String: Any])
• Objective-C: [AEPMobileEdgeIdentity updateOperationalData:] (NSDictionary<NSString *, id> *)
• An empty map is ignored. Values are not validated and are sent as given.

Flow

1. The API dispatches edgeIdentity / com.adobe.eventSource.requestOperationalData. Edge Identity matches the event on type and source, not name.
2. Edge Identity forwards the data to the rules engine as com.adobe.eventType.generic.operationalData / requestContent.
3. A rule with the forward-operational-data consequence (AEPCore 5.13.0) returns only the allowed paths as edgeIdentity / com.adobe.eventSource.responseOperationalData. If no rule matches, nothing is sent and no result event is dispatched.
4. Edge Identity removes unchanged values, adds app { id: <bundle id>, platform: apns | apnsSandbox } (from messaging.useSandbox), and dispatches com.adobe.eventType.edgeDeviceAttributes / requestContent. The Edge extension sends this to the device attributes endpoint.
5. One request is in flight at a time. The next one is sent when the Edge response (edgeDeviceAttributes / responseContent) for the active request arrives, whatever its status.

Deduplication (edgeidentity.optimizeOperationalProfileDataSync, default true)

• Only timezone, tokens.pushNotification and tokens.liveActivityStart are deduplicated and stored. Push-to-start tokens are compared ignoring order. All other values, including tokens.liveActivityUpdate, are always sent and never stored.
• A value is skipped when it matches the value Edge last confirmed, whatever the collect consent.
• When collect consent is y, or the Consent extension is not registered, a value is also skipped when it matches what its owner already holds: the timezone set through MobileCore.updateProfileAttributes, or Messaging's push token and push-to-start tokens. That value is stored as confirmed.
• Confirmed values are stored in the com.adobe.mobilecore.operationalData collection. They are cleared by resetIdentities. Push-to-start tokens are also cleared when Messaging clears Live Activities.

Events and shared state

• Each request ends with one Operational Data Sync Result event (edgeIdentity / responseContent) containing {status, reason, attributes}.
  • reason is "" on success.
  • When nothing is sent to Edge, reason is unchanged, identityReset or missingAppIdentifier.
  • Otherwise, on failure, it is Edge's reason, or unknown.
• On success, if tokens were sent, an Operational data confirmed event (messaging / responseContent, {tokens}) is dispatched for Messaging.
• A confirmed timezone also updates the profile attributes timezone.
• Confirmed values, merged with the profile timezone, are published in the standard shared state under profileAttributes. At registration this is published only when something is stored.

Changes to existing behavior

• Profile attributes (updateProfileAttributes, released in 5.1.0): an XDM shared state is created only when the timezone actually changes. Previously, every profile attributes event resolved a pending XDM shared state. The XDM com.adobe.mobilecore.profileAttributes.timeZone content is unchanged.
• AEPCore dependency raised to >= 5.13.0 in AEPEdgeIdentity.podspec and Package.swift. Podfile.lock updated to Core 5.13.0 and AEPIdentity 5.13.0 (test dependency).
• Version is 5.2.0 (base dev-v5.2.0).

Dependencies for release

• Requires an Edge extension that handles com.adobe.eventType.edgeDeviceAttributes (Isolated consent-independent device-attributes endpoint path to Edge Network aepsdk-edge-ios#547). Edge Identity cannot declare Edge as a dependency, because Edge already depends on Edge Identity. With an older Edge, the request gets no response, and later requests wait behind it.
• Release order: AEPCore 5.13.0 (released), then this release, then Edge with #547, with its AEPEdgeIdentity dependency raised to this version.
• Messaging must match the Operational data confirmed event by type, source and tokens, not by event name.

Related Issue

MOB-25063. Supersedes #149 and #154. Android: adobe/aepsdk-edgeidentity-android#155. Edge: adobe/aepsdk-edge-ios#547.

Motivation and Context

The timezone, push token and Live Activity push-to-start tokens are operational data that must reach the profile even without collect consent. The existing profile and Messaging paths are consent-gated. This API sends these values through Edge's dedicated device attributes endpoint, but only the values a Tags rule allows. It does not resend values that have not changed, and it reports every outcome so callers and Messaging can react.

How Has This Been Tested?

New tests:

• IdentityOperationalDataTests (93): routing, app, deduplication and the config flag, owner comparison at every consent state, the queue and response matching, result and confirmed events, reset, shared state and Live Activity clear.
• OperationalDataDeduplicatorTests (16).
• Two tests in IdentityPublicAPITests. IdentityTimezoneTests and IdentityTests are updated for the profile attributes shared-state change.

Local runs on Xcode 26.3, iPhone 16 simulator (iOS 18.4):

• xcodebuild test -workspace AEPEdgeIdentity.xcworkspace -scheme UnitTests: passed, 149/149, at 9400880. The code is identical to 65094c6 apart from the 5.2.0 version bump.
• xcodebuild test -workspace AEPEdgeIdentity.xcworkspace -scheme FunctionalTests: passed, 144/144, at 9400880.
• make lint: passed, no violations, at 9400880.
• xcodebuild test ... -only-testing:FunctionalTests/EdgeIdentityAndIdentityDirectTests: passed, 8/8, at 65094c6.
• Temporary, not committed, run at 65094c6:
  • Objective-C caller .m in UnitTests: passed, 4/4. The generated header declares + (void)updateOperationalData:(NSDictionary<NSString *, id> * _Nonnull)attributes;.
  • Scenarios through AEPCore 5.13.0's real LaunchRulesEngine with a forward-operational-data rule: passed, 23/23. They cover all, push-only, timezone-only and no attributes enabled, no matching rule, consent y/n/pending, the timezone set through both paths, push token owner match, sandbox platform, failure retry, reset and restart.

Also verified with a temporary harness: Edge Identity together with Messaging (feat/live-activity-consent-independent-forward) and the Consent extension, using real EventHub and Core 5.13.0, with Edge's device attributes response simulated. Consent transitions caused no extra device attributes requests for synced values.

CI: the first run on 65094c6 failed once in EdgeIdentityAndIdentityDirectTests.testEcidsAreDifferentAfterReset, which is unrelated and passes locally. A re-run is in progress.

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.