Mobile SDK LifeCycle metrics are not being tracked. | Community
Skip to main content
V
vallus
Level 2
May 1, 2024
Question

Mobile SDK LifeCycle metrics are not being tracked.

  • May 1, 2024
  • 2 replies
  • 3020 views

Hello Community,

 

We are currently facing a weird issue with our mobile app tracking. we've noticed that most of the life cycle metrics are not being tracked as shown below. Nothing is actually being tracked other than "app users". This issue is only with our iOS app

 

 

We have verified the code and followed the instructions as mentioned in launch (screenshot below). We have also updated the sdk pods to the new versions (5.0):

We have also checked this documentation (https://developer.adobe.com/client-sdks/home/base/mobile-core/lifecycle/#add-lifecycle-to-your-app) to see if we are missing anything but we couldn't find any issue with the code.

 

The only thing which we noticed is different on our code vs the instruction is that in the below line of code where "additionalContextData:" mentioned as "nil". On the launch instructions, it is mentioned as "MobileCore.lifecycleStart(additionalContextData: ["contextDataKey": "contextDataVal"])" . 

 

Would really appreciate if someone can help me with debugging this issue. Thanks alot!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

FarazHusain
Adobe Employee
FarazHusainAdobe Employee
Adobe Employee
May 2, 2024

Hey @vallus additionalConextData:nil shouldn't be the problem here as this is an optional parameter to pass a dictionary of additional data that will be attached to the lifecycle event.

 

I suspect it something else. Do you see any sort of errors in the debug logs? If we can get logs from the App it can provide more clarity on the issue. I would suggest to log client care ticket with Mobile Launch property details, configuration details and the debug logs. If you can create an Assurance session that would be helpful too.

 

Here's how you can setup Assurance - https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/app-implementation/assurance

 

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 2, 2024

Honestly, several years ago when our developers attempted to add context variables to our lifecycle calls on the ACP SDK they broke lifecycle metrics... we removed it and lifecycle started working again... 

 

We haven't yet gone back to trying to add context to Lifecycle again (other priorities).. 

 

So while it shouldn't be causing the problem, it might actually be the problem....

V
vallusAuthor
Level 2
May 2, 2024

Depending on your app? If you are using a shared code base it might be harder... but if you have separate iOS and Android versions then you should be able to make platform specific versions...

 

Of course, it it comes to needing context variables on your Lifecycle calls... that will be another challenge... but if you aren't using that now, and are just passing empty values... it's worth a shot?

 

Good Luck


Sorry, i meant the syntax which you've mentioned looks like is used for Android as per the documentation (https://developer.adobe.com/client-sdks/home/base/mobile-core/lifecycle/api-reference/)

 

Android:

iOS:

For iOS the syntax was mentioned as below. So, i'm just wondering if passing "null" would work for iOS swift.

 

    samhollingshead
    samhollingshead
    Level 2
    November 28, 2024

    @vallus did you resolve this? Are you using launch to implement?

    Terms & ConditionsAccessibility statement

    Loading footer...