Jump to content
Patrick

Many app restarts if the app is in background

Recommended Posts

Hello,

since a few days (can’t say if it is since iOS 13 or an Cachly update) the app crashes / closes very often in the background. Can anybody confirm this? I also looked into the logs and found some infos about high cpu usage in background. Maybe it’s a Cachly bug? I have attached 2 logs. 

 

{"app_name":"Cachly","timestamp":"2019-10-07 07:44:08.34 +0200","app_version":"5.2.9","slice_uuid":"EC17B9A6-14AF-3E82-9882-B69860032588","adam_id":645384141,"build_version":"1","bundleID":"com.zedsaid.geocaching","share_with_app_devs":true,"is_first_party":false,"bug_type":"202","os_version":"iPhone OS 13.1.2 (17A860)","incident_id":"44DA3F64-C519-4DA1-9063-B8275936B1DC","name":"Cachly"}
Date/Time:        2019-10-07 07:42:31 +0200
End time:         2019-10-07 07:44:08 +0200
OS Version:       iPhone OS 13.1.2 (Build 17A860)
Architecture:     arm64e
Report Version:   29
Incident Identifier: 44DA3F64-C519-4DA1-9063-B8275936B1DC

Data Source:      Microstackshots
Shared Cache:     0x13d20000 BDEF4C4B-9094-33DE-8B0D-0E4A31BF0D40

Command:          Cachly
Path:             /private/var/containers/Bundle/Application/D5267F8B-F73F-4FCF-9E31-1618E5A2FACA/Cachly.app/Cachly
Identifier:       com.zedsaid.geocaching
Version:          5.2.9 (1)
Beta Identifier:  6945A8BE-A2F1-4635-BAE4-5AF768C34EB6
PID:              522

Event:            cpu usage
Action taken:     none
CPU:              90 seconds cpu time over 97 seconds (93% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit:        90s
Limit duration:   180s
CPU used:         90s
CPU duration:     97s
Duration:         97.07s
Duration Sampled: 12.00s
Steps:            16

Hardware model:   iPhone12,3
Active cpus:      6


Heaviest stack for the target process:
  9  ??? (libsystem_pthread.dylib + 40048) [0x193e94c70]

 

- - - Second Log - - -

 

{"app_name":"Cachly","timestamp":"2019-10-08 15:47:23.22 +0200","app_version":"5.2.9","slice_uuid":"ec17b9a6-14af-3e82-9882-b69860032588","adam_id":645384141,"build_version":"1","bundleID":"com.zedsaid.geocaching","share_with_app_devs":true,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 13.1.2 (17A860)","incident_id":"88A3900A-2353-4BAE-B656-DBC1036B1568","name":"Cachly"}
Incident Identifier: 88A3900A-2353-4BAE-B656-DBC1036B1568
CrashReporter Key:   b6ab8653baab6bcef54b3b5bdcb96cf13472c603
Hardware Model:      iPhone12,3
Process:             Cachly [3256]
Path:                /private/var/containers/Bundle/Application/D5267F8B-F73F-4FCF-9E31-1618E5A2FACA/Cachly.app/Cachly
Identifier:          com.zedsaid.geocaching
Version:             1 (5.2.9)
AppStoreTools:       11A1002b
AppVariant:          1:iPhone12,3:13
Code Type:           ARM-64 (Native)
Role:                unknown
Parent Process:      launchd [1]
Coalition:           com.zedsaid.geocaching [1239]


Date/Time:           2019-10-08 15:47:22.6563 +0200
Launch Time:         2019-10-08 15:46:40.2241 +0200
OS Version:          iPhone OS 13.1.2 (17A860)
Release Type:        User
Baseband Version:    1.01.17
Report Version:      104

Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, scene-create watchdog transgression: application<com.zedsaid.geocaching>:3256 exhausted real (wall clock) time allowance of 29.81 seconds | ProcessVisibility: Background | ProcessState: Suspended | WatchdogEvent: scene-create | WatchdogVisibility: Background | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 14.200 (user 14.200, system 0.000), 8% CPU", | "Elapsed application CPU time (seconds): 0.288, 0% CPU" | )
Triggered by Thread:  0

Share this post


Link to post
Share on other sites
1 hour ago, Patrick said:

I know but this happens every time if I switch to another app and back again, on an iPhone 11 Pro. Wasn’t the case with my previous iPhone Xs. 

I am on an 11 Pro also and I am not able to replicate the situation. Can you send me the crash files for Cachly by email (make sure to send the files not just copy the text) that way I can use them to debug? support@cach.ly

Thanks! 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×