Some jailbroken devices frequently generate crashes or other data through cheating methods, resulting in a large number of log reports. To avoid unexpected consumption of your event quota caused by such devices, you can isolate the logs generated by these devices in the following ways.

Prerequisites

Only supported on iOS.

You need to upgrade the SDK to version 5.1.7 or later.

Procedure

Crash analysis

After adding the following configuration, crash logs generated by all jailbroken devices will be isolated.

Switch to the Ignore jailbroken device configuration item.

Click Create configuration or edit the fallback configuration.

Toggle the value of the configuration item to Yes.

Save the changes. After the client pulls the latest configuration, crash logs generated by jailbroken devices will no longer be reported.

Other logs

Set the sampling rate for jailbroken devices to 0 to ignore the logs generated by jailbroken devices. Check the sampling rate corresponding to various events in Event usage, and then adjust the sampling rate of the event you need to isolate. The following uses isolating MetricKit data as an example.

Select MetricKit stability sampling rate and create a configuration.

Set the sampling rate to 0, and add the filter condition: Is jailbroken user = Yes.

Drag the newly created configuration, adjust it to the highest priority, and save the changes. After the client pulls the latest configuration, MetricKit logs generated by jailbroken devices will no longer be reported.

Last updated: 2026.10.23 11:17:23

Public security network record in Beijing: No. 11010802032137