[GH-ISSUE #171] EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) #71

Closed
opened 2026-03-03 18:54:15 +03:00 by kerem · 4 comments
Owner

Originally created by @vtu-dog on GitHub (Aug 18, 2022).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/171

Hello,
I've just tried running Yeelight 3.3.37 and I encountered a peculiar error:

  1. The app opened fine at first, but it crashed as soon as I tried to log in (file: first-crash.txt)
  2. The app could no longer be opened, throwing the same error each time (first-crash again)
  3. Reinstalling the app resulted in an invalid code signature (subsequent-crashes.txt), self-signing doesn't seem to work

first-crash.txt
subsequent-crashes.txt

Originally created by @vtu-dog on GitHub (Aug 18, 2022). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/171 Hello, I've just tried running Yeelight 3.3.37 and I encountered a peculiar error: 1. The app opened fine at first, but it crashed as soon as I tried to log in (file: `first-crash.txt`) 2. The app could no longer be opened, throwing the same error each time (`first-crash` again) 3. Reinstalling the app resulted in an invalid code signature (`subsequent-crashes.txt`), self-signing doesn't seem to work [first-crash.txt](https://github.com/PlayCover/PlayCover/files/9372443/first-crash.txt) [subsequent-crashes.txt](https://github.com/PlayCover/PlayCover/files/9372445/subsequent-crashes.txt)
kerem closed this issue 2026-03-03 18:54:16 +03:00
Author
Owner

@vtu-dog commented on GitHub (Aug 18, 2022):

I renamed files from .ips to .txt, assuming that the output would not change, but using quicklook revealed that macOS cares about the extension after all. Sorry for the inconvenience!

<!-- gh-comment-id:1219296099 --> @vtu-dog commented on GitHub (Aug 18, 2022): I renamed files from `.ips` to `.txt`, assuming that the output would not change, but using quicklook revealed that macOS cares about the extension after all. Sorry for the inconvenience!
Author
Owner

@IsaacMarovitz commented on GitHub (Aug 18, 2022):

This is a known issue in PlayCover 1.1.0 (#176). For now, please downgrade to PlayCover 1.0.7 until a fix is released.

<!-- gh-comment-id:1219405936 --> @IsaacMarovitz commented on GitHub (Aug 18, 2022): This is a known issue in PlayCover 1.1.0 (#176). For now, please downgrade to PlayCover 1.0.7 until a fix is released.
Author
Owner

@vtu-dog commented on GitHub (Aug 18, 2022):

Downgrading to 1.0.7 and disabling jailbreak bypass fixed the issue, thank you.

<!-- gh-comment-id:1219411444 --> @vtu-dog commented on GitHub (Aug 18, 2022): Downgrading to 1.0.7 and disabling jailbreak bypass fixed the issue, thank you.
Author
Owner

@IsaacMarovitz commented on GitHub (Aug 18, 2022):

The issue will be resolved in hotfix 1.1.1 coming out in the next few hours.

<!-- gh-comment-id:1219453594 --> @IsaacMarovitz commented on GitHub (Aug 18, 2022): The issue will be resolved in hotfix 1.1.1 coming out in the next few hours.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/PlayCover#71
No description provided.