@francescap28994 You can find the platforms we are currently supporting through our SDK here: https://aep-sdks.gitbook.io/docs/resources/upgrading-to-aep/aepvs4x#os-platform-support. Most of the smart TV and set top boxes are browser based, the JS SDK through Adobe Experience Platform Launch (https://experienceleague.adobe.com/docs/launch/using/overview.html#adobe-experience-platform-launch-overview) should be used instead of the AEP SDK.

Hi, The log message doesn't show anything wrong with Analytics. The reason why you are getting is 304 is because the JSON file hasn't been modified since the previous transmission. Thanks,Stephen

Hi Varun,There is no need to deploy the mobile services acquisition configuration file in your app. If we were using mobile service, you need to install the mobile service extension in Launch. From there, you will be able to select the mobile services app. And the rest is to follow the Mobile Install Instrcution in Launch. For more information, please refer to Adobe Analytics - Mobile Services - Adobe Experience Platform Mobile SDKs.

Can I get a better understanding of the use case you are covering when using the custom visitor id? I assume you are mainly using that for cross device tracking in Analytics. The setUserIdentifier API is removed from the latest SDK because we are talking to the Analytics team on the best solution to handle cross device tracking. I will post an update once we have the final decision.