[GH-ISSUE #2072] [Bug]: endfield crashes after opened for around 1 minute #1388

Closed
opened 2026-03-03 19:06:36 +03:00 by kerem · 7 comments
Owner

Originally created by @meowscipty on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/2072

Describe the bug

endfield crashes on its own,without anything open it still crashes(i can't find the logs)

Steps to reproduce

use playcover nightly 1369
open endfield
wait for around 1 minute
crashes

Expected behaviour

it was running pretty good before an update or smth but now it crashes on its own

Crash log


What version of PlayCover are you using?

Nightly/beta (please specify build number)

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

  • Yes my issue is written in English
Originally created by @meowscipty on GitHub (Jan 27, 2026). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/2072 ### Describe the bug endfield crashes on its own,without anything open it still crashes(i can't find the logs) ### Steps to reproduce use playcover nightly 1369 open endfield wait for around 1 minute crashes ### Expected behaviour it was running pretty good before an update or smth but now it crashes on its own ### Crash log ```shell ``` ### What version of PlayCover are you using? Nightly/beta (please specify build number) ### What version of macOS are you using? Sonoma (macOS 14) ### Issue Language - [x] Yes my issue is written in English
kerem 2026-03-03 19:06:36 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Shalistera commented on GitHub (Jan 27, 2026):

same

<!-- gh-comment-id:3804976391 --> @Shalistera commented on GitHub (Jan 27, 2026): same
Author
Owner

@meowscipty commented on GitHub (Jan 27, 2026):

seems like Enable Jailbreak Bypass(Experimental) does not help

<!-- gh-comment-id:3805482997 --> @meowscipty commented on GitHub (Jan 27, 2026): seems like Enable Jailbreak Bypass(Experimental) does not help
Author
Owner

@Shalistera commented on GitHub (Jan 28, 2026):

Quick update from network comparisons (iPhone vs PlayCover):

  • On launch the game fetches two resources from listdl.com (paths include iedsafe).
  • About ~1 minute later it triggers a third fetch (path includes gamesafe).
  • PlayCover crashes at that point.
  • Right at the crash moment it also attempts to open a connection to glcs.listdl.com:443, but the connection drops immediately because the app terminates.
  • On a real iPhone, there’s no crash and the glcs.listdl.com:443 connection stays alive.

Given the iedsafe / gamesafe paths, this looks related to the security / anti-cheat flow (ACE?).

<!-- gh-comment-id:3808386746 --> @Shalistera commented on GitHub (Jan 28, 2026): Quick update from network comparisons (iPhone vs PlayCover): - On launch the game fetches two resources from `listdl.com` (paths include `iedsafe`). - About ~1 minute later it triggers a third fetch (path includes `gamesafe`). - **PlayCover crashes at that point.** - Right at the crash moment it also attempts to open a connection to `glcs.listdl.com:443`, but the connection drops immediately because the app terminates. - On a real iPhone, there’s no crash and the `glcs.listdl.com:443` connection stays alive. Given the `iedsafe` / `gamesafe` paths, this looks related to the security / anti-cheat flow (ACE?).
Author
Owner

@existence333 commented on GitHub (Jan 28, 2026):

Similar issue, here's my error log in case it helps:

Path:                /Users/USER/Library/Containers/io.playcover.PlayCover/*/com.gryphline.endfield.ios.app/Endfield
Identifier:          com.gryphline.endfield.ios
Version:             1.0.13 (0)
AppStoreTools:       17C53
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.gryphline.endfield.ios [5069]
User ID:             501

Date/Time:           2026-01-27 19:43:06.6207 -0800
Launch Time:         2026-01-27 19:42:41.5144 -0800
Hardware Model:      Mac14,2
OS Version:          macOS 26.2 (25C56)
Release Type:        User

Crash Reporter Key:  D420FC34-1881-4F60-CF9C-F53744235926
Incident Identifier: 39CA6498-F989-4932-AD72-7C0984D71870

Sleep/Wake UUID:       FBC9B54B-E956-4BED-8A2C-98AEF94D3C60

Time Awake Since Boot: 11000 seconds
Time Since Wake:       11283 seconds

System Integrity Protection: enabled

Triggered by Thread: 3, Dispatch Queue: com.apple.root.default-qos

Exception Type:    EXC_CRASH (SIGABRT)
Exception Codes:   0x0000000000000000, 0x0000000000000000


Application Specific Information:
abort() called```
<!-- gh-comment-id:3808785011 --> @existence333 commented on GitHub (Jan 28, 2026): Similar issue, here's my error log in case it helps: ```Process: Endfield [4798] Path: /Users/USER/Library/Containers/io.playcover.PlayCover/*/com.gryphline.endfield.ios.app/Endfield Identifier: com.gryphline.endfield.ios Version: 1.0.13 (0) AppStoreTools: 17C53 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.gryphline.endfield.ios [5069] User ID: 501 Date/Time: 2026-01-27 19:43:06.6207 -0800 Launch Time: 2026-01-27 19:42:41.5144 -0800 Hardware Model: Mac14,2 OS Version: macOS 26.2 (25C56) Release Type: User Crash Reporter Key: D420FC34-1881-4F60-CF9C-F53744235926 Incident Identifier: 39CA6498-F989-4932-AD72-7C0984D71870 Sleep/Wake UUID: FBC9B54B-E956-4BED-8A2C-98AEF94D3C60 Time Awake Since Boot: 11000 seconds Time Since Wake: 11283 seconds System Integrity Protection: enabled Triggered by Thread: 3, Dispatch Queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called```
Author
Owner

@MrWindDog commented on GitHub (Jan 28, 2026):

Quick update from network comparisons (iPhone vs PlayCover):

  • On launch the game fetches two resources from listdl.com (paths include iedsafe).
  • About ~1 minute later it triggers a third fetch (path includes gamesafe).
  • PlayCover crashes at that point.
  • Right at the crash moment it also attempts to open a connection to glcs.listdl.com:443, but the connection drops immediately because the app terminates.
  • On a real iPhone, there’s no crash and the glcs.listdl.com:443 connection stays alive.

Given the iedsafe / gamesafe paths, this looks related to the security / anti-cheat flow (ACE?).

I looked into this issue myself yesterday. My best guess is it is somehow related to certificates with listdl.com. It's the only thing that matched what I was seeing in Wireshark.

<!-- gh-comment-id:3814445517 --> @MrWindDog commented on GitHub (Jan 28, 2026): > Quick update from network comparisons (iPhone vs PlayCover): > > * On launch the game fetches two resources from `listdl.com` (paths include `iedsafe`). > * About ~1 minute later it triggers a third fetch (path includes `gamesafe`). > * **PlayCover crashes at that point.** > * Right at the crash moment it also attempts to open a connection to `glcs.listdl.com:443`, but the connection drops immediately because the app terminates. > * On a real iPhone, there’s no crash and the `glcs.listdl.com:443` connection stays alive. > > Given the `iedsafe` / `gamesafe` paths, this looks related to the security / anti-cheat flow (ACE?). I looked into this issue myself yesterday. My best guess is it is somehow related to certificates with listdl.com. It's the only thing that matched what I was seeing in Wireshark.
Author
Owner

@Infinityphoen1x commented on GitHub (Jan 29, 2026):

Duet Night Abyss had the same issue. It links to an online config file (config2.yaml for Endifeld). Duet Night Abyss' one is this: https://dl.listdl.com/gamesafe/mobile/huiwan/ios/com.panstudio.duetnightabyss.arpg.global/config2.xml
And Endfield's one is just a different file type, config2.yaml. You can locate the config2/3 files in Data in playcover, and they have a hash attached, but from what I've found out with research is that it prompts the laptop for more than 'device' name but hardware capability and other similar stuff, and blocks the request to authorise the game session if it doesn't match the specified device (aka mac, iphone, etc.). As for why it lasts a minute - probably just takes that long to get a response. Anywho, because the playcover 'masking' of devices isn't perfect, the hash config files aren't allowed through and we crash. From my experience with Duet Night Abyss it often turns up as looking like render issues or hardware conflicts in the terminal/ crash output, but if it's the anti-cheat sending a response back that our device is 'incompatible' and unable to implement the stuff in the game then the game probably crashes even though it does actually work. I think Huiwan is closely related to Tencent (or owned by them) Who use kernel-level Anti Cheat (ACE)

<!-- gh-comment-id:3814838719 --> @Infinityphoen1x commented on GitHub (Jan 29, 2026): Duet Night Abyss had the same issue. It links to an online config file (config2.yaml for Endifeld). Duet Night Abyss' one is this: https://dl.listdl.com/gamesafe/mobile/huiwan/ios/com.panstudio.duetnightabyss.arpg.global/config2.xml And Endfield's one is just a different file type, config2.yaml. You can locate the config2/3 files in Data in playcover, and they have a hash attached, but from what I've found out with research is that it prompts the laptop for more than 'device' name but hardware capability and other similar stuff, and blocks the request to authorise the game session if it doesn't match the specified device (aka mac, iphone, etc.). As for why it lasts a minute - probably just takes that long to get a response. Anywho, because the playcover 'masking' of devices isn't perfect, the hash config files aren't allowed through and we crash. From my experience with Duet Night Abyss it often turns up as looking like render issues or hardware conflicts in the terminal/ crash output, but if it's the anti-cheat sending a response back that our device is 'incompatible' and unable to implement the stuff in the game then the game probably crashes even though it does actually work. I think Huiwan is closely related to Tencent (or owned by them) Who use kernel-level Anti Cheat (ACE)
Author
Owner

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

Duplicate of #2060

<!-- gh-comment-id:3822399622 --> @ohaiibuzzle commented on GitHub (Jan 30, 2026): Duplicate of #2060
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#1388
No description provided.