Add TECH Patching an App to Make it Debuggable

[cpholguera]

title: Patching an App to Make it Debuggable

By default, app available on the Apple App Store are not debuggable. In order to debug an iOS application, it must have the get-task-allow entitlement enabled. This entitlement allows other processes (like a debugger) to attach to the app. Xcode doesn't add the get-task-allow entitlement in a distribution provisioning profile; it is only whitelisted and added in a development provisioning profile.

Please avoid repeating content as much as possible. As you can see in our techniques page we make our techniques very modular and narrow in scope so they can be easily reused across the guide.

Consider:

• MASTG-TECH-0054: Obtaining and Extracting Apps
• MASTG-TECH-xxxx: Patching -> This would be your new technique
• MASTG-TECH-0092: Signing IPA files
  
• MASTG-TECH-0055: Launching a Repackaged App in Debug Mode
  
• MASTG-TECH-0084: Debugging
  

So I think this works well. You can write this new technique following a similar approach as in MASTG-TECH-0038: Patching (Android) where one of the sub-sections can be ## Patching Example: Making an App Debuggable.

Before submitting for review please validate that all the steps above work and you're able to debug the app as indicated in MASTG-TECH-0084: Debugging.

[shwetd19]

Hey @cpholguera I'm thinking of this fix, can I work on it ?

1. we need to extract the IPA file and unzip it to access the app bundle.
2. Then, we can use a tool like codesign or optool to modify the entitlements plist by adding <key>get-task-allow</key><true/>.
3. After that, re-signing the app with a development provisioning profile using the command: codesign -f -s "iPhone Developer: [Your Name]" --entitlements entitlements.plist [AppName].app.
4. Finally, repackage the app and install the patched IPA using Xcode or a tool like ios-deploy.

This process allows a debugger to attach to the app, bypassing App Store restrictions.

[cpholguera]

It's assigned to you now @shwetd19.

Please avoid repeating content as much as possible. As you can see in our techniques page we make our techniques very modular and narrow in scope so they can be easily reused across the guide.

Consider:

• MASTG-TECH-0054: Obtaining and Extracting Apps
• MASTG-TECH-xxxx: Patching -> This would be your new technique
• MASTG-TECH-0092: Signing IPA files
  
• MASTG-TECH-0055: Launching a Repackaged App in Debug Mode
  
• MASTG-TECH-0084: Debugging
  

So I think this works well. You can write this new technique following a similar approach as in MASTG-TECH-0038: Patching (Android) where one of the sub-sections can be ## Patching Example: Making an App Debuggable.

Before submitting for review please validate that all the steps above work and you're able to debug the app as indicated in MASTG-TECH-0084: Debugging.

Please post here any proof (screenshots, etc.) and phone / OS versions and if it's jailbroken or not.

Thanks a lot!