Update...Found this article to explain the duplicate calls and
Also discovered that the redirects were occurring on devices that
weren't maintaing the s_vi cookie. 30% devices seems like a lot.Solution
is to post a custom visitor id using the vid variable with each tracking
call. It should actually give us better visitor tracking and eliminates
the redirect and incremental visitor count problem we...
I have determined that if I remove the Avg Time Spent metric in the
report I no longer get the error. I assume it has something to do with
Adobe changing how they calculate Avg Time Spent in their spring
release. It is throwing that error in older reports.
Hey Mike, Sending hits when the app enters the background (or while the
app is in the background) can cause issues in your lifecycle data. If
you are sending hits via the SDK from the background, make sure you're
using the trackActionFromBackground:data: message. Using this will
suppress new lifecycle sessions from being created by your app's
activity while it's in the background.If this doesn't help, I recommend
contacting Client Care so we can get a ticket open for you. steve
I would agree, and on top of that we didn't have advance warning that it
would be an issue. In fact our regional segments contained around 200
countries and took several hours to create. Now we have to re-create
them in the new segment manager which is slower than before. Fortunately
we have a record of the rules.
Hi Mike,Yes, moving the call to onResume is the correct way to fix the
issue. 🙂For anything that extends Activity, you should be using the
onResume() to call Config.collectLifecycleData() and onPause() to call
Config.pauseCollectingLifecycleData().You can always find more
documentation on this here, specifically under the 'Lifecycle Metrics'
ButterfieldMobile EngineerAdobe Marketing Cloud