You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need didReceiveMemoryWarningInLastSession to calculate the app crash metrics.
More Information
I talked with troubleshooting team, they said the replacement in AppCenter is - (BOOL)isAppKill.
However, that's not entirely equivalent to didReceiveMemoryWarningInLastSession, because - (BOOL)isAppKill indicates not only memory warnings, it checks if a crash report contains the SIGKILL symbol which generally indicates that the app was killed by the OS, and there are multiple reasons like:
high memory usage (likely after receiving the low memory warning)
app kills by the user
app kills because the app does not have certain permissions and the dev forgot to check
other reasons...
Problem that we have
Problem is we need to get the crashes that was only caused by memory usage/warnings.
If they are mixed with "App kills by the user", then we can't use it any more.
This will be a very big gap for us since we have a large DAU and the tracking each crash reason is very important to us. Without this metric we can't fulling migrate to AppCenter.
Solution we need
We need to keep the functionality of didReceiveMemoryWarningInLastSession;
Please provide an equivalent function for it in AppCenter so we can different the crash reasons.
The text was updated successfully, but these errors were encountered:
TLiu2121999
changed the title
Equivalent function for didReceiveMemoryWarningInLastSession
Equivalent function for didReceiveMemoryWarningInLastSession?
Mar 20, 2019
Describe the solution you'd like
We need didReceiveMemoryWarningInLastSession to calculate the app crash metrics.
More Information
I talked with troubleshooting team, they said the replacement in AppCenter is
- (BOOL)isAppKill
.However, that's not entirely equivalent to
didReceiveMemoryWarningInLastSession
, because- (BOOL)isAppKill
indicates not only memory warnings, it checks if a crash report contains the SIGKILL symbol which generally indicates that the app was killed by the OS, and there are multiple reasons like:Problem that we have
Problem is we need to get the crashes that was only caused by memory usage/warnings.
If they are mixed with "App kills by the user", then we can't use it any more.
This will be a very big gap for us since we have a large DAU and the tracking each crash reason is very important to us. Without this metric we can't fulling migrate to AppCenter.
Solution we need
We need to keep the functionality of
didReceiveMemoryWarningInLastSession
;Please provide an equivalent function for it in AppCenter so we can different the crash reasons.
The text was updated successfully, but these errors were encountered: