Monday, December 12, 2022
HomeAppleios - Putting in an iphone app on an m1 mac

ios – Putting in an iphone app on an m1 mac

I am seeking to set up a specific app on my mac the usage of playcover,

The app is going thru applicationDidFinishLaunching and applicationDidBecomeActive however in an instant crashes because of a segfault,

I used to be ready to get round this by means of manually putting in the ipa each week the usage of sideloadly and a loose developer account however its getting truly tedious

How does sideloadly set up the app for private checking out functions?

The app put in with sideloadly has the construct model because the freshly unzipped ipa
Load command 9 cmd LC_VERSION_MIN_IPHONEOS cmdsize 16 model 9.0 sdk 15.2

while PlayCover adjustments it to maccatalyst
Load command 66 cmd LC_BUILD_VERSION cmdsize 24 platform MACCATALYST minos 11.0 sdk 14.0 ntools 0

That is what PlayCover recently makes use of to put in an app:

  1. unzip the app
  2. save its entitlements to a folder
  3. get a listing of all machos
  4. patch the app executable with the playtools executable (for keymapping)
  5. signal the app "/usr/bin/codesign -fs- (executable trail) --deep --preserve-metadata=entitlements"
  6. for each macho from the checklist:
    1. substitute @/rpath/libswiftUIKit.dylib with
      /Machine/iOSSupport/usr/lib/swift/libswiftUIKit.dylib the usage of install_name_tool
    2. set the platform to maccatalyst, minos to 11.0, and sdk to fourteen.0 the usage of vtool
    3. signal the macho the usage of "/usr/bin/codesign -fs- (trail)"
  7. set 0o755 permission at the document
  8. delete embedded.mobileprovision
  9. set MinimumOSVersion of information.plist to no less than 11 // the damaged app at first has a model of 13
  10. signal the app with entitlements "/usr/bin/codesign -fs- (executable trail) --deep --entitlements (entitlements trail)")

with default entitlements {

"": true,
"": true,
"": true,
"": true,
"": true,
"": true,
" camera": true,
"": true,
"": true,
"": true,
"": true,
"": true,
"": true,
"": true,
"": true,
"": true,
"": ["(allow user-preference-write (preference-domain ".GlobalPreferences"))", "(allow user-preference-read (preference-domain ".GlobalPreferences"))", "(allow file* file-read* file-write* file-write-data file-read-metadata file-ioctl (literal "/Users/user/Library/Preferences/playcover.plist"))", "(allow file* file-read* file-read-metadata file-ioctl (subpath "/Users/user/Library/Frameworks/PlayTools.framework"))"]


I’ve attempted skipping step 4 to peer if it’s the one breaking the app, and

Atmosphere permission 755 and codesigning the executable, then transferring it to the wrapper folder within a legitimate ios app put in at the mac

However each failed.

Additionally, for private use is ad-hoc signing the similar as signing with a certificates?


Most Popular

Recent Comments