Advanced ResourceRules Instructions

As you probably noticed from following through our SDK instructions, AppBlade uses it's own ResourceRules plist to do some magic on the backend. Sometimes projects already have a ResourceRules plist and – similar to the plot of immortal film Highlander — there can be only one.

Fortunately, this is where the similarity to Highlander ends, as we can resolve this conflict peacefully. It just takes a bit of manual editing.

###Add the AppBlade-related rules to your ResourceRules plist###

Open the existing resource rules plist of your project. Under the rules value set the ^AppBladeKeys.plist as Omitted with a weight of 100.

Your end result should look something like this

###Check that the new resource rules are set properly after building your project###

1. Build your ipa file in the usual way (just like how you'd build it for AppBlade)

2. Next you'll need to extract the IPA, change the ipa to a zip file (just rename it).

3. Double click to extract the ipa Payload folder.

4. Open your Payload folder and Right-click > Show Package Contents in your .app file

5. In your package contents, Locate your AppBladeKeys.plist file.

6. Open a terminal window, we use iTerm, and navigate to where you built your ipa.

7. Use codesign -dvvv in the terminal to confirm that the AppBladeKeys plist is properly included in the ipa

• Running codesign -dvvv extracted_path_to_your_payload_folder/Payload/ExampleApp.app/path_to_your/AppBladeKeys.plist
• The result should be something like 'Payload/ExampleApp.app/AppBladeKeys.plist: code object is not signed at all'