[GH-ISSUE #1895] [App Support]: LifeAfter (明日之后) crashes on M3 Pro with latest Nightly after accepting user agreement #1242

Open
opened 2026-03-03 19:05:03 +03:00 by kerem · 1 comment
Owner

Originally created by @thedakers on GitHub (Jun 15, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1895

Mac Model: MacBook Pro (M3 Pro)
macOS Version: macOS 14.4 (23E214)
PlayCover Version: [3.0.0-nightly.1234]
Game: LifeAfter (明日之后) v2.0.399

Problem Description:
The game starts normally and shows the user agreement. However, it crashes immediately after I click "Accept". The crash seems to be caused by the anti-cheat system.

What I've Tried:
I have already tried all the common solutions, including:

  1. Enabling PlayChain.
  2. Using the latest Nightly build.
  3. A full, clean re-installation (including deleting the ~/Library/Containers/io.playcover.PlayCover folder and rebooting).
  4. Changing the spoofed device model (iPad and iPhone).
    The issue still persists.

Current issues

  • App fails to install
  • App fails to open
  • App crashes randomly during usage
  • App experiences graphical issues or broken UI
  • App fails to connect to servers
  • Other

More details

Subject: [Bug Report] LifeAfter (明日之后) crashes on M3 Pro with latest Nightly build after accepting user agreement

Hello PlayCover Team,

First, I want to say thank you for all your hard work on this amazing project. I'm writing to report a persistent crash issue I'm experiencing with the game LifeAfter (明日之后) on my M3 Pro Mac.

My System Environment:

PlayCover Version: [Please enter your Nightly version number here, e.g., 3.0.0-nightly.1234]
macOS Version: macOS 14.4 (23E214)
Mac Model: MacBook Pro (M3 Pro, 18 GB RAM)
Game: LifeAfter (明日之后), version 2.0.399
Description of the Issue:
The game launches successfully and proceeds to the user agreement screen. However, immediately after I click "Accept" on the agreement, the application reliably crashes.

The crash report shows a Termination Reason: SIGNAL, Code 6 Abort trap: 6 and indicates that abort() called. This suggests that an anti-cheat or environment integrity check is being triggered after the agreement is accepted, causing the game to terminate itself.

Troubleshooting Steps Already Performed:
I have been troubleshooting this extensively and have already tried the following solutions, but the problem persists:

Enabled PlayChain in the game's settings.
Updated to the latest available Nightly build of PlayCover.
Performed a full, clean re-installation of PlayCover. This included deleting the application, deleting the ~/Library/Containers/io.playcover.PlayCover folder, rebooting the Mac, and then reinstalling the Nightly build and the game.
Tried spoofing different device models in the settings, including various iPad and iPhone models.
Despite all these steps, the crash continues to happen at the exact same point. It seems the game's latest security measures may not be fully bypassed by the current version, especially on the M3 architecture.

I have attached the full crash report for your detailed analysis.

Thank you again for your time and dedication. Please let me know if there is any further information or testing I can provide to help you diagnose and resolve this issue. I'm looking forward to a future update.

Best regards.

Crash log

---
### Condensed Crash Report for LifeAfter (明日之后)
---

### 1. Essential Information
- **Process:** g66 [1510]
- **Identifier:** com.netease.mrzh
- **Version:** 2.0.399
- **Code Type:** ARM-64 (Native)
- **OS Version:** macOS 14.4 (23E214) on Mac15,7 (M3 Pro)

### 2. Exception Details
- **Exception Type:** EXC_CRASH (SIGABRT)
- **Termination Reason:** Namespace SIGNAL, Code 6 Abort trap: 6
- **Terminating Process:** g66 [1510]
- **Application Specific Information:** abort() called

### 3. Crashed Thread Backtrace (Thread 0)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib           0x1879f2a60 __pthread_kill + 8
1   libsystem_pthread.dylib          0x187a2ac20 pthread_kill + 288
2   libsystem_c.dylib                0x187937a20 abort + 180
3   libc++abi.dylib                  0x1879e1d30 abort_message + 132
4   libc++abi.dylib                  0x1879d1fcc demangling_terminate_handler() + 320
5   libobjc.A.dylib                  0x1876701e0 _objc_terminate() + 160
6   g66                              0x10456bb8c 0x102418000 + 34945932
7   libc++abi.dylib                  0x1879e10f4 std::__terminate(void (*)()) + 16
8   libc++abi.dylib                  0x1879e1098 std::terminate() + 108
9   g66                              0x10391cc74 0x102418000 + 22039668
10  libsystem_c.dylib                0x1878e7f2c __cxa_finalize_ranges + 476
11  libsystem_c.dylib                0x1878e7cb4 exit + 44
12  g66                              0x1051c1c5c 0x102418000 + 47881308
13  g66                              0x1051c1b70 0x102418000 + 47881072
14  g66                              0x1051c0364 0x102418000 + 47874916
15  g66                              0x1051c0318 0x102418000 + 47874840
16  g66                              0x1036dca80 0x102418000 + 19679872
17  g66                              0x10242e348 0x102418000 + 90952
... (Additional game-specific frames) ...
22  g66                              0x103aee138 0x102418000 + 23945528
23  g66                              0x103aedce0 0x102418000 + 23944416
24  UIKitCore                        0x1b6ec61c0 -[UIViewController loadViewIfRequired] + 492
... (Frames showing UI loading and app lifecycle) ...
46  AppKit                           0x18b353cb8 -[NSApplication run] + 476
47  AppKit                           0x18b32af54 NSApplicationMain + 880
48  AppKit                           0x18b57d610 _NSApplicationMainWithInfoDictionary + 24
49  UIKitMacHelper                   0x1a0d990dc UINSApplicationMain + 972
50  UIKitCore                        0x1b6e859b4 UIApplicationMain + 148
51  g66                              0x103af947c 0x102418000 + 23991420
52  g66                              0x10242b94c 0x102418000 + 80204
53  dyld                             0x1876a20e0 start + 2360

### 4. Crashed Thread State (ARM 64-bit)
    x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
    x4: 0x00000001879e629c   x5: 0x000000016d9e2a40   x6: 0x0000000000000074   x7: 0x0000000000000000
    x8: 0xff77d985df2e8e60   x9: 0xff77d984305df4a0  x10: 0x0000000000000200  x11: 0x000000000000002d
   x16: 0x0000000000000148  x17: 0x00000001f9aa2c30  x19: 0x0000000000000006  x20: 0x00000001ef737ac0
    fp: 0x000000016d9e29b0   lr: 0x0000000187a2ac20
    sp: 0x000000016d9e2990   pc: 0x00000001879f2a60 cpsr: 0x40001000
   far: 0x0000000000000000  esr: 0x56000080 (Address size fault)

What version of PlayCover are you using?

3.1.0

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

  • Yes my issue is written in English
Originally created by @thedakers on GitHub (Jun 15, 2025). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1895 ### App Store link 、 Mac Model: MacBook Pro (M3 Pro) macOS Version: macOS 14.4 (23E214) PlayCover Version: [3.0.0-nightly.1234] Game: LifeAfter (明日之后) v2.0.399 Problem Description: The game starts normally and shows the user agreement. However, it crashes immediately after I click "Accept". The crash seems to be caused by the anti-cheat system. What I've Tried: I have already tried all the common solutions, including: 1. Enabling PlayChain. 2. Using the latest Nightly build. 3. A full, clean re-installation (including deleting the ~/Library/Containers/io.playcover.PlayCover folder and rebooting). 4. Changing the spoofed device model (iPad and iPhone). The issue still persists. ### Current issues - [ ] App fails to install - [x] App fails to open - [ ] App crashes randomly during usage - [ ] App experiences graphical issues or broken UI - [ ] App fails to connect to servers - [ ] Other ### More details Subject: [Bug Report] LifeAfter (明日之后) crashes on M3 Pro with latest Nightly build after accepting user agreement Hello PlayCover Team, First, I want to say thank you for all your hard work on this amazing project. I'm writing to report a persistent crash issue I'm experiencing with the game LifeAfter (明日之后) on my M3 Pro Mac. My System Environment: PlayCover Version: [Please enter your Nightly version number here, e.g., 3.0.0-nightly.1234] macOS Version: macOS 14.4 (23E214) Mac Model: MacBook Pro (M3 Pro, 18 GB RAM) Game: LifeAfter (明日之后), version 2.0.399 Description of the Issue: The game launches successfully and proceeds to the user agreement screen. However, immediately after I click "Accept" on the agreement, the application reliably crashes. The crash report shows a Termination Reason: SIGNAL, Code 6 Abort trap: 6 and indicates that abort() called. This suggests that an anti-cheat or environment integrity check is being triggered after the agreement is accepted, causing the game to terminate itself. Troubleshooting Steps Already Performed: I have been troubleshooting this extensively and have already tried the following solutions, but the problem persists: Enabled PlayChain in the game's settings. Updated to the latest available Nightly build of PlayCover. Performed a full, clean re-installation of PlayCover. This included deleting the application, deleting the ~/Library/Containers/io.playcover.PlayCover folder, rebooting the Mac, and then reinstalling the Nightly build and the game. Tried spoofing different device models in the settings, including various iPad and iPhone models. Despite all these steps, the crash continues to happen at the exact same point. It seems the game's latest security measures may not be fully bypassed by the current version, especially on the M3 architecture. I have attached the full crash report for your detailed analysis. Thank you again for your time and dedication. Please let me know if there is any further information or testing I can provide to help you diagnose and resolve this issue. I'm looking forward to a future update. Best regards. ### Crash log ```shell --- ### Condensed Crash Report for LifeAfter (明日之后) --- ### 1. Essential Information - **Process:** g66 [1510] - **Identifier:** com.netease.mrzh - **Version:** 2.0.399 - **Code Type:** ARM-64 (Native) - **OS Version:** macOS 14.4 (23E214) on Mac15,7 (M3 Pro) ### 2. Exception Details - **Exception Type:** EXC_CRASH (SIGABRT) - **Termination Reason:** Namespace SIGNAL, Code 6 Abort trap: 6 - **Terminating Process:** g66 [1510] - **Application Specific Information:** abort() called ### 3. Crashed Thread Backtrace (Thread 0) Crashed Thread: 0 Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x1879f2a60 __pthread_kill + 8 1 libsystem_pthread.dylib 0x187a2ac20 pthread_kill + 288 2 libsystem_c.dylib 0x187937a20 abort + 180 3 libc++abi.dylib 0x1879e1d30 abort_message + 132 4 libc++abi.dylib 0x1879d1fcc demangling_terminate_handler() + 320 5 libobjc.A.dylib 0x1876701e0 _objc_terminate() + 160 6 g66 0x10456bb8c 0x102418000 + 34945932 7 libc++abi.dylib 0x1879e10f4 std::__terminate(void (*)()) + 16 8 libc++abi.dylib 0x1879e1098 std::terminate() + 108 9 g66 0x10391cc74 0x102418000 + 22039668 10 libsystem_c.dylib 0x1878e7f2c __cxa_finalize_ranges + 476 11 libsystem_c.dylib 0x1878e7cb4 exit + 44 12 g66 0x1051c1c5c 0x102418000 + 47881308 13 g66 0x1051c1b70 0x102418000 + 47881072 14 g66 0x1051c0364 0x102418000 + 47874916 15 g66 0x1051c0318 0x102418000 + 47874840 16 g66 0x1036dca80 0x102418000 + 19679872 17 g66 0x10242e348 0x102418000 + 90952 ... (Additional game-specific frames) ... 22 g66 0x103aee138 0x102418000 + 23945528 23 g66 0x103aedce0 0x102418000 + 23944416 24 UIKitCore 0x1b6ec61c0 -[UIViewController loadViewIfRequired] + 492 ... (Frames showing UI loading and app lifecycle) ... 46 AppKit 0x18b353cb8 -[NSApplication run] + 476 47 AppKit 0x18b32af54 NSApplicationMain + 880 48 AppKit 0x18b57d610 _NSApplicationMainWithInfoDictionary + 24 49 UIKitMacHelper 0x1a0d990dc UINSApplicationMain + 972 50 UIKitCore 0x1b6e859b4 UIApplicationMain + 148 51 g66 0x103af947c 0x102418000 + 23991420 52 g66 0x10242b94c 0x102418000 + 80204 53 dyld 0x1876a20e0 start + 2360 ### 4. Crashed Thread State (ARM 64-bit) x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x00000001879e629c x5: 0x000000016d9e2a40 x6: 0x0000000000000074 x7: 0x0000000000000000 x8: 0xff77d985df2e8e60 x9: 0xff77d984305df4a0 x10: 0x0000000000000200 x11: 0x000000000000002d x16: 0x0000000000000148 x17: 0x00000001f9aa2c30 x19: 0x0000000000000006 x20: 0x00000001ef737ac0 fp: 0x000000016d9e29b0 lr: 0x0000000187a2ac20 sp: 0x000000016d9e2990 pc: 0x00000001879f2a60 cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 (Address size fault) ``` ### What version of PlayCover are you using? 3.1.0 ### What version of macOS are you using? Sonoma (macOS 14) ### Issue Language - [x] Yes my issue is written in English
Author
Owner

@Refac7 commented on GitHub (Oct 29, 2025):

Same in M4 (MacOS Tahoe 26.0.1)

<!-- gh-comment-id:3461815783 --> @Refac7 commented on GitHub (Oct 29, 2025): Same in M4 (MacOS Tahoe 26.0.1)
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#1242
No description provided.