[GH-ISSUE #1239] Abandoned, please delete or close this issue, thanks #716

New issue

Closed

opened 2026-03-03 19:00:23 +03:00 by kerem · 39 comments

kerem commented 2026-03-03 19:00:23 +03:00

Owner

Copy link

Originally created by @Coresi7 on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1239

Abandoned, please delete or close this issue, thanks

Originally created by @Coresi7 on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1239 Abandoned, please delete or close this issue, thanks

kerem 2026-03-03 19:00:23 +03:00

• closed this issue
• added the
  app-support
  documentation
  labels

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@TheMoonThatRises commented on GitHub (Nov 30, 2023):

You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain.

<!-- gh-comment-id:1833164842 --> @TheMoonThatRises commented on GitHub (Nov 30, 2023): You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain.

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Nov 30, 2023):

You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain.

We cannot, as you see, we can't reproduce this issue, I'm using xcode to build and test our game on mac os silicon everyday. Could you give me some hint of how to reproduce it without playcover? Or any ideas of which we can suspect?
if you mean we might get crash under path contains Chinese, this is App Store's strategy, the ipa we submit should looks like "Z_release__iOS_1.6.16.1016__rxxxxxx_bxxx_release.ipa", so the path issue is out of our control.

However, if users from playcover hint the issue, please acquire game log to us, it should locate at com.tencent.jkchess/yxzg/net. Or, let user upload their log via "修复(Fix)", "上传日志(Upload Log)" menu at login and server select stage, and tell us uid (should looks like a 9-10 dit number) locate at userinfo page.
Add Chinese instruction for other users who occur the same issue:
然而，如果有用户发生了同样的问题（没有因为将金铲铲之战重命名为jkchess造成崩溃），请上传日志，应该位于 com.tencent.jkchess/yxzg/net，或者告知我们UID（位于角色信息处的一串数字）的同时，通过游戏登录界面的修复 —— 上传日志功能上传日志。

<!-- gh-comment-id:1833193874 --> @Coresi7 commented on GitHub (Nov 30, 2023): > You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain. We cannot, as you see, we can't reproduce this issue, I'm using xcode to build and test our game on mac os silicon everyday. Could you give me some hint of how to reproduce it without playcover? Or any ideas of which we can suspect? if you mean we might get crash under path contains Chinese, this is App Store's strategy, the ipa we submit should looks like "Z_release__iOS_1.6.16.1016__rxxxxxx_bxxx_release.ipa", so the path issue is out of our control. However, if users from playcover hint the issue, please acquire game log to us, it should locate at com.tencent.jkchess/yxzg/net. Or, let user upload their log via "修复(Fix)", "上传日志(Upload Log)" menu at login and server select stage, and tell us uid (should looks like a 9-10 dit number) locate at userinfo page. Add Chinese instruction for other users who occur the same issue: 然而，如果有用户发生了同样的问题（没有因为将金铲铲之战重命名为jkchess造成崩溃），请上传日志，应该位于 com.tencent.jkchess/yxzg/net，或者告知我们UID（位于角色信息处的一串数字）的同时，通过游戏登录界面的修复 —— 上传日志功能上传日志。

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@XuYicong commented on GitHub (Nov 30, 2023):

For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model.

In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders.

I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue.

But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately.

Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check PlayCover/AppInstaller/Installer.swift for details. I suspect there are some pathing mistakes in this.

You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause.

<!-- gh-comment-id:1833939978 --> @XuYicong commented on GitHub (Nov 30, 2023): For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model. <img width="1012" alt="图片" src="https://github.com/PlayCover/PlayCover/assets/16048758/1a4ff0c2-1598-4438-9d35-7f3260e06950"> In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders. I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue. But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately. Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check `PlayCover/AppInstaller/Installer.swift` for details. I suspect there are some pathing mistakes in this. You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause.

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@Keep-hair-loss commented on GitHub (Dec 1, 2023):

First of all, thanks for your help. My system is macOS Sonoma 14.1.1
The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.

That's what the game reminds me.

首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。
游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。

<!-- gh-comment-id:1835387142 --> @Keep-hair-loss commented on GitHub (Dec 1, 2023): First of all, thanks for your help. My system is macOS Sonoma 14.1.1 The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.  That's what the game reminds me.  首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。 游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 1, 2023):

For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model. In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders.

I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue.

But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately.

Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check PlayCover/AppInstaller/Installer.swift for details. I suspect there are some pathing mistakes in this.

You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause.

Oh, I recently noticed that Apple will try to fake its deviceModel, such as "iPad8,6" (ipad pro 12.9inch 3rd gen, with a12x bionic) for silicon mac, but it did provide an api to tell me that, so I have to modify our Unity engine build (we are using 2018.4.25 without iosAppOnMac api support, so I brought it back today) to add this detection. So it's not under playcover's control and I'm adding some advanced features for mac devices. This require a major version update, and it's hopefully to add, such as advanced graphics features, and keyboard support for mac devices on Chinese lunar spring festival version.

For Chinese name problems, I'll try to look into it. But this would be in low priority because we are under developing new features for our next major version, and for me, I need to add some feature for mac devices as well. I'll give it a try because without playcover, our effort will be useless, until we pronounce to officially support mac os platform.

It looks like the game itself will apply less anti-cheat or anti-cracker feature if the ios device is not jail braked, so playcover should be fine. However, we use an isolated sdk to provide the anti-cheat support, and this sdk is not under our control. So one day this stategy might change, and they will never inform even to us.

<!-- gh-comment-id:1835681637 --> @Coresi7 commented on GitHub (Dec 1, 2023): > For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model. <img alt="图片" width="1012" src="https://private-user-images.githubusercontent.com/16048758/286954469-1a4ff0c2-1598-4438-9d35-7f3260e06950.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDE0MTkwNDIsIm5iZiI6MTcwMTQxODc0MiwicGF0aCI6Ii8xNjA0ODc1OC8yODY5NTQ0NjktMWE0ZmYwYzItMTU5OC00NDM4LTlkMzUtN2YzMjYwZTA2OTUwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjAxVDA4MTkwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0ODM5OWU0ZDI2NDM4YWMyOTJjZDAwMDM5OWQ1ZGFiNDAyYzlkYWUyN2ZkNWM5NGI5ZDJiZWMzOTIwZGUwNzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.FoRSIRBwBkvGhPlnwg3UKMdfujatmE6x2xH0yb5urkI"> In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders. > > I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue. > > But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately. > > Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check `PlayCover/AppInstaller/Installer.swift` for details. I suspect there are some pathing mistakes in this. > > You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause. Oh, I recently noticed that Apple will try to fake its deviceModel, such as "iPad8,6" (ipad pro 12.9inch 3rd gen, with a12x bionic) for silicon mac, but it did provide an api to tell me that, so I have to modify our Unity engine build (we are using 2018.4.25 without iosAppOnMac api support, so I brought it back today) to add this detection. So it's not under playcover's control and I'm adding some advanced features for mac devices. This require a major version update, and it's hopefully to add, such as advanced graphics features, and keyboard support for mac devices on Chinese lunar spring festival version. For Chinese name problems, I'll try to look into it. But this would be in low priority because we are under developing new features for our next major version, and for me, I need to add some feature for mac devices as well. I'll give it a try because without playcover, our effort will be useless, until we pronounce to officially support mac os platform. It looks like the game itself will apply less anti-cheat or anti-cracker feature if the ios device is not jail braked, so playcover should be fine. However, we use an isolated sdk to provide the anti-cheat support, and this sdk is not under our control. So one day this stategy might change, and they will never inform even to us.

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 1, 2023):

First of all, thanks for your help. My system is macOS Sonoma 14.1.1 The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.

That's what the game reminds me.

首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。 游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。

We use GVoice sdk for in-game voice support, I'll try to ask them what went wrong on mac. But we have no plan to upgrade sdk version so if problem exists within, will takes one or more major versions to fix it, but if it's our mistake, well, I will try to look into it.
Please share your uid and upload your log to me follow the steps I mentioned before. Notice: not your QQ or WeChat id for privacy consideration.

游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。
麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。

<!-- gh-comment-id:1835683371 --> @Coresi7 commented on GitHub (Dec 1, 2023): > First of all, thanks for your help. My system is macOS Sonoma 14.1.1 The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.  > > That's what the game reminds me.  > > 首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。 游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。 We use GVoice sdk for in-game voice support, I'll try to ask them what went wrong on mac. But we have no plan to upgrade sdk version so if problem exists within, will takes one or more major versions to fix it, but if it's our mistake, well, I will try to look into it. Please share your uid and upload your log to me follow the steps I mentioned before. Notice: not your QQ or WeChat id for privacy consideration. 游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。 麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。

kerem commented 2026-03-03 19:00:24 +03:00

Author

Owner

Copy link

@Keep-hair-loss commented on GitHub (Dec 2, 2023):

游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。
麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。

感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996

我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。

Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996.
I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game.

<!-- gh-comment-id:1837114725 --> @Keep-hair-loss commented on GitHub (Dec 2, 2023): > 游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。 > 麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。 感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996 我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。   --- Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996. I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 4, 2023):

游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。
麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。

感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996

我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。

Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996. I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game.

Thanks, problem reproduced, and it does not matter if you use playcover or not, which means this should has something wrong in our side. But we are still investigating if this problem exists in Gvoice or us. For further information, I'll inform you here.
感谢，问题已经查实确实存在且内部成功复现，与PlayCover无关，我们正在核实该问题是在sdk侧还是我们。有进展会回复你。

<!-- gh-comment-id:1837914387 --> @Coresi7 commented on GitHub (Dec 4, 2023): > > 游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。 > > 麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。 > > 感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996 > > 我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。 > > ##  >  > Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996. I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game. Thanks, problem reproduced, and it does not matter if you use playcover or not, which means this should has something wrong in our side. But we are still investigating if this problem exists in Gvoice or us. For further information, I'll inform you here. 感谢，问题已经查实确实存在且内部成功复现，与PlayCover无关，我们正在核实该问题是在sdk侧还是我们。有进展会回复你。

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 4, 2023):

For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model. In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders.

I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue.

But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately.

Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check PlayCover/AppInstaller/Installer.swift for details. I suspect there are some pathing mistakes in this.

You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause.

I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there.

<!-- gh-comment-id:1838452838 --> @Coresi7 commented on GitHub (Dec 4, 2023): > For game dev, you can test with playtools removed to avoid bypassing behaviours like faking device model. <img alt="图片" width="1012" src="https://private-user-images.githubusercontent.com/16048758/286954469-1a4ff0c2-1598-4438-9d35-7f3260e06950.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDE2OTAwNjAsIm5iZiI6MTcwMTY4OTc2MCwicGF0aCI6Ii8xNjA0ODc1OC8yODY5NTQ0NjktMWE0ZmYwYzItMTU5OC00NDM4LTlkMzUtN2YzMjYwZTA2OTUwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjA0VDExMzYwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTEyODRmY2E3MjA5NWQ2MDY0ZTY1MmFkMWU4ZTA5NzJiN2UzMGM2YTliZTAyZDlmZGJlNTdkZjVkZDVjMTA2YjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.VnwY053ODU_27RyBPXy8m59wEfKLrmMyprb5avkKlVY"> In this interface, click 移除PlayTools, and then you can test your own adaptations like keyboard, touchpad and shaders. > > I think the Chinese name crashing is an issue on our side, cause it also happens to 崩坏3 and 崩坏:星穹铁道. But we have little knowledge on it. You're welcome to open PRs to help us solve this issue. > > But as for the crash report specifically in your screenshot, that's probably some fault in playtools, not the naming affairs. That should be a separate issue and should be investigated separately. > > Basically playtools is a dylib that's injected to the game when installing. You can consider it a 善意外挂. If any problem persists even when playtools removed (and cannot reproduce without playcover), that's probably something wrong with the app install procedures of playcover. You can check `PlayCover/AppInstaller/Installer.swift` for details. I suspect there are some pathing mistakes in this. > > You may also try Sideloadly, another sideloading software similar to playcover but with less functionality but (possibly) more stable. Playcover can also "export to sideloadly" for an app. You can try multiple combinations to get a clue to locate the cause. I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 4, 2023):

