# Does Crasheye charge?

Free forever, please feel free to use it.

# How to add project application members

# Step 1:

On the Crasheye platform, move the mouse to the left menu bar and select Rights Management Platform (opens new window)

# Step 2:

Switch member management, click Add, search for project members through Email and select user group information. Email can add multiple members at the same time separated by English commas. Click Save to add successfully (Non-administrator permissions, members cannot be added, you can consult the administrator of the corresponding project to add)

# How to use the alarm function/alarm?

# Settings

In Crasheye platform (opens new window) Settings - Monitoring Settings - Alarm Settings, click Add Alarm Rule

  • After the alarm rule is met, the number of uses of the App must be > 0 to trigger the alarm .
  • The project will (with AppKey as the unique identifier) send an alert email within 24 hours from now (crash number, crash rate, affected user count, affected user rate), Email without cap.

# Same crash problem

  • The alarm is triggered for the first time, and the alarm email is received within about 10min - 30min;
  • Reaches the alarm threshold again (the numeric value remains unchanged compared to the last time, no notification is triggered) Send the second email after 1 hour;
  • The service verifies the alarm rule every 10min or so, the mail service fails to receive the alarm, retries every 0.5min, throws an exception when the retry fails, and stops and retries 3 times, and the result is logged.

# alarm function configuration example image

# Monitor items

  • Specified version:
    Specify a version number and the version number reports crash to trigger the alarm rule; when multiple version numbers are specified, any version satisfies the alarm rule and triggers the alarm.
  • All editions:
    All versions meet the alarm rules and trigger an alarm.
  • Single version:
    Any version meets the alarm rules and triggers an alarm.
  • Single crash issue:
    When a crash problem, when the number of crashes exceeds x, an alarm is triggered

# monitor metrics

  • crash rate (recommended):
    Crash rate (%) = number of crashes/number of uses, 1 decimal place reserved
  • Affected user rate (recommended):
    Affected user rate (%) = affected user count/user count, 1 decimal place reserved
  • Number of crashes:
    Number of flashbacks that occurred when using the App, integer
  • Number of affected users:
    Multiple flashbacks of a device, counted as a number of affected users, integer

# Does Crasheye have data leaks? What information is collected?

The collected data is related to the crash, the purpose is to provide developers with a real crash scenario, and no personal privacy information is collected, and after the data analysis is completed, it is only open to the project members.
Routinely collected information mainly includes:

  • crash environment: Crash information and thread stack, ROM/RAM, network environment/system language, etc
  • App information: package name, version, process name
  • Device information: device name, system version, screen resolution

Developers can view all reports by printing the report data log

# Can I use apps that are not online?


# Will there be conflicts between Crasheye and third-party SDK compiling at the same time?

There may be conflicts, if you encounter problems accessing, you can contact Crasheye or the official staff of the third-party SDK, or find a solution in the corresponding help

# Will there be conflicts when Crasheye and similar SDKs are used at the same time?

No, it is recommended to initialize Crasheye after similar SDK initialization

# Will accessing Crasheye affect the running speed of the program?

With little impact, Crasheye only checks for the last crash data to upload when the app starts. If so, the data is uploaded after compression without affecting the function of the application.

# Is the traffic consumed big?

Crasheye provides interface settings that are only reported in the wifi environment. When the crash file is not generated under wifi, it will be saved locally and uploaded under the wifi environment.
According to Crasheye, the average data transmission per crash is around 10K

# (iOS) Does access Crasheye affect app store publishing?


# What customized features does Crasheye support?

Provides multiple functions control interface and information logging API:

Android Api Instructions
iOS Api Instructions

# I use my own account to login now. Can I change the login account due to work changes?

If you're an "app owner," you can't untie your account from your app.
It is recommended to use a company product mailbox instead of a personal name mailbox when creating an app.
If you are not the "app owner", contact the "app owner" to unlink.

# After accessing Crasheye, how much impact will it have on the memory occupancy and CPU consumption of the original application?

After accessing Crasheye, the memory occupancy increased by 0.86MB, and the CPU mode was 1%, which had no effect.

Test method: Use the TestPlus client (opens new window) performance test tool to test the same program at least three times before and after accessing Crasheye, each test time is not less than 30 seconds, and take the average value. The test data is shown in the following table (test phone: Redmi note3):

No Crasheye With Crasheye Increase
Memory 32.81MB 33.67MB 0.86MB
CPU mode 1% 1% 0%

# The project has accessed Crasheye, but the page shows that it is not connected?

Problem removal method:

# Step1:

Access network permissions have been added:
< uses-permission android:name="android.permission.INTERNET"/>

# Step2:

Search in logcat for the following characters (reporting active):
NetSender: Sending data to url: http://rp.crasheye.cn/session

# Step3:

Check for the following results:
NetSender: Transmitting result {"ret":0,"msg":"","data":{"appkeyvalid":true}}

If the above 3 steps fail, please check the access document to re-access or contact the official staff

# Why does my app crash rate exceed 100%?

There are two possibilities:

  1. The crash occurred as soon as the application was started, and was successfully captured by Crasheye. However, the live report was not completed. Because the crash stack has the function of reporting failure caching, but the live report has no such logic, resulting in a later report. Multiple crashes were reported at the same time, but there was only one live report. In this case, there may be more crashes than live reports, which will eventually lead to a crash rate of more than 100%;
  2. The application initializes Crasheye in the service. After the service generates a crash, Crasheye will report the crash, but because the session will not be performed when the service is started, and the main program does not crash at this time. If a large number of such (service crash) conditions occur, the number of crashes > the number of live reports; if it is determined that crashes need to be collected in the service, it is normal for the number of crashes to be greater than the number of live reports;

Ps: Why doesn't Crasheye report the service? The crash of the service will not affect the function of the main program, and the main program can start the service at any time, but the start of the service cannot be regarded as an active user, so Crasheye determined that it would not provide live reports in the service.

# How to find the corresponding crash information on the page through the crashed mobile phone?

There are two ways to locate crash problems:

# Method 1: All crash information of this machine can be located through uid (client/client side/client end ID)

  1. Mobile phone to access the computer, you can find the value of uid through logcat, you can find it on the computer through this value, the uid of the following figure is: 69d86f0988d898df246e36071bb02baa
  1. Search directly on the page by client/client side/client end ID

The crash information number #417 is the crash we need to search for

# Method 2: Locate crash information by user identity

  1. The user identity is set when initializing Crasheye: (You can check the common API: Set user identity)
  2. If the user identity you set is UserByCQF, then you can search like this on the page:

The page will list all crashes about the user UserByCQF

Last Updated: 12/6/2022, 10:58:32 AM