Expected Behaviour
Match all AEP Mobile Edge Response events in a Project Griffon session. Including error events.
Actual Behaviour
I’ve run into a few inconsistencies with edge response events vs SDK v5 response events.
In Edge, the ACPExtensionEventSource is being overwritten with the konductor handle type so it doesn’t contain the v5 value: com.adobe.eventsource.responsecontent
The ACPExtensionEventData payload is coming back as an array instead of an object
The request event identifier in edge events is requestEventId but in SDK v5 it’s requestEventIdentifier
Reproduce Scenario (including but not limited to)
No schemas or code exist to match AEP Mobile Edge Error Response events.
Current matchers for AEP Mobile Edge Response events only match events where Konductor handle types have not been applied.
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem
Expected Behaviour
Match all AEP Mobile Edge Response events in a Project Griffon session. Including error events.
Actual Behaviour
I’ve run into a few inconsistencies with edge response events vs SDK v5 response events.
In Edge, the ACPExtensionEventSource is being overwritten with the konductor handle type so it doesn’t contain the v5 value: com.adobe.eventsource.responsecontent
The ACPExtensionEventData payload is coming back as an array instead of an object
The request event identifier in edge events is requestEventId but in SDK v5 it’s requestEventIdentifier
Reproduce Scenario (including but not limited to)
No schemas or code exist to match AEP Mobile Edge Error Response events.
Current matchers for AEP Mobile Edge Response events only match events where Konductor handle types have not been applied.
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem