Closed mdonke closed 2 years ago
The issue is located in RCTAEPEdgeMapUtil where you don't handle the incoming (weird) ArrayList/HashMap data structure for "segments".
Can you please fix this?
I didn't check iOS. Maybe there is the same issue.
@mdonke, thanks for reporting. We will look into it.
Calise Cheung Mobile Engineer
Hi @mdonke, We narrowed down the issue for Android platform and working on a fix. iOS has different implementation, could you check iOS and let us know if you see the issue there with the same response?
Thanks, Calise Cheung Mobile Engineer
Yes, just verified: its working fine on iOS.
@mdonke Thanks for confirming on iOS.
Thanks, Calise
Hi @mdonke, @adobe/react-native-aepedge@1.0.0-beta.2 is released which addresses this issue.
Please let us know if it resolves the problem.
Thanks, Calise
Hi @mdonke, have you got chance to try the beta.2 and see the issue is resolved?
Closing this for now, you can open a new ticket if still see the issue.
Upgraded to 1.0.0 and I confirm its working now. Thanks for your efforts!
I'm having issues extracting the Edge Tracking Response in my RN code. While native code receives the data correctly, the
Edge.sendEvent
callback in RN does not give all information.Expected Behaviour
Edge Tracking Event response is available in RN code
Actual Behaviour
Cropped response
Steps to Reproduce
Platform and Version
Android @adobe/react-native-aepedge@1.0.0-beta.1
Sample Code that illustrates the problem
Logs taken while reproducing problem
Looking at
adb logcat
I can see the expected response coming. (Look at "segments" below)