4. Please check if this step needs to be performed by the following content.
In the class where the Application is located, enter attachBaseContext to check if there is an override method. If there is an override method, ignore this step. If not, please proceed to Next.
Add the package path of the Application to the following configuration.
Reference code:
QAPMPluginConfig{
// Optional, defaults to empty. In the class where Application is located, enter attachBaseContext to see if there is an override method. If there is no override method, this item needs to be configured. The following figure shows that this check is not necessary.
5. At this point, you can try to compile. Compilation-related FAQ can be referred to for this step.
Q1: If an error stating "feature is disabled" occurs during compilation, see below:
A1: The plugin needs to dynamically insert properties into BuildConfig. Please add the following code under the app module's build.gradle file.
Reference code:
android {
...
// Add the following content.
buildFeatures {
...
buildConfig true
}
...
}
Q2: If a "Class Conflict" error occurs during compilation, as follows:
A2: Qapm and your project use different Android support libraries. Please remove the qapm's android.support library when adding dependencies, as follows:
2. Copy the code below and modify some of the fields. The following items are mandatory interface settings; for additional interface configurations, refer to the initialization interface analysis (Initializing QAPM in Application is recommended).
// Set the mobile phone model and device ID.
// Device identifier required, in the form of any string. deviceId (mandatory).
// The deviceId can be used to enable an allowlist, avoiding data sampling (Except crash and startup data, the sampling rate for other data is 0.1%).
// Set AppKey (mandatory, used to distinguish the reporting products. The value is obtained from the Product Configuration page under Mobile Performance Monitoring, refer to the previous step).
// Set the UUID to pull the obfuscated stack's mapping (mandatory. If QAPM Symbol Table Upload plugin is used, this variable can be used directly).
// If the qapmplugin plugin is used, this variable will be generated at build time, and errors can be ignored. If not used, it needs to be manually input. Please ensure the use of UUID format and that one apk corresponds to only one uuid.
// Set the QAPM external network reporting domain (required). Chinese Mainland: https://app.rumt-zh.com; global regions (except Chinese Mainland): https://app.rumt-sg.com
Crash and start data are reported in full, while other data is sampled due to its large volume, at a rate of 0.1% (one in a thousand). To report all data, an allowlist can be enabled, and the app will change the sampling rate at the next start.
The preset userId or deviceId can be added to the allowlist through the Application Management page to enable the allowlist.
Multiple processes need to initialize QAPM, separately.
Step 4: Access verification.
1. If the following log is printed, it indicates that the user has not been sampled, and the sampling rate needs to be reset:
See TAG: QAPM_manager_QAPMLauncher
2. If the following log is printed, it indicates that the initial access succeeded. You can verify data reporting and try to enable the advanced feature:
See TAG: QAPM_manager_QAPMPluginManager
Initialized Interface Analysis
API Name
Parameter
Parameter Description
Notes
public static QAPM setProperty(int key, Stringvalue)
Functionality: Set QAPM parameters.
key
Required. The Key that needs to be set.
-
QAPM.PropertyKeyLogLevel
Optional. Enable log level. (It is recommended to use QAPM.LevelDebug for Debug versions and QAPM.LevelWarn for release versions).
QAPM.PropertyNeedTranslate
Optional. Whether stack translation is needed, which by default is required. If the apk is not obfuscated, then pass in 'false'. Otherwise the frontend may display everything as 'unTranslated'.
public static boolean beginScene(String sceneName, int mode)
Functionality: Enable monitoring.
sceneName
Required. Scene name.
Use the OR operation to enable the performance module from Definition, such as enabling Crash and Anr: beginScene(“Crash&ANR”, QAPM.ModeCrash| QAPM.ModeANR)
mode
Required. The feature to be enabled.
QAPM.ModeStable
Optional. Enable all features (Recommended for external releases. Includes interval performance, crash, ANR, WebView page load, JsError, and network).
QAPM.ModeWebView
Optional. Enable WebView page load monitoring.
QAPM.ModeJsError
Optional. Enable WebView JS exception monitoring.
QAPM.ModeHTTPInWeb
Optional. Enable WebView network monitoring.
QAPM.ModeHTTP
Optional. Enable network monitoring.
public static boolean endScene(String sceneName, long mode)
Functionality: End monitoring (Only effective for frame drops and interval performance collection).
sceneName
Required. The name of the scene to be turned off (Required to correspond to the beginScene).
-
QAPM.ModeDropFrame
Optional. Turn off frame drop monitoring.
QAPM.ModeResource
Optional. Turn off interval performance monitoring.
Others
Note:
When compiling and packaging the app through the qapm plugin, the app needs a UUID as the Build ID. If there is a qapm.properties file in the project directory, and the value of the qapm_uuid property exists, this value will be used as the Build ID; otherwise, the plugin will randomly generate a Build ID.
qapm-plugin Version 2.39 and earlier will report an IO Error during the app compiling process: java.io.FileNotFoundException, qapm.properties (No such file or directory).
This error only occurs during compilation and does not affect the running of the app.
Yes
No
Was this page helpful?