Hey @fern1 - All of the a.action.time.* context data values are used with tracking timed actions. A couple of questions for you: What version of the SDK are you using?If v4, are you use the trackAction API, or the trackTimedAction API? I suspect you want a.timesincelaunch, but your answers to the ab...

Hey Amol,Can you turn on verbose logging for the SDK?MobileCore.setLogLevel(LoggingMode.VERBOSE);Assuming that the proper APIs are being called, the logs should confirm the following:The app SDK is getting properly configuredThe Analytics extension is being registeredAnalytics requests are being sen...

Hi @amolp86453083 -Have you had a chance to look at the logs generated by the SDK?  My initial thought is there are one of two issues:The app property didn't get fully published in Data Collection (Launch) - you can verify this by checking the remote location mentioned in the logs: https://assets.ad...

Hey @ericb17371700 - Sorry for confusion caused by the old documentation.  It used to be true that backdating session info hits could cause an extra visit (if more time than your Analytics visit timeout had passed since the user re-launched the app), but this behavior has been fixed on the backend s...

Hey @viniciushisao -We haven't had any issues running the Android SDKs on an M1 machine using Google's M1 preview emulator.  What kind of errors are you seeing that make you think it's an issue with the Adobe SDK?  Thanks.-steveb

Hey @viniciushisao -Are you using the Android Emulator M1 Preview?  https://github.com/google/android-emulator-m1-preview-steveb

Hey @bobo1429 - We've spent some time trying to reproduce this issue internally and haven't had any success.  If there are any settings or environment conditions that you can suggest that would help us to reproduce the issue, please let us know.Otherwise, please open a ticket with Client Care so tha...