[GH-ISSUE #2058] [Bug]: Where Wind Meets (阴阳师：妙境物语) Crashes on Launch #1374

New issue

Open

opened 2026-03-03 19:06:14 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 19:06:14 +03:00

Owner

Originally created by @tawwn on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/2058

Describe the bug

Where Wind Meets (阴阳师：妙境物语) crashes immediately after the initial protocol/agreement screen, approximately 14 seconds after launch. The crash is 100% reproducible and occurs during the NetEase SDK initialization phase when calling finishAndStartGameEngine.
Error: Segmentation fault (SIGSEGV) - null pointer dereference at address 0x0000000000000000
The crash happens in the main thread when the game attempts to execute a callback function pointer that was never properly initialized, causing the program counter to jump to address 0x0.
Expected behaviour*
The game should:

Launch successfully
Display the NetEase SDK protocol/agreement screen
Complete SDK initialization after agreement acceptance
Start the game engine
Proceed to the main menu/game interface

This is the normal behavior on actual iOS devices.

Steps to reproduce

1.Install "Where Wind Meets" (阴阳师：妙境物语) version 15.0.0 using PlayCover 1.1.7
2.Launch the game from PlayCover
3/Wait for the initial loading screens
4.Accept/complete the protocol/agreement screen if it appears
5.Crash occurs - Game terminates with segmentation fault

Reproducibility: 100% consistent crash at the exact same point every launch

Expected behaviour

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Termination Reason: Segmentation fault: 11
Triggered Thread: Thread 0 (Main Thread)

Environment Details:
PlayCover Version: 1.1.7
macOS Version: 26.1 (25B78) - Sequoia
Hardware: MacBook Pro (M1, 2020) - MacBookPro17,1
RAM: 16 GB
App Identifier: com.netease.yysls
App Version: 15.0.0 (Build 1.0.5)

Crash log

Thread 0 Crashed (Main Thread):
0   ???                                 0x0 (null pointer)
1   Game                                0x10392d240 (offset: 23614016)
2   Game                                0x103929178 (offset: 23597432)
3   Game                                0x103929608 (offset: 23598600)
4   Game                                0x10391f7f0 (offset: 23558128)
5   Game                                0x10391f6cc (offset: 23557836)
6   NtUniSdkCommon                      -[NGUTMPDelegate finishAndStartGameEngine] + 800
7   NtUniSdkCommon                      -[NGUTMPDelegate onFinishProtocol:] + 552
8   CoreFoundation                      __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148

What version of PlayCover are you using?

3.1.0

What version of macOS are you using?

Other (please specify)

Issue Language

Yes my issue is written in English

Originally created by @tawwn on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/2058 ### Describe the bug Where Wind Meets (阴阳师：妙境物语) crashes immediately after the initial protocol/agreement screen, approximately 14 seconds after launch. The crash is 100% reproducible and occurs during the NetEase SDK initialization phase when calling finishAndStartGameEngine. Error: Segmentation fault (SIGSEGV) - null pointer dereference at address 0x0000000000000000 The crash happens in the main thread when the game attempts to execute a callback function pointer that was never properly initialized, causing the program counter to jump to address 0x0. Expected behaviour* The game should: Launch successfully Display the NetEase SDK protocol/agreement screen Complete SDK initialization after agreement acceptance Start the game engine Proceed to the main menu/game interface This is the normal behavior on actual iOS devices. ### Steps to reproduce 1.Install "Where Wind Meets" (阴阳师：妙境物语) version 15.0.0 using PlayCover 1.1.7 2.Launch the game from PlayCover 3/Wait for the initial loading screens 4.Accept/complete the protocol/agreement screen if it appears 5.Crash occurs - Game terminates with segmentation fault Reproducibility: 100% consistent crash at the exact same point every launch ### Expected behaviour Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Termination Reason: Segmentation fault: 11 Triggered Thread: Thread 0 (Main Thread) Environment Details: PlayCover Version: 1.1.7 macOS Version: 26.1 (25B78) - Sequoia Hardware: MacBook Pro (M1, 2020) - MacBookPro17,1 RAM: 16 GB App Identifier: com.netease.yysls App Version: 15.0.0 (Build 1.0.5) ### Crash log ```shell Thread 0 Crashed (Main Thread): 0 ??? 0x0 (null pointer) 1 Game 0x10392d240 (offset: 23614016) 2 Game 0x103929178 (offset: 23597432) 3 Game 0x103929608 (offset: 23598600) 4 Game 0x10391f7f0 (offset: 23558128) 5 Game 0x10391f6cc (offset: 23557836) 6 NtUniSdkCommon -[NGUTMPDelegate finishAndStartGameEngine] + 800 7 NtUniSdkCommon -[NGUTMPDelegate onFinishProtocol:] + 552 8 CoreFoundation __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 ``` ### What version of PlayCover are you using? 3.1.0 ### What version of macOS are you using? Other (please specify) ### Issue Language - [x] Yes my issue is written in English

kerem added the

bug

label

2026-03-03 19:06:14 +03:00

kerem commented

2026-03-03 19:06:15 +03:00

Author

Owner

@tawwn commented on GitHub (Jan 18, 2026):

i have update to playcover 3.1.0 but still error

@tawwn commented on GitHub (Jan 18, 2026): i have update to playcover 3.1.0 but still error

kerem commented

2026-03-03 19:06:15 +03:00

Author

Owner

@ohaiibuzzle commented on GitHub (Jan 30, 2026):

Error: Segmentation fault (SIGSEGV) - null pointer dereference at address 0x0000000000000000

Sounds like anticheat behavior than anything else. Who would dereference a nullptr intentionally

@ohaiibuzzle commented on GitHub (Jan 30, 2026): > Error: Segmentation fault (SIGSEGV) - null pointer dereference at address 0x0000000000000000 Sounds like anticheat behavior than anything else. Who would dereference a nullptr intentionally