Inflated AA events in iOS Flutter mobile app | Adobe Higher Education
Skip to main content
N
nancyduley
Level 2
July 30, 2025
Pregunta

Inflated AA events in iOS Flutter mobile app

  • July 30, 2025
  • 1 respuesta
  • 472 visualizaciones

Hello!

 

Is anyone here using Flutter for mobile apps and Adobe Analytics mobile SDK via Adobe Tag property?
We have identified inflated reporting for iOS events using the latest AA mobile iOS SDK version.

We are tracking events using code that looks like:
MobileCore.track(action: "start initial chat type", data: [
])

 

On these OS and device versions, we are seeing a higher number count for events in the reporting than expected:
iPadOS 18.5 on an iPad 11,6
iOS 18.5 on an iPhone 16
iOS 18.1.1 on an iPhone 14,5

Our developer is logging her testing, and is only seeing events fire once. When I test with the app installed on my iPad, my activity is inflated compared to what I actually did in the app.

 

Gemini has a host of possible culprits (below, details attached) but I am wondering if anyone has experienced this problem and if so, how you fixed it. Android version is working great! Sigh.
1. Rapid Event Firing (Double-Counting)
2. Asynchronous Behavior and Race Conditions
3. App Crashing and Restarting
4. Issues with SDK Initialization and Configuration
5. Device-Specific Behavior and OS Version Changes

 

We are in the process of getting the Adobe Analytics Assurance tool set up. Not that that will fix the problem, but it will help me do QA. I want to avoid setting up Charles.

 

Thanks for any advice or tips.

1 respuesta

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 30, 2025

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... 

    N
    nancyduleyAutor
    Level 2
    July 31, 2025

    Thanks again for your help, Jennifer! The rest of the story (as I understand it from developer)...
    We had the Android and iOS code combined. We had implemented a special fix for Android to initialize the SDK manually, which also got included with iOS. So iOS SDK was getting manually initialized and automatically initialized, which caused the inflated events. Now the code is separated and both Android and iOS working as expected.

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      July 31, 2025

      I'm so glad you figured it out!

       

      That makes a lot of sense... there are so many different mobile app code bases out there, and then of course the differences between Android and iOS... consolidate solutions have to make adjustments to deal with these complexities, and it doesn't help when some things work automatically, and others need something to be triggered... making sure that everything is working properly takes a little finesse.. 

        Términos y condicionesAccessibility statement

        Loading footer...