title: Different iOS Direct Update Dialog Buttons from same code from SVN with two different build processes (WL Studio / Jenkins Xcode)?
body: <p>We are seeing a strange behavior in our iOS part of the App:</p>
  
  <p>We are using a Jenkins Build Server with an XCode plugin to compile the app on the command line</p>
  
  <p>At first we had an SVN ignore on the iPhone "native" folder in our SVN. So all was taken from common and the whole native project was generated by the worklight Ant scripts on the Jenkins server. This was then compiled by the xcode on jenkins and the App worked fine with Direct Update - the Dialog had a "UPDATE" and a "EXIT" button, both buttons worked as intended.</p>
  
  <p>Then we added a CustomWebView to our project and had to include the native folder into the SVN. We tried to SVN.ignore all generated files and the build processes in Worklight Studio and on the Jenkins xcode server work both fine.
  We did not change any of the generated code except we added two classes:</p>
  
  <pre><code>WebViewOverlayPlugin.h
  WebViewOverlayPlugin.m
  </code></pre>
  
  <p>and added the plugin to the config.xml:</p>
  
  <pre><code>&lt;plugin name="WebViewOverlayPlugin" value="WebViewOverlayPlugin"/&gt;
  </code></pre>
  
  <p>BUT:</p>
  
  <ul>
  <li><p>when we compile the same SVN code in the Worklight Studio, we have an iPhone app that has a Direct Update dialog with only the "UPDATE" button across the whole dialog. There is no "EXIT" button anymore at all.</p></li>
  <li><p>when we compile the same SVN on the Jenkins Xcode server, we have an iPhone app that has a Direct Update dialog with an "UPDATE" and an "EXIT" button but the "EXIT" button does not work as intended  - when pressing it, the app stays open and the dialog closes, so the user can continue to use the old version of the app without updating. The "UPDATE" button works and updates the App.</p></li>
  </ul>
  
  <p>So my question is, what build setting, generated files or configuration etc. could have any influence on the behavior of the Direct Update dialog. Since we use the exact same SVN source it has to have something to do with something generated, or with some configuration.</p>
  
  <p>Is anything around such a strange behavior known?</p>
  
  <p>Is it known that one can "configure" the Direct Update dialog to have only an "UPDATE" button with no "EXIT"?</p>
  
  <p>Thank you all for any help or hint where we could look to further investigate. </p>