Closed SoneeJohn closed 4 years ago
I am using the latest version (1.5.2)
Could you tell me are you inserted any IOS device, if yes the model ? Thanks.
@sicreative I have an iPhone 8 that is connected over Wi-Fi other than that no iOS models are connected via a cable.
BatteryStatusShow_beta_1.5.3.zip Could you help to check is this beta version crash on your system.
@sicreative Same crash
System Integrity Protection: enabled
Notes: Translocated Process
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [2756]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 sicreativelee.batterystatusshow 0x0000000108f127f1 specialized NSColor.init(hex:) + 449
1 sicreativelee.batterystatusshow 0x0000000108f08b92 IOBattery.iosioregclaim() + 3394
2 sicreativelee.batterystatusshow 0x0000000108f07b90 IOBattery.updatebattery() + 32
3 sicreativelee.batterystatusshow 0x0000000108f06462 IOBattery.init() + 1394
4 sicreativelee.batterystatusshow 0x0000000108f33338 AppDelegate.datacontrollerfinished() + 328
5 sicreativelee.batterystatusshow 0x0000000108f34201 partial apply + 17
6 sicreativelee.batterystatusshow 0x0000000108f26721 partial apply for thunk for @callee_guaranteed () -> () + 17
7 sicreativelee.batterystatusshow 0x0000000108f2554e thunk for @escaping @callee_guaranteed () -> () + 14
8 libdispatch.dylib 0x00007fff6f511658 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff6f51d7ab _dispatch_async_and_wait_invoke + 87
10 libdispatch.dylib 0x00007fff6f511658 _dispatch_client_callout + 8
Could you tell me which OSX version you currency used.
I, too, get this crash. No iOS-device attached. Application launches, but crashes seconds to minutes thereafter.
I, too, get this crash. No iOS-device attached. Application launches, but crashes seconds to minutes thereafter.
Sorry about that i can't reproduced this issue under our current system, so i don't know where the issue from. The symptom may come from the process of detect IOS, as the APP should able to ignore this if no IOS device detected.
The new version of 1.5.3 updated to provide more capability of read IOS devices.
The app crashes on launch on my system, here is the stack trace: