Quick Tracking:Introducing and configuring the SDK

Basic SDK information

1 Quick integration

In the background of QuickTracking, dedicated integration code is generated for each App, which can be integrated according to the guidance in the product. Check whether you have used the Umeng + SDK. If you have used the SDK, change the SDK file path in a timely manner. For more information, see 1.2 in this document.

1.1 product path

Quick Tracking "Home"-"management console", "management console" on the "management console" to go to the "organization list" function, the organization list displays the currently created organization, find the organization to which the application belongs, click the "management application" function to jump to the "application management] page, on the right side of the created application, click" de-integrate ".

Click the "Deintegrate" button to jump to the new page to obtain the dedicated integration code, click Next to enter the "integration verification", scan the code to call up the app, and confirm whether the integration is successful.

1.2 check whether it conflicts with Umeng + SDK

Note that you need to check whether you have already used the Umeng + SDK. If you have already used it, be sure to set the change SDK file path.

2 Integration code details

If the preceding page cannot be reached due to specific reasons, you need to view the document before you can integrate it. The specific integration code is as follows:

2.1 Parameter Preparation

appKey: obtained from the application list

Collection domain name: obtained in the "Management Console-Collect Information" module

SDK information: You can obtain the Add Web Page Link in the "Collect Information" section of the Management Console.

2.2 introduce the SDK

2.2.1 Automatic integration

Add the URL of the new Maven repository for the QuickTracking SDK to the buildscript and allprojects sections in the build.gradle configuration script of the project.

maven { url 'https://repo1.maven.org/maven2/' }

Add the SDK Maven repository address to the repositories section of the build.gradle configuration script corresponding to the project:

buildscript {
    repositories {
        google()
        jcenter()
        maven { url 'https://repo1.maven.org/maven2/' }
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.0'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        maven { url 'https://repo1.maven.org/maven2/' }
    }
}

Add the dependencies of the statistics SDK library and other libraries to the dependencies section of the build.gradle configuration script corresponding to the project app:

dependencies {
    implementation fileTree(include:['*.jar'], dir:'libs')

    // QuickTracking statistical analysis SDK
    implementation 'com.lydaas.qtsdk:qt-px-common:1.8.5.PX'
  
}

In the development environment of Android Studio 3.1 or later, if you specify the latest version of the dependency "latest.de velopment", the download timeout may occur. In this case, you must specify the version number.

2.2.2 Manual integration

Select and download the SDK functional components, and decompress the. zip file to obtain the corresponding component package:

• qt-px-common-1.x.x.PX.aar // Statistics SDK, which must be integrated.

• Copy the relevant component jar package into the project libs directory of Android Studio, right-click the project of Android Studio, and select Open Module Settings -> in the Project Structure pop-up box-> select the Dependencies tab-> click the "+" at the bottom left-> select the component package type-> introduce the corresponding package.

• Right-click the project root directory in Eclipse, select Properties -> Java Build Path -> Libraries, then click Add External JARs... select the path pointing to JAR, and click OK, that is, the import is successful. (ADT17 and later do not need to be manually imported).

• Add the statistics SDK library to the dependencies section of the build.gradle configuration script corresponding to the project application level.

repositories{
    flatDir{
        dirs 'libs'
    }
}

dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation files('libs/qt-px-common-1.x.x.PX.aar') // Required.
}

2.3 configuration permissions

The statistics SDK requires the host application to be granted the following permissions:

An example AndroidManifest.xml manifest file is given below:

<manifest>
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
    <uses-permission android:name="android.permission.READ_PHONE_STATE"/>
    <uses-permission android:name="android.permission.INTERNET"/>
</manifest>

2.4 obfuscation configuration

If your application uses code obfuscation, add the following configuration to prevent the SDK from being unavailable due to Quick Tracking SDK obfuscation.

-keep class com.umeng.** {*;}
-keep class org.repackage.** {*;}

-keep class com.quick.qt.** {*;}
-keep class rpk.quick.qt.** {*;}

-keepclassmembers class * {
   public <init> (org.json.JSONObject);
}
-keepclassmembers enum * {
    public static **[] values();
    public static ** valueOf(java.lang.String);
}

The SDK needs to reference the resource file of the imported project and obtains the resource reference file R.java through the reflection mechanism, but proguard may delete R.java when developers use obfuscation /optimization tools such as proguard to process apk. If this problem occurs, please add the following configuration:

-keep public class [your app package name]. R$*{
public static final int *;
} 

2.5 tag verification configuration

Find the activity of the response android.intent.action.MAIN in the AndroidManifest.xml file (that is, the first Activity that the application can be evoked externally), and add the following code so that the application can be evoked by the specified connection scheme:

<intent-filter>
    <action android:name="android.intent.action.VIEW"/>
    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />
    <data android:scheme="atm. Your appKey" />
</intent-filter>

Note:

1. Please use a separate intent-filter, and other intent-filters side by side, do not fill the above code into other intent-filters;

2. Replace "Your appKey" with the appKey of your application.