Enabling Feature
Initialization requires enabling Crash and ANR monitoring, which by default monitors Crash and ANR information.
QAPM.beginScene(QAPM.SCENE_ALL, QAPM.ModeStable);
QAPM provides APIs for uploading custom log files in case of crashes or ANRs, if necessary. An example is as follows:
QAPM.setProperty(QAPM.PropertyExtraDataListener, new IExtraDataListener() {
@Override
public List<String> onAnrExtraFileHandler() {
List<String> files = new ArrayList<>();
File[] fileArray = new File("xxxx").listFiles();
for (File file : fileArray) {
files.add(file.getAbsolutePath());
}
return files;
}
@Override
public List<String> onCrashExtraFileHandler() {
List<String> files = new ArrayList<>();
File[] fileArray = new File("xxxx").listFiles();
for (File file : fileArray) {
files.add(file.getAbsolutePath());
}
return files;
}
});
Verifying Whether the Feature Is Working Properly
Retrieval tag: QAPM_manager_QAPMPluginManager
Retrieval tag: QAPM_crash
The following log message in case of crashes or ANRs indicates that QAPM has collected this exception:
Retrieval tag: plugin::144
The following log message indicates that QAPM has successfully reported this exception. An example is as follows:
The other crash retrieval tags are as follows:
ANR: [plugin::140].
NativeCrash: [plugin::146].
Note:
To avoid lagging, keep the logic in the interface callbacks as simple and straightforward as possible.
Uploaded files must be less than 20 MB in size. Files larger than the limit will not be uploaded. Select helpful log files.
Crash events can be viewed on the Mobile Monitoring Crash page, and ANR rates can be viewed in the Overview page.
Was this page helpful?