[GH-ISSUE #1946] [Bug]: PlayCover crashes as I try to install Honkai Star Rail ver3.5 #1285

New issue

Closed

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

kerem commented

2026-03-03 19:05:32 +03:00

Owner

Originally created by @Sethos0531 on GitHub (Aug 17, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1946

Describe the bug

When I tried to install the .ipa file of hsr ver3.5 downloaded from here, https://decrypt.day/app/id1599719154/dl/qKyvuLvXZciQYE1aT63sb
the PlayCover app crashed.

Note: My Mac's os version is Mac OS Sequoia 15.6

Steps to reproduce

Delete the ipa file and downloaded a new one from the same page. Then I tried to install it with the PlayCover app.

Expected behaviour

The HSR app should have been added to the App library.

Crash log

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               PlayCover [41265]
Path:                  /Applications/PlayCover.app/Contents/MacOS/PlayCover
Identifier:            io.playcover.PlayCover
Version:               3.1.0 (856)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2025-08-17 16:26:13.3553 +0900
OS Version:            macOS 15.6 (24G84)
Report Version:        12
Anonymous UUID:        B5ADBA64-E979-8C6C-69A7-E53C3C569F9F

Sleep/Wake UUID:       DFADFFEF-C96A-42FA-91D5-451C59945204

Time Awake Since Boot: 420000 seconds
Time Since Wake:       2945 seconds

System Integrity Protection: enabled

Crashed Thread:        12  Dispatch queue: io.playcover.PlayCover.URLExtension (QOS: USER_INITIATED)

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0xfffffffffffffff0
Exception Codes:       0x0000000000000001, 0xfffffffffffffff0

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [41265]

VM Region Info: 0xfffffffffffffff0 is not in any region.  
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      UNUSED SPACE AT END

Thread 12 Crashed::  Dispatch queue: io.playcover.PlayCover.URLExtension (QOS: USER_INITIATED)
0   libswiftCore.dylib            	       0x1a884d860 _swift_release_dealloc + 32
1   libswiftCore.dylib            	       0x1a884e750 bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1>>::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 152
2   PlayCover                     	       0x104e27c90 0x104d44000 + 933008
3   PlayCover                     	       0x104d5b3f4 0x104d44000 + 95220
4   PlayCover                     	       0x104d5eeb4 0x104d44000 + 110260
5   PlayCover                     	       0x104df758c 0x104d44000 + 734604
6   PlayCover                     	       0x104df7664 0x104d44000 + 734820
7   Foundation                    	       0x1983b10ac __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 24
8   Foundation                    	       0x1983b0f74 -[NSBlockOperation main] + 96
9   Foundation                    	       0x1983b0f0c __NSOPERATION_IS_INVOKING_MAIN__ + 16
10  Foundation                    	       0x1983b027c -[NSOperation start] + 640
11  Foundation                    	       0x1983afff4 __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 16
12  Foundation                    	       0x1983afee4 __NSOQSchedule_f + 164
13  libdispatch.dylib             	       0x196b6b338 _dispatch_block_async_invoke2 + 148
14  libdispatch.dylib             	       0x196b7585c _dispatch_client_callout + 16
15  libdispatch.dylib             	       0x196b605e0 _dispatch_continuation_pop + 596
16  libdispatch.dylib             	       0x196b5fc54 _dispatch_async_redirect_invoke + 580
17  libdispatch.dylib             	       0x196b6de30 _dispatch_root_queue_drain + 364
18  libdispatch.dylib             	       0x196b6e5d4 _dispatch_worker_thread2 + 156
19  libsystem_pthread.dylib       	       0x196d0fe28 _pthread_wqthread + 232
20  libsystem_pthread.dylib       	       0x196d0eb74 start_wqthread + 8

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 @Sethos0531 on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1946 ### Describe the bug When I tried to install the .ipa file of hsr ver3.5 downloaded from here, [https://decrypt.day/app/id1599719154/dl/qKyvuLvXZciQYE1aT63sb](url) the PlayCover app crashed. Note: My Mac's os version is Mac OS Sequoia 15.6 ### Steps to reproduce Delete the ipa file and downloaded a new one from the same page. Then I tried to install it with the PlayCover app. ### Expected behaviour The HSR app should have been added to the App library. ### Crash log ```shell ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: PlayCover [41265] Path: /Applications/PlayCover.app/Contents/MacOS/PlayCover Identifier: io.playcover.PlayCover Version: 3.1.0 (856) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-08-17 16:26:13.3553 +0900 OS Version: macOS 15.6 (24G84) Report Version: 12 Anonymous UUID: B5ADBA64-E979-8C6C-69A7-E53C3C569F9F Sleep/Wake UUID: DFADFFEF-C96A-42FA-91D5-451C59945204 Time Awake Since Boot: 420000 seconds Time Since Wake: 2945 seconds System Integrity Protection: enabled Crashed Thread: 12 Dispatch queue: io.playcover.PlayCover.URLExtension (QOS: USER_INITIATED) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffff0 Exception Codes: 0x0000000000000001, 0xfffffffffffffff0 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [41265] VM Region Info: 0xfffffffffffffff0 is not in any region. REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> UNUSED SPACE AT END Thread 12 Crashed:: Dispatch queue: io.playcover.PlayCover.URLExtension (QOS: USER_INITIATED) 0 libswiftCore.dylib 0x1a884d860 _swift_release_dealloc + 32 1 libswiftCore.dylib 0x1a884e750 bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1>>::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 152 2 PlayCover 0x104e27c90 0x104d44000 + 933008 3 PlayCover 0x104d5b3f4 0x104d44000 + 95220 4 PlayCover 0x104d5eeb4 0x104d44000 + 110260 5 PlayCover 0x104df758c 0x104d44000 + 734604 6 PlayCover 0x104df7664 0x104d44000 + 734820 7 Foundation 0x1983b10ac __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 24 8 Foundation 0x1983b0f74 -[NSBlockOperation main] + 96 9 Foundation 0x1983b0f0c __NSOPERATION_IS_INVOKING_MAIN__ + 16 10 Foundation 0x1983b027c -[NSOperation start] + 640 11 Foundation 0x1983afff4 __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 16 12 Foundation 0x1983afee4 __NSOQSchedule_f + 164 13 libdispatch.dylib 0x196b6b338 _dispatch_block_async_invoke2 + 148 14 libdispatch.dylib 0x196b7585c _dispatch_client_callout + 16 15 libdispatch.dylib 0x196b605e0 _dispatch_continuation_pop + 596 16 libdispatch.dylib 0x196b5fc54 _dispatch_async_redirect_invoke + 580 17 libdispatch.dylib 0x196b6de30 _dispatch_root_queue_drain + 364 18 libdispatch.dylib 0x196b6e5d4 _dispatch_worker_thread2 + 156 19 libsystem_pthread.dylib 0x196d0fe28 _pthread_wqthread + 232 20 libsystem_pthread.dylib 0x196d0eb74 start_wqthread + 8 ``` ### 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

2026-03-03 19:05:32 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 19:05:33 +03:00

Author

Owner

@Kyle-Ye commented on GitHub (Sep 1, 2025):

Also encounter the issue when I use the latest 3.1 release. So I clone the repo and build it from source. And the issue is gone. Looks like the issue is already fixed. But there is no corresponding release yet.

@Kyle-Ye commented on GitHub (Sep 1, 2025): Also encounter the issue when I use the latest 3.1 release. So I clone the repo and build it from source. And the issue is gone. Looks like the issue is already fixed. But there is no corresponding release yet.

kerem referenced this issue

2026-03-03 19:09:16 +03:00

[PR #1285] [MERGED] Fix build output file name #1846

kerem referenced this issue

2026-03-03 19:09:16 +03:00

[PR #1286] [CLOSED] Merge develop into stable #1848