[GH-ISSUE #183] Encryption error message gets triggered by other issues? #79

Closed
opened 2026-03-03 18:54:20 +03:00 by kerem · 19 comments
Owner

Originally created by @brsotis on GitHub (Aug 18, 2022).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/183

A known good IPA was not opening. Updated PlayCover, and received a "move play cover to Applications" error.
Disabled SIP, removed the installed IPA, and went to reinstall after updating PlayCover.

Getting "This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!" on multiple, decrypted IPA's.

Originally created by @brsotis on GitHub (Aug 18, 2022). Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/183 A known good IPA was not opening. Updated PlayCover, and received a "move play cover to Applications" error. Disabled SIP, removed the installed IPA, and went to reinstall after updating PlayCover. Getting "This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!" on multiple, decrypted IPA's.
kerem 2026-03-03 18:54:20 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Candygoblen123 commented on GitHub (Aug 18, 2022):

What app are you trying to run? Specific examples would be best.

<!-- gh-comment-id:1220078081 --> @Candygoblen123 commented on GitHub (Aug 18, 2022): What app are you trying to run? Specific examples would be best.
Author
Owner

@Depal1 commented on GitHub (Aug 18, 2022):

Updated PlayCover, and received a "move play cover to Applications" error.

This first issue is literally for running PlayCover out of the Applications folder, perhaps you ran it from the installation disk. Move it to the Applications folder.

<!-- gh-comment-id:1220083473 --> @Depal1 commented on GitHub (Aug 18, 2022): > Updated PlayCover, and received a "move play cover to Applications" error. This first issue is literally for running PlayCover out of the Applications folder, perhaps you ran it from the installation disk. Move it to the Applications folder.
Author
Owner

@ZhichGaming commented on GitHub (Aug 18, 2022):

A known good IPA was not opening. Updated PlayCover, and received a "move play cover to Applications" error. Disabled SIP, removed the installed IPA, and went to reinstall after updating PlayCover.

Getting "This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!" on multiple, decrypted IPA's.

It seems that you are trying to run an encrypted IPA file. You need to use ipas that have been decrypted yourself or by someone else. You can find those here: https://ipa.playcover.workers.dev/0:/, here https://armconverter.com/decryptedappstore or here https://ipa.decrypt.day/.

<!-- gh-comment-id:1220085190 --> @ZhichGaming commented on GitHub (Aug 18, 2022): > A known good IPA was not opening. Updated PlayCover, and received a "move play cover to Applications" error. Disabled SIP, removed the installed IPA, and went to reinstall after updating PlayCover. > > Getting "This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!" on multiple, decrypted IPA's. It seems that you are trying to run an encrypted IPA file. You need to use ipas that have been decrypted yourself or by someone else. You can find those here: https://ipa.playcover.workers.dev/0:/, here https://armconverter.com/decryptedappstore or here https://ipa.decrypt.day/.
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

App was decrypted myself on a jailbroken iPhone. It runs directly out of the ~containers folder from a backup, but will not launch, or let me reinstall from Playcover.

Playcover is and was in the applications folder. Before this error, it said something about playtools and wouldn't launch.

<!-- gh-comment-id:1220098273 --> @brsotis commented on GitHub (Aug 19, 2022): App was decrypted myself on a jailbroken iPhone. It runs directly out of the ~containers folder from a backup, but will not launch, or let me reinstall from Playcover. Playcover is and was in the applications folder. Before this error, it said something about playtools and wouldn't launch.
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

Tried with the Netflix download as well, and get This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!"

<!-- gh-comment-id:1220098718 --> @brsotis commented on GitHub (Aug 19, 2022): Tried with the Netflix download as well, and get This app is encrypted! Please use a decrypted IPA from AppDb or download one from the internal store. iMazing IPA are not currently supported!"
Author
Owner

@Depal1 commented on GitHub (Aug 19, 2022):

I reckon this can be a legitimate issue as the original poster has just written. Perhaps the error message is too broad, and it isn't triggered because of encryption, or he is using 1.1.0 instead of 1.1.1.

@brsotis What PlayCover version are you using?

<!-- gh-comment-id:1220099562 --> @Depal1 commented on GitHub (Aug 19, 2022): I reckon this can be a legitimate issue as the original poster has just written. Perhaps the error message is too broad, and it isn't triggered because of encryption, or he is using 1.1.0 instead of 1.1.1. @brsotis What PlayCover version are you using?
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

Version 1.1.0 (17)

<!-- gh-comment-id:1220099833 --> @brsotis commented on GitHub (Aug 19, 2022): Version 1.1.0 (17)
Author
Owner

@Depal1 commented on GitHub (Aug 19, 2022):

Please use 1.1.1. There were issues related to yours that were fixed.

<!-- gh-comment-id:1220100071 --> @Depal1 commented on GitHub (Aug 19, 2022): Please use 1.1.1. There were issues related to yours that were fixed.
Author
Owner

@Depal1 commented on GitHub (Aug 19, 2022):

Keep me posted.

<!-- gh-comment-id:1220100292 --> @Depal1 commented on GitHub (Aug 19, 2022): Keep me posted.
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

Same error with the known good decrypted app (Azur Lane) that can still launch from containers from a backup.

Screen Shot 2022-08-18 at 8 20 21 PM

Will try netflix now

<!-- gh-comment-id:1220103469 --> @brsotis commented on GitHub (Aug 19, 2022): Same error with the known good decrypted app (Azur Lane) that can still launch from containers from a backup. <img width="895" alt="Screen Shot 2022-08-18 at 8 20 21 PM" src="https://user-images.githubusercontent.com/111543579/185516643-8bc02e0d-4ebd-46f0-8849-be81457c100a.png"> Will try netflix now
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

The above error is from Version 1.1.1 (36)

<!-- gh-comment-id:1220103703 --> @brsotis commented on GitHub (Aug 19, 2022): The above error is from Version 1.1.1 (36)
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

Screen Shot 2022-08-18 at 8 23 41 PM
<!-- gh-comment-id:1220104552 --> @brsotis commented on GitHub (Aug 19, 2022): <img width="895" alt="Screen Shot 2022-08-18 at 8 23 41 PM" src="https://user-images.githubusercontent.com/111543579/185516878-1855e537-2c72-41d8-9dd1-de28287f6374.png">
Author
Owner

@brsotis commented on GitHub (Aug 19, 2022):

Weirdly enough Netflix works after the above error is thrown. I can try re-cracking the app, but it took a long time originally

<!-- gh-comment-id:1220105081 --> @brsotis commented on GitHub (Aug 19, 2022): Weirdly enough Netflix works after the above error is thrown. I can try re-cracking the app, but it took a long time originally
Author
Owner

@Depal1 commented on GitHub (Aug 19, 2022):

Are you on Ventura by any chance?

<!-- gh-comment-id:1220106314 --> @Depal1 commented on GitHub (Aug 19, 2022): Are you on Ventura by any chance?
Author
Owner

@Depal1 commented on GitHub (Aug 19, 2022):

Nevermind, it was macOS 12.5.1.

<!-- gh-comment-id:1220106526 --> @Depal1 commented on GitHub (Aug 19, 2022): Nevermind, it was macOS 12.5.1.
Author
Owner

@ZhichGaming commented on GitHub (Aug 19, 2022):

You can try deleting the playcover apps folder and reinstalling your apps.

<!-- gh-comment-id:1220111562 --> @ZhichGaming commented on GitHub (Aug 19, 2022): You can try deleting the playcover apps folder and reinstalling your apps.
Author
Owner

@ohaiibuzzle commented on GitHub (Aug 20, 2022):

This error is thrown not only when an app main binary is encrypted but also when any Mach-O binaries after extraction is found encrypted. You may want to check if your dumper has properly decrypted everything including dylibs and such, as even if one of them stays encrypted (otool -l output has LC_ENCRYPTION_INFO and cryptid 1), installation will immediately be aborted.

<!-- gh-comment-id:1221266484 --> @ohaiibuzzle commented on GitHub (Aug 20, 2022): This error is thrown not only when an app main binary is encrypted but also when **any** Mach-O binaries after extraction is found encrypted. You may want to check if your dumper has properly decrypted everything including dylibs and such, as even if one of them stays encrypted (`otool -l` output has `LC_ENCRYPTION_INFO` and `cryptid 1`), installation will immediately be aborted.
Author
Owner

@yuchenxi2000 commented on GitHub (Aug 31, 2022):

Same error with the known good decrypted app (Azur Lane) that can still launch from containers from a backup.

Screen Shot 2022-08-18 at 8 20 21 PM

Will try netflix now

Was your Azur Line app downloaded from Playcover's decrypted IPA server? (https://ipa.playcover.workers.dev/) I downloaded the app in CN region, but I think it's the same case with the app in US region.

The main binary has two architectures, armv7 and arm64. The arm64 code is decrypted, while the armv7 code is not decrypted. M1 Macs will run the arm64 code, therefore this app should run in Playcover. However, Playcover think the binary is encrypted, because it runs otool command and only checks if the output contains "cryptid 1".

The fix is to ignore the cryptid under LC_ENCRYPTION_INFO load command, and only check the cryptid under LC_ENCRYPTION_INFO_64 load command. If you want to run the app before the fix, you can extract the arm64 code using lipo command, and make another IPA that doesn't contain any encrypted armv7 code.

<!-- gh-comment-id:1232558433 --> @yuchenxi2000 commented on GitHub (Aug 31, 2022): > Same error with the known good decrypted app (Azur Lane) that can still launch from containers from a backup. > > <img alt="Screen Shot 2022-08-18 at 8 20 21 PM" width="895" src="https://user-images.githubusercontent.com/111543579/185516643-8bc02e0d-4ebd-46f0-8849-be81457c100a.png"> > > Will try netflix now Was your Azur Line app downloaded from Playcover's decrypted IPA server? (https://ipa.playcover.workers.dev/) I downloaded the app in CN region, but I think it's the same case with the app in US region. The main binary has two architectures, armv7 and arm64. The arm64 code is decrypted, while the armv7 code is not decrypted. M1 Macs will run the arm64 code, therefore this app should run in Playcover. However, Playcover think the binary is encrypted, because it runs otool command and only checks if the output contains "cryptid 1". The fix is to ignore the cryptid under LC_ENCRYPTION_INFO load command, and only check the cryptid under LC_ENCRYPTION_INFO_64 load command. If you want to run the app before the fix, you can extract the arm64 code using lipo command, and make another IPA that doesn't contain any encrypted armv7 code.
Author
Owner

@Candygoblen123 commented on GitHub (Aug 31, 2022):

We could also add an install anyway button to the error popup, just as a manual bypass.

<!-- gh-comment-id:1232937212 --> @Candygoblen123 commented on GitHub (Aug 31, 2022): We could also add an install anyway button to the error popup, just as a manual bypass.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/PlayCover#79
No description provided.