Yeah, you will definitely need to see what is happening with regards to Adobe...
Something like Charles or Fiddler or HTTP Toolkit (or some other Proxy tool) helps you see what is being sent to Adobe, but not the result of the post-processing.
It's good that you are working on adding AEP Assurance, this is the best option as it will show you the calls going to Adobe, as well as the post-processed values of those calls...
Until you can really dig into what is happening in your app, it will be hard to guess at the cause.
We don't use flutter, we use React Native, but I haven't seen any duplication.
Since you are using
MobileCore.track(action: "start initial chat type", data: [])
I assume that you are either using the Adobe Edge Bridge extension or maybe you are still using the older SDK? We are in the process of updating our SDK, but decided not to try and bridge the events, but rather switched our code to using the Edge.sendEvent... that shouldn't impact anything, since many users use the Bridge and I haven't seen anyone else mention this issue... however, potentially something happening in Launch, or possibly in your processing rules might be adding some complexity to what you are seeing...
Honestly, the suggestions posed by AI don't look like likely scenarios...
- Rapid Firing would/should have been caught by your developer... and it wasn't.... but maybe their logging isn't catching it... so maybe??
- Asynchronous Behavior and Race Conditions - that could impact the order that things are triggered, but I really can't see it leading to duplication... I mean, maybe if the developer was checking for a condition that passed the logic check twice I supposed it could lead to duplication, but again, the developer would have caught that in their logs
- App Crashing and Restarting - umm what?? This one doesn't make much sense at all... if the app crashes (which you would have seen, and you didn't) it's not going to resend your event upon restarting....
- Issues with SDK Initialization and Configuration - again, this doesn't seem likely..
- Device-Specific Behavior and OS Version Changes - iOS isn't going to natively duplicate a call... and you aren't running an OS update in the middle of your test....
I assume the entire event is being duplicated, not just duplicated custom "events" inside the call...
Testing blind like this is really hard... If you can't get AEP Assurance in quickly, I would suggest using a proxy to test... despite it being a pain to set up...
