Reset Search



[Video] Uploading dSYMs to Apteligent automatically

« Go Back


We've all forgotten something here and there. Uploading your dSYM to Apteligent shouldn't be one of them. By adding a build script that runs for each build you release, you'll never have to worry about tracking down your dSYMs again.

In most cases, using our server-side symbolication will be the most effective way to maintain the highest level of security (obfuscation) and reduced package size for your app. Here's what you need to set up in XCode:

- In your target's Build Settings, verify the following are set:

  • Strip Debug Symbols During Copy: Yes
  • Strip Linked Product: Yes
User-added image

- For every build you release to testers or users, you have to store the dSYM file and upload it to Apteligent. For why this is important check out our article about symbolication for iOS

Note: Apteligent Server-Side symbolication works for both Device and Simulator builds.

Uploading dSYM via XCode Build Script

The build script is now available inside the latest version of the iOS library (4.0.1 and higher).
After saving the file, make the script executable by running the command:

# chmod +x /PATH_TO_SCRIPT/

In order to configure Xcode to use the script each time you build your app, 

1. Select "Project" in XCode
2. Click on the appropriate "Target"
3. Select "Build Phases" tab:

User-added image
4. Go to Editor on Menu bar -> "Add Build Phase" -> select "Add Run Script Build Phase" (note: this step may already be completed if you've used a build script before):

User-added image

5. Login to your Apteligent Account -> Go to the App for which you want dSYM uploaded -> App Settings -> Upload dSYMs tab and copy the text under Upload via Build Script:

User-added image

and paste it under the textbox for "Run Script" under "Build Phases"

User-added image

Note for apps/project names with spaces:

If you have spaces in the name of the App/Project, then use double quotes around {SRCROOT} so that it can traverse the path correctly, like:
source "${SRCROOT}"/CrittercismSDK/

Alternatively you can also use the absolute path to the script location like (in this case, the path should be updated whenever the current location of the script changes ):
source "<Absolute Path to Project>/CrittercismSDK/"

You can also add optional parameters so that Run Script like:

6. Run & Build, your dSYM will upload to Apteligent.

Do you use Jenkins for your CI solution? There's a plugin available and you can find information about it here.

Watch the Video version:




Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255