[GH-ISSUE #1344] [Game Support]: ONE PIECE Bounty Rush #790

New issue

Open

opened 2026-03-03 19:01:02 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:01:02 +03:00

Owner

Originally created by @Mujiko-013 on GitHub (Jan 24, 2024).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1344

App Store link

https://apps.apple.com/us/app/one-piece-bounty-rush/id1343688545?uo=4

Current issues

Game fails to install
Game fails to open
Game crashes randomly during gameplay
Game does not work with keymapping
Game experiences graphical issues or broken UI
Game fails to connect to servers or complete download

More details

After completing the installation of the latest update and starting the game, the following error message will appear.

MacOS : Sonoma14.2.1 (23C71)
PlayCover nightly (558)

Crash log

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

Process:               Bounty [3139]
Path:                  /Users/USER/Library/Containers/io.playcover.PlayCover/Bounty.app/Bounty
Identifier:            jp.co.bandainamcoent.BNEI0297
Version:               70000 (70000)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2024-01-24 15:33:20.1283 +0700
OS Version:            macOS 14.2.1 (23C71)
Report Version:        12
Anonymous UUID:        9E1758CF-5FF3-414B-CD29-3949CDC6EB67

Sleep/Wake UUID:       7A4793FA-D978-451C-BB8B-4D033E555796

Time Awake Since Boot: 4300 seconds
Time Since Wake:       2745 seconds

System Integrity Protection: enabled

Crashed Thread:        74

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0001f513adbcd460 -> 0x00007513adbcd460 (possible pointer authentication failure)
Exception Codes:       0x0000000000000001, 0x0001f513adbcd460

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

VM Region Info: 0x7513adbcd460 is not in any region.  Bytes after previous region: 23173726524513  
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      MALLOC_NANO              600000000000-600020000000 [512.0M] rw-/rwx SM=PRV  
--->  
      UNUSED SPACE AT END
-
- 
-

Model: Mac14,2, BootROM 10151.61.4, proc 8:4:4 processors, 8 GB, SMC 
Graphics: Apple M2, Apple M2, Built-In
Display: Color LCD, 2560 x 1664 Retina, Main, MirrorOff, Online
Memory Module: LPDDR5, Hynix
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x4387), wl0: Sep  1 2023 19:46:07 version 20.10.1073.3.8.7.165 FWID 01-b66346c5
AirPort: 
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB31Bus
Thunderbolt Bus: Laptop, Apple Inc.
Thunderbolt Bus: Laptop, Apple Inc.

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 @Mujiko-013 on GitHub (Jan 24, 2024). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1344 ### App Store link https://apps.apple.com/us/app/one-piece-bounty-rush/id1343688545?uo=4 ### Current issues - [ ] Game fails to install - [X] Game fails to open - [ ] Game crashes randomly during gameplay - [ ] Game does not work with keymapping - [ ] Game experiences graphical issues or broken UI - [ ] Game fails to connect to servers or complete download ### More details After completing the installation of the latest update and starting the game, the following error message will appear. MacOS : Sonoma14.2.1 (23C71) PlayCover nightly (558) ### Crash log ```shell ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Bounty [3139] Path: /Users/USER/Library/Containers/io.playcover.PlayCover/Bounty.app/Bounty Identifier: jp.co.bandainamcoent.BNEI0297 Version: 70000 (70000) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-01-24 15:33:20.1283 +0700 OS Version: macOS 14.2.1 (23C71) Report Version: 12 Anonymous UUID: 9E1758CF-5FF3-414B-CD29-3949CDC6EB67 Sleep/Wake UUID: 7A4793FA-D978-451C-BB8B-4D033E555796 Time Awake Since Boot: 4300 seconds Time Since Wake: 2745 seconds System Integrity Protection: enabled Crashed Thread: 74 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0001f513adbcd460 -> 0x00007513adbcd460 (possible pointer authentication failure) Exception Codes: 0x0000000000000001, 0x0001f513adbcd460 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [3139] VM Region Info: 0x7513adbcd460 is not in any region. Bytes after previous region: 23173726524513 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL MALLOC_NANO 600000000000-600020000000 [512.0M] rw-/rwx SM=PRV ---> UNUSED SPACE AT END - - - Model: Mac14,2, BootROM 10151.61.4, proc 8:4:4 processors, 8 GB, SMC Graphics: Apple M2, Apple M2, Built-In Display: Color LCD, 2560 x 1664 Retina, Main, MirrorOff, Online Memory Module: LPDDR5, Hynix AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x4387), wl0: Sep 1 2023 19:46:07 version 20.10.1073.3.8.7.165 FWID 01-b66346c5 AirPort: Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports Network Service: Wi-Fi, AirPort, en0 USB Device: USB31Bus USB Device: USB31Bus Thunderbolt Bus: Laptop, Apple Inc. Thunderbolt Bus: Laptop, Apple Inc. ``` ### 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 added the

game-support

label

2026-03-03 19:01:02 +03:00

kerem commented

2026-03-03 19:01:03 +03:00

Author

Owner

@Mujiko-013 commented on GitHub (Jan 24, 2024):

How do I set up the application? or do I have to install another version of PlayCover Nightly? Because PlayCover 3.0.0 Beta 2 has the same problem...

@Mujiko-013 commented on GitHub (Jan 24, 2024): How do I set up the application? or do I have to install another version of PlayCover Nightly? Because PlayCover 3.0.0 Beta 2 has the same problem...

kerem commented

2026-03-03 19:01:03 +03:00

Author

Owner

@User32015 commented on GitHub (Mar 16, 2024):

Do you have the same problem as me? I can open the game and all that, but every time, after like 20 seconds, no matter what I am doing, the game crashes. I've tried all of the things to try and make this work. Wasn't able. I've even tried to remove Play Tools, wasn't the cause of the problem.

@User32015 commented on GitHub (Mar 16, 2024): Do you have the same problem as me? I can open the game and all that, but every time, after like 20 seconds, no matter what I am doing, the game crashes. I've tried all of the things to try and make this work. Wasn't able. I've even tried to remove Play Tools, wasn't the cause of the problem.

kerem commented

2026-03-03 19:01:03 +03:00

Author

Owner

@KezzaJNR commented on GitHub (Jan 1, 2026):

Do you have the same problem as me? I can open the game and all that, but every time, after like 20 seconds, no matter what I am doing, the game crashes. I've tried all of the things to try and make this work. Wasn't able. I've even tried to remove Play Tools, wasn't the cause of the problem.

I think it has some sort of sideloading protection, because if u sideload the game it crashes even with a certificate im pretty sure, they added this after they started banning all the hackers

@KezzaJNR commented on GitHub (Jan 1, 2026): > Do you have the same problem as me? I can open the game and all that, but every time, after like 20 seconds, no matter what I am doing, the game crashes. I've tried all of the things to try and make this work. Wasn't able. I've even tried to remove Play Tools, wasn't the cause of the problem. I think it has some sort of sideloading protection, because if u sideload the game it crashes even with a certificate im pretty sure, they added this after they started banning all the hackers

kerem referenced this issue

2026-03-03 19:08:44 +03:00

[PR #790] [CLOSED] Add 2 more iPad models to choose from #1753