Debugging on device error

BiehaoZhang's Avatar


22 Dec, 2016 08:26 AM

error: failed to load Reveal Server because it was not found in the application bundle. For information about debugging apps with Reveal on device, please refer to the Integration Guide.

  1. Support Staff 1 Posted by Vlas Voloshin on 22 Dec, 2016 08:34 AM

    Vlas Voloshin's Avatar


    This error is displayed when a reveal load debugger command is executed while running the app on device without Reveal Server in its bundle. As you have probably followed the integration guide for loading Reveal Server using a breakpoint, you probably have a UIApplicationMain breakpoint with reveal load command in it. If you would like to use Reveal while debugging on device, please make sure you follow the steps in the "Debugging on device" section of that document. Otherwise, you can either safely ignore that error message, or simply disable the UIApplicationMain breakpoint in Xcode while debugging on device.

    Best regards,

  2. 2 Posted by 664630287 on 22 Dec, 2016 09:35 AM

    664630287's Avatar

    I have follow the steps in the "Debugging on device" section of that document, but it doesn't work. So I want to do with pod, but the Reveal-SDK is old version.

    ------------------ 原始邮件 ------------------
    发件人: "Vlas Voloshin";<[email blocked]>;
    发送时间: 2016年12月22日(星期四) 下午4:34
    收件人: "664630287"<[email blocked]>;

    主题: Re: Debugging on device error [Support #59845]

  3. Support Staff 3 Posted by Vlas Voloshin on 28 Dec, 2016 11:05 AM

    Vlas Voloshin's Avatar

    Hi again!

    If you have correctly followed the instructions in the "Debugging on device" section, your project should have a Reveal Server integration build phase. That build phase is supposed to automatically detect where you have installed Reveal, but that might sometimes fail if you have more than one Reveal 2+ application bundle somewhere on disk, or potentially if Spotlight is disabled on your computer. Also please note that this method is only designed to work in Debug configurations.

    To check if the build phase encountered any issues, please try building your project in Xcode (still with Reveal integration build phase), and when that's finished, use View → Navigators → Show Report Navigator menu, select the most recent Build report, and there filter by "Reveal" to find "Run custom shell script 'Integrate Reveal'" section and its output. If the build phase succeeded, you should see a "RevealServer.framework is included in this build..." message.

    If you see a "Reveal Server not loaded: Cannot find a compatible Reveal app." message, you can try specifying path to Reveal in the build script manually. For example, if you have Reveal installed in /Applications/, you can replace this line in the Reveal integration build phase script:

    REVEAL_APP_PATH=$(mdfind kMDItemCFBundleIdentifier="com.ittybittyapps.Reveal2" | head -n 1)

    with this line:


    As a result, the script will use this exact path instead of locating Reveal automatically.

    However, if you'd like to integrate Reveal using CocoaPods instead, the issue you're having with that is simply due to your pods repository being out of date. As noted in this integration guide, simply execute the following Terminal command in your project directory: pod update Reveal-SDK. After that completes, try building and running your project again. Note that to avoid two integration methods from colliding, I'd recommend removing Reveal integration script from your project build phases if you decide to settle with CocoaPods.

    Best regards,

  4. 4 Posted by 4faramita on 21 Nov, 2018 08:46 AM

    4faramita's Avatar

    For anyone who is bothered by this: “/Applications/” checks if your build configuration's NAME is "Debug", so if you have a different name, maybe change line 3 of this file:
    if [ "${CONFIGURATION}" != "Debug" ]; then

    And this is so stupid…

  5. Support Staff 5 Posted by Tony Arnold on 22 Nov, 2018 10:10 PM

    Tony Arnold's Avatar

    We restrict loading of the RevealServer framework to the debug configuration to prevent accidental inclusion in release configuration builds.

    And this is so stupid…

    Would you like to elaborate? I'm more than happy to discuss alternative approaches to the problem if you have ideas.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac