ad-hoc-distribution

I'm developing an application that works perfectly well on my phone when I run it through Xcode. But when I distribute a beta through TestFlight, none of the users can run it - NOTE : They can install the app on their phones without any problem. The application just closes before it launches and there are no crash logs on TestFlight. I can connect any of my testers' phones to my computer and run the app on them (using Xcode) just fine. I thought maybe this is a problem with provisioning profiles, but on my phone, I can delete the relevant profile from Settings app then install the app from the

Having issues doing this. It will NOT let me select the provisioning profile to use, instead it defaults to some XC Ad Hoc: * and I cannot change it. The correct profile is selected in the build settings. I get: voratima I was experiencing the same issue in Xcode 6. I fixed it by: Go to Apple Developer > Create a new App ID specifically for the app with Explicit App ID like com.mywebsite.MyApp. Don't choose Wildcard App ID option. Go to Provisioning Profiles > Distribution > Update App ID (for MyApp) to the new one I just created. Generate a new profile. Download and install. It doesn't hurt

I have an iOS app that I've developing for a while. Initially there were around 8 devices in the iOS dev account, ad builds were prepared and distributed through Hockey App, no problems. Recently, we've added a bunch more devices, but for some reason the ad hoc builds won't install on those devices (but continues to install just fine on the original set). I have been over and over the certificates, devices and provisioning profiles in the iOS Dev Center. I've triple checked all the Build Settings in XCode. The app is for iOS 6 and iOS 7 only. It is built in XCode 5. I've tried installing the

We have an enterprise account and need to distribute the App with ad-hoc distribution. But with the ad-hoc distribution, the testers were still asked to trust enterprise developer and we cannot find the profile & device management in the Setting. Why does iOS ad-hoc distribution still need to trust enterprise developer? Is there anyone who encountered the similar issue? Once you installed application, 1: Go to setting -> General 2: Profile and Device Management 3: Click on "Untrusted app" 4: There is option for "trust" As described here: https://discussions.apple.com/thread/7611217 , the

I have an app that I am distributing using AdHoc - that works fine (using testflightapp.com) on most devices, however I have two older ones which run iOS 5.1.1 and iOS 4.3 respectively and on those I just can't get the app installed. The app has been built using XCode 5.1.1 and deployment target of iOS 4.3. The installation goes about 75% through (i.e. icon shows on home screen, progress indicator starts running up to about 75%), then an error message is shown: "Unable to Download Application" - ... could not be downloaded at this time. Checking the logs I found crash of /usr/libexec/installd

I did a ad Hoc Distribution of my App now i want to to Debug it again (i have changed something with CoreData) but i cant. If i press Debug unsing the Settings for Distribution the Default picture starts on the device but i get an error "Error form Debuger: The programm being debugged is not being run.". If i use the Debug Settings i get an other Error: "The Executeable was signed with invalid entitlements." What do i have to do to be able to Debug again? You need to change the "Code Signing Identity" setting for your app target in XCode back to "iPhone Development", with the relevant

I think there's an issue with my app's .entitlements file when a .ipa is created and so I want to check the Bundle ID of the entitlements file. There's a fairly complicated build script I am using to change some stuff in there before building so I want to see what the final product is. I know that there used to be an Entitlements.plist that I could get off of the ipa but it doesn't seem to be there any longer. Is there any way to access the .entitlements file now? Sure, unzip the .ipa file which will create a Payload directory. Inside of the Payload directory is the application package. Right