You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain.

The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue.

<!-- gh-comment-id:1838599220 --> @Coresi7 commented on GitHub (Dec 4, 2023): > You can take a look at this issue which currently tracks the issue: #1104. I'm not sure as to why the name specifically causes the app to crash, but you could look into that. As to not pretend to be a certain device model, that could be possible, but I personally am not certain. The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@XuYicong commented on GitHub (Dec 4, 2023):

I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there.

You can build PlayCover using xcode, then run your game via that xcode build version of PlayCover. The whole process tree would be in xcode-debug env.

<!-- gh-comment-id:1839503908 --> @XuYicong commented on GitHub (Dec 4, 2023): > I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there. You can build PlayCover using xcode, then run your game via that xcode build version of PlayCover. The whole process tree would be in xcode-debug env.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@ohaiibuzzle commented on GitHub (Dec 5, 2023):

The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue.

To be completely fair to you this is our issue that we should fix properly on PlayCover (We went to naming the app bundle using the same as its actual name in 2.0). It’s not something you’d ever expect (on iOS they are always guaranteed to be UUID using ASCII characters)

<!-- gh-comment-id:1840148946 --> @ohaiibuzzle commented on GitHub (Dec 5, 2023): > The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue. To be completely fair to you this is our issue that we should fix properly on PlayCover (We went to naming the app bundle using the same as its actual name in 2.0). It’s not something you’d ever expect (on iOS they are always guaranteed to be UUID using ASCII characters)

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there.

You can build PlayCover using xcode, then run your game via that xcode build version of PlayCover. The whole process tree would be in xcode-debug env.

The crash stacktrace looks in our game side, I need to extract symbol there, so you may give me a way to run my app built by xcode via playcover.

<!-- gh-comment-id:1840182858 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > I know what you mean, I caught a crash when using Chinese name with playcover, maybe you may tell me how to run our game via xcode using playcover, I have to try to debug it under playcover env, because I can't reproduce it via xcode run, so I cannot extract stacktrace symbol there. > > You can build PlayCover using xcode, then run your game via that xcode build version of PlayCover. The whole process tree would be in xcode-debug env. The crash stacktrace looks in our game side, I need to extract symbol there, so you may give me a way to run my app built by xcode via playcover.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue.

To be completely fair to you this is our issue that we should fix properly on PlayCover (We went to naming the app bundle using the same as its actual name in 2.0). It’s not something you’d ever expect (on iOS they are always guaranteed to be UUID using ASCII characters)

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

<!-- gh-comment-id:1840186128 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > The Chinese name crash is reproducable under playcover even in our dev version, but I cannot reproduce it in xcode build env, or run it without playcover by our enterprise apple signiture. Please give me way to try to run it debuggable in playcover, otherwise I can't extract stacktrace and help you to fix this issue. > > To be completely fair to you this is our issue that we should fix properly on PlayCover (We went to naming the app bundle using the same as its actual name in 2.0). It’s not something you’d ever expect (on iOS they are always guaranteed to be UUID using ASCII characters) It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。
麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。

感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996

我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。

Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996. I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game.

We disabled gvoice sdk ask permission because it will pop up permission request window all the time, and we detected there's something wrong with this sdk, so we disable it for now. We've issue a ticket to sdk side, and wait for their solution.
由于问题出现在GVoice SDK一侧，这个问题解决之前，反复弹窗提醒授权实在是干扰游戏运行，故我们在Mac OS平台上暂时禁用这个功能，但是我已经将此问题反馈给了GVoice他们，请静待后续更新解决。

<!-- gh-comment-id:1840216402 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > 游戏内音频支持我们是使用Gvoice sdk提供的支持，我可以帮你问问他们并且测试这个功能是否在mac可用。但我们至少春节版本应该没有更新sdk的计划，故如果真因为sdk出的问题，或许可能需要若干个大版本解决，但如果是因为我们自己的问题，我们想想办法。 > > 麻烦参考我第二个回应来尝试上传一下日志并提供uid，注意，不是qq或者微信id，这有助于保护你的隐私。 > > 感谢您可以回复我的问题关于在macOS Sonoma 14.1.1 上运行游戏无法使用麦克风，也感谢你可以用中文回复我，我的游戏UID是 2866590996 > > 我在登陆界面上传了日志，希望对你们改进游戏能有有效的帮助。 > > ##  >  > Thank you for replying to my question about the inability to use the microphone when running the game on macOS Sonoma 14.1.1, and thank you for replying to me in Chinese, my game UID is 2866590996. I uploaded the log on the login interface, I hope it can be of effective help to you to improve the game. We disabled gvoice sdk ask permission because it will pop up permission request window all the time, and we detected there's something wrong with this sdk, so we disable it for now. We've issue a ticket to sdk side, and wait for their solution. 由于问题出现在GVoice SDK一侧，这个问题解决之前，反复弹窗提醒授权实在是干扰游戏运行，故我们在Mac OS平台上暂时禁用这个功能，但是我已经将此问题反馈给了GVoice他们，请静待后续更新解决。 

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@ohaiibuzzle commented on GitHub (Dec 5, 2023):

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

A hack I can come up with is basically to export the ipa with its CFDisplayName key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much

github.com/PlayCover/PlayCover@4c504e35cc/PlayCover/AppInstaller/Installer.swift (L206)

I'll see if there is a feasible way that we can convert all existing app bundle to CFBundleName instead of CFDisplayName, it would reduce headache for titles like Honkai Impact 3rd CN as well

<!-- gh-comment-id:1840219910 --> @ohaiibuzzle commented on GitHub (Dec 5, 2023): > It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product. A hack I can come up with is basically to export the ipa with its `CFDisplayName` key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much https://github.com/PlayCover/PlayCover/blob/4c504e35ccf686a8409e545c936c4488a8a66a26/PlayCover/AppInstaller/Installer.swift#L206 I'll see if there is a feasible way that we can convert all existing app bundle to `CFBundleName` instead of `CFDisplayName`, it would reduce headache for titles like Honkai Impact 3rd CN as well

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

A hack I can come up with is basically to export the ipa with its CFDisplayName key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much

github.com/PlayCover/PlayCover@4c504e35cc/PlayCover/AppInstaller/Installer.swift (L206)

I'll see if there is a feasible way that we can convert all existing app bundle to CFBundleName instead of CFDisplayName, it would reduce headache for titles like Honkai Impact 3rd CN as well

Thanks, I'll look into it.

<!-- gh-comment-id:1840227410 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product. > > A hack I can come up with is basically to export the ipa with its `CFDisplayName` key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much > > https://github.com/PlayCover/PlayCover/blob/4c504e35ccf686a8409e545c936c4488a8a66a26/PlayCover/AppInstaller/Installer.swift#L206 > > I'll see if there is a feasible way that we can convert all existing app bundle to `CFBundleName` instead of `CFDisplayName`, it would reduce headache for titles like Honkai Impact 3rd CN as well Thanks, I'll look into it.

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

A hack I can come up with is basically to export the ipa with its CFDisplayName key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much

github.com/PlayCover/PlayCover@4c504e35cc/PlayCover/AppInstaller/Installer.swift (L206)

I'll see if there is a feasible way that we can convert all existing app bundle to CFBundleName instead of CFDisplayName, it would reduce headache for titles like Honkai Impact 3rd CN as well

Problem founded, and I tried to extract the stack trace using symbol manually. It looks like something wrong with the path, which cause wwise crashed.
Wwise sound solution is widely used among a lot of games, so it's possible that same thing will happen to them.
However, I've diffed the path passed in if run our game directly with our enterprise signature, they are the same, looks like mac os will translate the path automatically. I don't know why because wwise is a black box for us.
By the way, the default base path (and default search path) for wwise is /path-to-app-container/Data/Raw/Audio/GeneratedSoundBanks/iOS, AKSoundEngine.AddBasePath is invoked to add wwise search path for DLC content downloaded.
@TheMoonThatRises @XuYicong @ohaiibuzzle

<!-- gh-comment-id:1840309845 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product. > > A hack I can come up with is basically to export the ipa with its `CFDisplayName` key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much > > https://github.com/PlayCover/PlayCover/blob/4c504e35ccf686a8409e545c936c4488a8a66a26/PlayCover/AppInstaller/Installer.swift#L206 > > I'll see if there is a feasible way that we can convert all existing app bundle to `CFBundleName` instead of `CFDisplayName`, it would reduce headache for titles like Honkai Impact 3rd CN as well <img width="1053" alt="Screenshot 2023-12-05 at 17 24 33" src="https://github.com/PlayCover/PlayCover/assets/21254846/32f1a40a-d8af-473a-8947-6fbfcf65ba70">    Problem founded, and I tried to extract the stack trace using symbol manually. It looks like something wrong with the path, which cause wwise crashed. Wwise sound solution is widely used among a lot of games, so it's possible that same thing will happen to them. However, I've diffed the path passed in if run our game directly with our enterprise signature, they are the same, looks like mac os will translate the path automatically. I don't know why because wwise is a black box for us. By the way, the default base path (and default search path) for wwise is /path-to-app-container/Data/Raw/Audio/GeneratedSoundBanks/iOS, AKSoundEngine.AddBasePath is invoked to add wwise search path for DLC content downloaded. @TheMoonThatRises @XuYicong @ohaiibuzzle

kerem commented 2026-03-03 19:00:25 +03:00

Author

Owner

Copy link

@ohaiibuzzle commented on GitHub (Dec 5, 2023):

Okay that one is legitimately… weird.

The Containers folders are actually not named using Unicode characters, if you open a terminal to it, they will actually use bundle IDs. macOS is just showing them as the app name in the Finder

<!-- gh-comment-id:1840736725 --> @ohaiibuzzle commented on GitHub (Dec 5, 2023): Okay that one is legitimately… weird. The `Containers` folders are actually not named using Unicode characters, if you open a terminal to it, they will actually use bundle IDs. macOS is just showing them as the app name in the Finder

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@XuYicong commented on GitHub (Dec 5, 2023):

bro I wonder if it's ok to leak your private code publicly. btw that 顺手提前检查一下 looks pretty weird, generally you don't do things by 顺手 in coding, that's definitely bringing unnecessary complexity with very little benefit. It not only decrease your branch coverage during testing aka. make testing harder, but also brings extra recognition burden to code readers.

and that "如果...那肯定就..." assertion looks pretty fragile or too implicit at the best, considering how it's phrased. That may be a result of your specific updating policy which is quite fragile to rely on in pretty low-level cpp code like this.

And that function name isMacOrMacSiliconDevice looks suspicious, I mean isn't the category of MacSilicon a part of Mac? It's kinda weird to or them.

And if it's not something wrong in playcover, please don't outsource your own work to the community.

<!-- gh-comment-id:1840876276 --> @XuYicong commented on GitHub (Dec 5, 2023): bro I wonder if it's ok to leak your private code publicly. btw that 顺手提前检查一下 looks pretty weird, generally you don't do things by 顺手 in coding, that's definitely bringing unnecessary complexity with very little benefit. It not only decrease your branch coverage during testing aka. make testing harder, but also brings extra recognition burden to code readers. and that "如果...那肯定就..." assertion looks pretty fragile or too implicit at the best, considering how it's phrased. That may be a result of your specific updating policy which is quite fragile to rely on in pretty low-level cpp code like this. And that function name `isMacOrMacSiliconDevice` looks suspicious, I mean isn't the category of `MacSilicon` a part of `Mac`? It's kinda weird to `or` them. And if it's not something wrong in playcover, please don't outsource your own work to the community.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

bro I wonder if it's ok to leak your private code publicly. btw that 顺手提前检查一下 looks pretty weird, generally you don't do things by 顺手 in coding, that's definitely bringing unnecessary complexity with very little benefit. It not only decrease your branch coverage during testing aka. make testing harder, but also brings extra recognition burden to code readers.

and that "如果...那肯定就..." assertion looks pretty fragile or too implicit at the best, considering how it's phrased. That may be a result of your specific updating policy which is quite fragile to rely on in pretty low-level cpp code like this.

And that function name isMacOrMacSiliconDevice looks suspicious, I mean isn't the category of MacSilicon a part of Mac? It's kinda weird to or them.

And if it's not something wrong in playcover, please don't outsource your own work to the community.

Thx! Code edited.

<!-- gh-comment-id:1840921295 --> @Coresi7 commented on GitHub (Dec 5, 2023): > bro I wonder if it's ok to leak your private code publicly. btw that 顺手提前检查一下 looks pretty weird, generally you don't do things by 顺手 in coding, that's definitely bringing unnecessary complexity with very little benefit. It not only decrease your branch coverage during testing aka. make testing harder, but also brings extra recognition burden to code readers. > > and that "如果...那肯定就..." assertion looks pretty fragile or too implicit at the best, considering how it's phrased. That may be a result of your specific updating policy which is quite fragile to rely on in pretty low-level cpp code like this. > > And that function name `isMacOrMacSiliconDevice` looks suspicious, I mean isn't the category of `MacSilicon` a part of `Mac`? It's kinda weird to `or` them. > > And if it's not something wrong in playcover, please don't outsource your own work to the community. Thx! Code edited.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@TheMoonThatRises commented on GitHub (Dec 5, 2023):

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

A hack I can come up with is basically to export the ipa with its CFDisplayName key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much

github.com/PlayCover/PlayCover@4c504e35cc/PlayCover/AppInstaller/Installer.swift (L206)

I'll see if there is a feasible way that we can convert all existing app bundle to CFBundleName instead of CFDisplayName, it would reduce headache for titles like Honkai Impact 3rd CN as well

This is basically what my PR in #1100 does, except it turns them into the Bundle ID, which I believe should be more unique than CFBundleName.

<!-- gh-comment-id:1840930602 --> @TheMoonThatRises commented on GitHub (Dec 5, 2023): > > It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product. > > A hack I can come up with is basically to export the ipa with its `CFDisplayName` key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much > > https://github.com/PlayCover/PlayCover/blob/4c504e35ccf686a8409e545c936c4488a8a66a26/PlayCover/AppInstaller/Installer.swift#L206 > > I'll see if there is a feasible way that we can convert all existing app bundle to `CFBundleName` instead of `CFDisplayName`, it would reduce headache for titles like Honkai Impact 3rd CN as well This is basically what my PR in #1100 does, except it turns them into the Bundle ID, which I believe should be more unique than CFBundleName.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

Okay that one is legitimately… weird.

The Containers folders are actually not named using Unicode characters, if you open a terminal to it, they will actually use bundle IDs. macOS is just showing them as the app name in the Finder

Yes, I've tested this, and indeed it uses the correct bundle name path in terminal.
So I don't know why but in our case the problem lies there, I've crashed 金铲铲之战 multiple times using playcover and the stacktrace is same. Is there somewhere to get the source code of wwise? Which might helps.
I noticed @TheMoonThatRises has issued a pr which might helps, I will give it a try when possible.

<!-- gh-comment-id:1840936791 --> @Coresi7 commented on GitHub (Dec 5, 2023): > Okay that one is legitimately… weird. > > The `Containers` folders are actually not named using Unicode characters, if you open a terminal to it, they will actually use bundle IDs. macOS is just showing them as the app name in the Finder Yes, I've tested this, and indeed it uses the correct bundle name path in terminal. So I don't know why but in our case the problem lies there, I've crashed 金铲铲之战 multiple times using playcover and the stacktrace is same. Is there somewhere to get the source code of wwise? Which might helps. I noticed @TheMoonThatRises has issued a pr which might helps, I will give it a try when possible.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product.

A hack I can come up with is basically to export the ipa with its CFDisplayName key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much
github.com/PlayCover/PlayCover@4c504e35cc/PlayCover/AppInstaller/Installer.swift (L206)

I'll see if there is a feasible way that we can convert all existing app bundle to CFBundleName instead of CFDisplayName, it would reduce headache for titles like Honkai Impact 3rd CN as well

This is basically what my PR in #1100 does, except it turns them into the Bundle ID, which I believe should be more unique than CFBundleName.

If the pr merged, just let me know and try again using the latest playcover nightly build.

<!-- gh-comment-id:1840939669 --> @Coresi7 commented on GitHub (Dec 5, 2023): > > > It's very kindly of you to tell me that, however we are under investigating what we can do to make a hotfix workaround instead of letting player change the name of our product. > > > > > > A hack I can come up with is basically to export the ipa with its `CFDisplayName` key modified, it's how PlayCover determines where to put the finalized app bundle. Since PlayCover deals with unsigned apps anyway, it's not like this would matter much > > https://github.com/PlayCover/PlayCover/blob/4c504e35ccf686a8409e545c936c4488a8a66a26/PlayCover/AppInstaller/Installer.swift#L206 > > > > I'll see if there is a feasible way that we can convert all existing app bundle to `CFBundleName` instead of `CFDisplayName`, it would reduce headache for titles like Honkai Impact 3rd CN as well > > This is basically what my PR in #1100 does, except it turns them into the Bundle ID, which I believe should be more unique than CFBundleName. If the pr merged, just let me know and try again using the latest playcover nightly build.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 5, 2023):

I've add some keyboard shotcuts for playing on mac and testing this feature. If possible, will take effect in the next major version.
Alphanumric 1-5: buy chess 1-5, if long press: show info for the chess instead of buying it.
D: refresh shop
S: show or hide shop (when in phone's composition, unavailable in pad's composition.)
F: buy exp using coin
X: lock/unlock shop
keyboard shotcut is unavailable for iOS and iPadOS devices (even connected to a bluetooth keyboard).

