galliner.blogg.se - Imuscle oxs android integration

Imuscle oxs android integration install#
Imuscle oxs android integration code#

Double check your event tracking code and ensure it is reachable.

If you are tracking user events, you can use this test to ensure the SDK was configured properly and is successfully sending these events to Kochava.

Ensure the network connection from the test device is not limited behind a firewall or otherwise.

Ensure the SDK configuration and startup code is being reached.

Correct App GUID is used within SDK code configuration.After refreshing, if the Integration Not Complete! message persists, double check the following, then repeat this test: If instead you see a Integration Not Complete! message, wait a few more minutes and refresh the page.

Imuscle oxs android integration install#

At this point you have confirmed a successful SDK integration and can move ahead to Validate Post Install Events below. Within that page, look for the Integration Success! message which indicates integration was successful and that Kochava did receive an install from the SDK.

Wait a minute or two and visit the Install Feed Validation page for your app within the Kochava dashboard, under Apps & Assets > Install Feed Validation.

Run the app for approximately 30 seconds, which will allow more than enough time for the SDK to start and send an install to Kochava under typical conditions.

Double check the SDK configuration in code, ensuring the correct App GUID.

This test ensures the SDK was configured properly and successfully sent the install to Kochava. The SDK will send an install for the app once, after a fresh install.

keep class .After integrating the SDK or creating a new App GUID, we suggest performing these tests to ensure the SDK has been integrated successfully and is functioning as expected within your app. # KochavaTrackerLegacyReferrer: Referrer Receiver # KochavaCore: Keep annotations used for json serialization. # KochavaCore: Ignore SDK warnings for missing dependencies. Optional permissions are noted and can be removed if desired using the manifest entry shown. The following permissions are split by module and are automatically included with the module. Implementation ':ads-installreferrer:3.4.39.302' The Kochava SDK does not require specific versions of its dependencies however we recommend keeping them up to date whenever possible.Īds Identifier implementation ':ads-identifier:3.4.39.302' Collection is handled by the Kochava SDK with only the dependency itself needing to be included. If you wish for the SDK to collect the Huawei Advertising ID (OAID) and/or make use of the Install Referrer, you must integrate the Huawei Ads SDK by adding the appropriate dependencies. Install Referrer implementation ':installreferrer:2.2'Īpp Set ID implementation ':play-services-appset:16.0.0' NOTE: If using a version prior to version 17.1.0 you must also add the following permission. The Kochava SDK does not require specific versions of its dependencies however we recommend keeping them up to date whenever possible.Īds Identifier implementation ':play-services-ads-identifier:17.1.0' If you wish for the SDK to collect the Google Play Ads Identifier (ADID), App Set ID (ASID) and/or make use of the Install Referrer, you must integrate Google Play Services by adding the appropriate dependencies.