3 Replies
      Latest reply on Jun 24, 2019 9:47 AM by alouane
      OneGM Level 1 Level 1 (0 points)

        Hello all,

         

        We have been hosting an enterprise application for our company for about 2 years now. Roughly 2 weeks ago, we got a report in that when trying to download the app it was returning a cannot connect to server error. I've been looking into this since then and have been turning up empty handed at every turn. Some info on the app:

        • The last build that we uploaded for distribution was back in October and everything worked correctly at that point.
        • The ipa, plist and png files are all publicly accessible on the server and can all be downloaded via safari when using a mac.
        • All of these are avaible via https connection as well.
        • The manifest url is as follows:<a href="itms-services://?action=download-manifest&url=<https><server_url>/<public_directory>/<plist_name>.plist" type="button">Download iOS App</a>
        • All of the details in the .plist file are correct as well.

         

        I also rebuilt the app in xcode, re-generated all of the provisioning profiles and certificates, signed and exported the ipa and plist files with different names to verify that it wasn't an issue with the build itself or a caching issue. I spent some time in the device logs as well to see what error the device was getting when it was throwing this error. That report is below:

         

        <Notice>: Could not load download manifest with underlying error: Error Domain=NSURLErrorDomain Code=-1005 "Cannot connect to <server_url>" UserInfo={NSUnderlyingError=0x103e655c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 "(null)" UserInfo={_kCFStreamErrorCodeKey=54, _kCFStreamErrorDomainKey=1}}, NSErrorFailingURLStringKey=<https><server_url>/<public_directory>/<plist_name>.plist, NSErrorFailingURLKey=<https><server_url>/<public_directory>/<plist_name>.plist, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=54, NSLocalizedDescription=Cannot connect to <server_url>}

         

        I've done a lot of different google searches on different aspects of that error code, but I can't find anything that quite matches the error that I'm getting.

         

        Any help or insights that could help with this issue would be greatly appreciated.

         

        Thanks.