我增加了若干键盘操作，如果顺利的话或许将在下个大版本生效
按键1-5（主键盘）：购买1-5号棋子（长按：显示这个棋子的详细信息但不购买）
D：刷新商店
S：显示或者隐藏商店（需使用手机视图，对平板电脑视图无效）
F：购买经验
X：锁定/解锁商店
按键仅对Mac OS平台下生效，iOS和iPadOS平台下无效（即便是连接蓝牙键盘）

<!-- gh-comment-id:1841306413 --> @Coresi7 commented on GitHub (Dec 5, 2023): I've add some keyboard shotcuts for playing on mac and testing this feature. If possible, will take effect in the next major version. Alphanumric 1-5: buy chess 1-5, if long press: show info for the chess instead of buying it. D: refresh shop S: show or hide shop (when in phone's composition, unavailable in pad's composition.) F: buy exp using coin X: lock/unlock shop keyboard shotcut is unavailable for iOS and iPadOS devices (even connected to a bluetooth keyboard). 我增加了若干键盘操作，如果顺利的话或许将在下个大版本生效 按键1-5（主键盘）：购买1-5号棋子（长按：显示这个棋子的详细信息但不购买） D：刷新商店 S：显示或者隐藏商店（需使用手机视图，对平板电脑视图无效） F：购买经验 X：锁定/解锁商店 按键仅对Mac OS平台下生效，iOS和iPadOS平台下无效（即便是连接蓝牙键盘）

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 6, 2023):

First of all, thanks for your help. My system is macOS Sonoma 14.1.1 The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.

That's what the game reminds me.

首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。 游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。

A workaround fix for this issue has internally applied, we will try to ask for permission when loading into main hall for mac os platform. And is pending release for next major version. However we will still keep an eye on sdk side.
我们内部实现了一个绕过的解决方案，会在进入大厅的时机提前尝试申请麦克风权限。这项修复仅对macos生效，其他平台策略不变，仍然是在房间内尝试开麦，或者聊天当中尝试发送语音的时候申请权限，此项修复将在下一个赛季当中生效。我们仍然会继续跟进SDK侧看看他们何时发布修复版本。

<!-- gh-comment-id:1842533995 --> @Coresi7 commented on GitHub (Dec 6, 2023): > First of all, thanks for your help. My system is macOS Sonoma 14.1.1 The game works, but I can't use the microphone to communicate with my teammates. I've given jkchess access to the microphone.  > > That's what the game reminds me.  > > 首先感谢您可以提供帮助，我的系统是macOS Sonoma 14.1.1。 游戏可以正常运行，但是我是用不了麦克风和队友交流。我已经给jkchess麦克风权限。 A workaround fix for this issue has internally applied, we will try to ask for permission when loading into main hall for mac os platform. And is pending release for next major version. However we will still keep an eye on sdk side. 我们内部实现了一个绕过的解决方案，会在进入大厅的时机提前尝试申请麦克风权限。这项修复仅对macos生效，其他平台策略不变，仍然是在房间内尝试开麦，或者聊天当中尝试发送语音的时候申请权限，此项修复将在下一个赛季当中生效。我们仍然会继续跟进SDK侧看看他们何时发布修复版本。 <img width="828" alt="Screenshot 2023-12-06 at 17 59 00" src="https://github.com/PlayCover/PlayCover/assets/21254846/c9daed56-89a8-4eb9-a852-bb377ddf8b41">

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@XuYicong commented on GitHub (Dec 8, 2023):

Hello #1100 is merged. You may try it in nightly build tomorrow.

Edit: try nightly build 570

<!-- gh-comment-id:1847859147 --> @XuYicong commented on GitHub (Dec 8, 2023): Hello #1100 is merged. You may try it in nightly build tomorrow. Edit: try nightly build 570

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 11, 2023):

Hello #1100 is merged. You may try it in nightly build tomorrow.

Edit: try nightly build 570

Got it, trying

<!-- gh-comment-id:1849487377 --> @Coresi7 commented on GitHub (Dec 11, 2023): > Hello #1100 is merged. You may try it in nightly build tomorrow. > > Edit: try nightly build 570 Got it, trying

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Dec 11, 2023):

Hello #1100 is merged. You may try it in nightly build tomorrow.

Edit: try nightly build 570

I noticed that you've wrapped our app as "com.tencent.jkchess" without the requirements of upgrade or modify my app, and it does not crash anymore, however, I didn't test the version with playtools cause playtools.framework is not trusted.

Hello #1100 is merged. You may try it in nightly build tomorrow.

Edit: try nightly build 570

I don't know why the microphone and keyboard support are all missing, it looks like playcover will hide it as an ipad, even I try to uninstall playtool. Please remove such fake operation because thus something will go wrong on mac platform.

<!-- gh-comment-id:1849557139 --> @Coresi7 commented on GitHub (Dec 11, 2023): > Hello #1100 is merged. You may try it in nightly build tomorrow. > > Edit: try nightly build 570 I noticed that you've wrapped our app as "com.tencent.jkchess" without the requirements of upgrade or modify my app, and it does not crash anymore, however, I didn't test the version with playtools cause playtools.framework is not trusted. > Hello #1100 is merged. You may try it in nightly build tomorrow. > > Edit: try nightly build 570 I don't know why the microphone and keyboard support are all missing, it looks like playcover will hide it as an ipad, even I try to uninstall playtool. Please remove such fake operation because thus something will go wrong on mac platform.

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@James-Harden-13-R commented on GitHub (Dec 26, 2023):

I still have graphical issues after I removed PlayTools, though the crash didn't happen anymore. I wonder what I can do to solve the problem. Thanks.

macOS 12.4.1

playcover: 3.0.0 beta 2

<!-- gh-comment-id:1869448013 --> @James-Harden-13-R commented on GitHub (Dec 26, 2023): I still have graphical issues after I removed PlayTools, though the crash didn't happen anymore. I wonder what I can do to solve the problem. Thanks. macOS 12.4.1 playcover: 3.0.0 beta 2 

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@byitSen commented on GitHub (Dec 28, 2023):

所有需要麦克风权限的APP都无法正常使用语音，可能是系统本身问题。

<!-- gh-comment-id:1870912059 --> @byitSen commented on GitHub (Dec 28, 2023): 所有需要麦克风权限的APP都无法正常使用语音，可能是系统本身问题。

kerem commented 2026-03-03 19:00:26 +03:00

Author

Owner

Copy link

@Lantern-r commented on GitHub (Dec 30, 2023):

playcover: 3.0.0 beta 2
感谢您的帮助，在游戏中我遇见了两个小问题：

1. 在选择海克斯界面，一旦进入锁定阶段便不会出现投票按钮。如果在此前没有进行投票，则连投票框（圆圈）都进不去。
2. 在对局内无法打字，在大厅时可以。

<!-- gh-comment-id:1872548776 --> @Lantern-r commented on GitHub (Dec 30, 2023): playcover: 3.0.0 beta 2 感谢您的帮助，在游戏中我遇见了两个小问题： 1. 在选择海克斯界面，一旦进入锁定阶段便不会出现投票按钮。如果在此前没有进行投票，则连投票框（圆圈）都进不去。 2. 在对局内无法打字，在大厅时可以。

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@shycomet commented on GitHub (Jan 25, 2024):

@Coresi7 官方开发大佬，你好。
com.tencent.jkchess_1.6.16.ipa在PlayCover中正常安装
com.tencent.jkchess_1.6.17.ipa在PlayCover中安装直接报错，但是可以在Sideloadly中签名安装。我不知道是不是官方这次专门针对PlayCover的优化出了问题，请予以排查。

xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/jkchess'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/PlugIns/Notification.appex/Notification'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GCloudCore.framework/GCloudCore'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/crosCurl.framework/crosCurl'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSight.framework/CrashSight'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/kgvmp_dy.framework/kgvmp_dy'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/tersafe.framework/tersafe'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDataMaster.framework/TDataMaster'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKWebView.framework/MSDKWebView'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDMIDFA.framework/TDMIDFA'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/Hippy.framework/Hippy'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKSensitivity.framework/MSDKSensitivity'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/tgpa_wrapper.framework/tgpa_wrapper'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKDns.framework/MSDKDns'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKTDM.framework/MSDKTDM'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightCore.framework/CrashSightCore'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKSystem.framework/MSDKSystem'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GCloud.framework/GCloud'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKLBS.framework/MSDKLBS'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightAdapter.framework/CrashSightAdapter'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/PluginCrosCurl.framework/PluginCrosCurl'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GRobot.framework/GRobot'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKCore.framework/MSDKCore'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDMASA.framework/TDMASA'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKAdapter.framework/MSDKAdapter'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/enq_transceiver_dy.framework/enq_transceiver_dy'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GPM_dylib.framework/GPM_dylib'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightPlugin.framework/CrashSightPlugin'
xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GVoice_dylib.framework/GVoice_dylib'

<!-- gh-comment-id:1910696382 --> @shycomet commented on GitHub (Jan 25, 2024): @Coresi7 官方开发大佬，你好。 com.tencent.jkchess_1.6.16.ipa在PlayCover中正常安装 com.tencent.jkchess_1.6.17.ipa在PlayCover中安装直接报错，但是可以在Sideloadly中签名安装。我不知道是不是官方这次专门针对PlayCover的优化出了问题，请予以排查。  xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/jkchess' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/PlugIns/Notification.appex/Notification' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GCloudCore.framework/GCloudCore' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/crosCurl.framework/crosCurl' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSight.framework/CrashSight' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/kgvmp_dy.framework/kgvmp_dy' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/tersafe.framework/tersafe' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDataMaster.framework/TDataMaster' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKWebView.framework/MSDKWebView' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDMIDFA.framework/TDMIDFA' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/Hippy.framework/Hippy' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKSensitivity.framework/MSDKSensitivity' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/tgpa_wrapper.framework/tgpa_wrapper' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKDns.framework/MSDKDns' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKTDM.framework/MSDKTDM' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightCore.framework/CrashSightCore' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKSystem.framework/MSDKSystem' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GCloud.framework/GCloud' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKLBS.framework/MSDKLBS' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightAdapter.framework/CrashSightAdapter' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/PluginCrosCurl.framework/PluginCrosCurl' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GRobot.framework/GRobot' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKCore.framework/MSDKCore' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/TDMASA.framework/TDMASA' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/MSDKAdapter.framework/MSDKAdapter' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/enq_transceiver_dy.framework/enq_transceiver_dy' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GPM_dylib.framework/GPM_dylib' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/CrashSightPlugin.framework/CrashSightPlugin' xattr: [Errno 13] Permission denied: '/var/folders/qz/tw65t2qs0kvbj_17_9q0qnjr0000gn/T/TemporaryItems/NSIRD_PlayCover_A1JT3S/Payload/jkchess.app/Frameworks/GVoice_dylib.framework/GVoice_dylib'

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@shycomet commented on GitHub (Jan 25, 2024):

@Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。

同时也有小伙伴反馈同样的问题。

<!-- gh-comment-id:1910727934 --> @shycomet commented on GitHub (Jan 25, 2024): @Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。  同时也有小伙伴反馈同样的问题。

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Jan 30, 2024):

@Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。 同时也有小伙伴反馈同样的问题。

我个人不再推荐使用playcover，建议尝试sideloadly
I personally do not recommend using playcover anymore, now I recommend to run via sideloadly.

<!-- gh-comment-id:1916029394 --> @Coresi7 commented on GitHub (Jan 30, 2024): > @Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。  同时也有小伙伴反馈同样的问题。 我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly.

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@akss5768 commented on GitHub (Jan 30, 2024):

@Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。 同时也有小伙伴反馈同样的问题。

我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly.

sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用

<!-- gh-comment-id:1916348500 --> @akss5768 commented on GitHub (Jan 30, 2024): > > @Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。  同时也有小伙伴反馈同样的问题。 > > 我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly. sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Jan 30, 2024):

@Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。 同时也有小伙伴反馈同样的问题。

我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly.

sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用

不会吧？麦克风我在sideloadly环境验证过，若你用的是春节版本，应该是可以用的
playercover环境下使用麦克风我是真解决不了。不知道是SDK问题还是mac问题，麦克风权限我总是无法正确授权。

<!-- gh-comment-id:1916892839 --> @Coresi7 commented on GitHub (Jan 30, 2024): > > > @Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。  同时也有小伙伴反馈同样的问题。 > > > > > > 我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly. > > sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用 不会吧？麦克风我在sideloadly环境验证过，若你用的是春节版本，应该是可以用的 playercover环境下使用麦克风我是真解决不了。不知道是SDK问题还是mac问题，麦克风权限我总是无法正确授权。

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@Coresi7 commented on GitHub (Jan 30, 2024):

@Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。 同时也有小伙伴反馈同样的问题。

我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly.

sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用

是，但是分辨率这个限制是苹果的限制，假如有朝一日我们开放了mac silicon平台，他也会是这样的。我们根据长宽比自动应用了ipad布局。

<!-- gh-comment-id:1916894630 --> @Coresi7 commented on GitHub (Jan 30, 2024): > > > @Coresi7 我使用了PlayCover2.0.5、3.0.0beta、3.0.0beta2、nightly542和nightly617这五个版本都尝试过，无一例外，全部报错。  同时也有小伙伴反馈同样的问题。 > > > > > > 我个人不再推荐使用playcover，建议尝试sideloadly I personally do not recommend using playcover anymore, now I recommend to run via sideloadly. > > sideloady装的都是ipad模式 装备备战席 用起来不习惯 另外 似乎麦克风的问题仍然不能使用 是，但是分辨率这个限制是苹果的限制，假如有朝一日我们开放了mac silicon平台，他也会是这样的。我们根据长宽比自动应用了ipad布局。

kerem commented 2026-03-03 19:00:27 +03:00

Author

Owner

Copy link

@F1ySyn commented on GitHub (Feb 1, 2024):

I believe what you have done for jkchess here is meaningful, as it indeed makes our experience on Mac much better.

However, I think since you plan to support keyboard operations for the game on Mac, it would be equally nice to bring official keyboard support to the iPad Pro with the Magic Keyboard, as the experience there is far more perfect.

At the same time, I wonder if it's possible to modify the frame rate limit by manually editing some files, because I actually use an M3 Max paired with a 240Hz screen (I need to clarify, this is not a mandatory requirement, just out of my personal curiosity).

I noticed in the boot.config file there is 'hdr-display-enabled=0' (but I have never seen this option in iOS and iPadOS, are you still testing the possibility of HDR?), and I also noticed in gameConfig there are some setting parameters: m_DisplayMode = 5, m_FramePerSecondSetting = 4, m_HighFrameRate = 0, m_HighResolution = 0, m_HDRBloom = 1, m_SSAO = 1, m_ColorGrading = 1, m_ContrastEnhance = 1, m_SoftLight = 1.

I also want to know if modifying these contents is safe, although it does not involve any game fairness.

In addition, I think Playcover is still meaningful, as sideloadly cannot modify resolution, and my experience under a 49-inch ultrawide screen is very poor. I know you might never bring official support to Mac, but honestly, I'm happy to see you striving for all this.

<!-- gh-comment-id:1922188078 --> @F1ySyn commented on GitHub (Feb 1, 2024): I believe what you have done for jkchess here is meaningful, as it indeed makes our experience on Mac much better. However, I think since you plan to support keyboard operations for the game on Mac, it would be equally nice to bring official keyboard support to the iPad Pro with the Magic Keyboard, as the experience there is far more perfect. At the same time, I wonder if it's possible to modify the frame rate limit by manually editing some files, because I actually use an M3 Max paired with a 240Hz screen (I need to clarify, this is not a mandatory requirement, just out of my personal curiosity). I noticed in the boot.config file there is 'hdr-display-enabled=0' (but I have never seen this option in iOS and iPadOS, are you still testing the possibility of HDR?), and I also noticed in gameConfig there are some setting parameters: m_DisplayMode = 5, m_FramePerSecondSetting = 4, m_HighFrameRate = 0, m_HighResolution = 0, m_HDRBloom = 1, m_SSAO = 1, m_ColorGrading = 1, m_ContrastEnhance = 1, m_SoftLight = 1. I also want to know if modifying these contents is safe, although it does not involve any game fairness. In addition, I think Playcover is still meaningful, as sideloadly cannot modify resolution, and my experience under a 49-inch ultrawide screen is very poor. I know you might never bring official support to Mac, but honestly, I'm happy to see you striving for all this.

kerem referenced this issue 2026-03-03 19:08:34 +03:00

[PR #716] [CLOSED] Updated README #1722

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

swift-6-migration

update

stable

test-build-sparkle-pr

test-xcode-less-installer

stage-xclt

preview-test-fancy-library

3.1.0

3.0.0

3.0.0-beta.2

3.0.0-beta.1

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

2.0.0-beta.1

2.0.0-alpha.2

2.0.0-alpha.1

1.1.1

1.1.0

1.0.7

1.0.6

1.0.4

1.0.1

1.0.0

0.9.9

0.9.8

0.9.7

0.9.5

0.9.6

0.8.9

0.9.1

0.9.2

0.8.7

0.7.5

0.7.6

0.7.7

0.7.8

0.8.4

0.8.1

0.7.3

0.7.9

0.6.0

0.6.1

0.6.2

0.5.0

0.4.0

0.1.1

0.1.0-fix

0.1.0-beta

0.0.2-alpha

Labels

Clear labels   

UI

  

app-support

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

game-support

  

good first issue

  

help wanted / caution

  

inactive

  

invalid

  

macos-beta

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

wontfix

No labels

UI

app-support

bug

bug

documentation

duplicate

enhancement

game-support

good first issue

help wanted / caution

inactive

invalid

macos-beta

pull-request

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#716

No description provided.