testflight

I create a new App Store Distribution profile containing the beta entitlement to distribute builds via TestFlight, I create my application based on new profile that was contain beta entitlement, when I submit my application I got this error: Generate a new App Store Distribution profile containing the beta entitlement to distribute builds via TestFlight Here is my provision profile: <key>Entitlements</key> <dict> <key>keychain-access-groups</key> <array> <string>XXXXXXX.*</string> </array> <key>get-task-allow</key> <false/> <key>application-identifier</key> <string>XXXXXXX.my.companyname.test<

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

I've followed the instructions from TestFlight to duplicate the "release" configuration. Also I'm using TestFlight SDK to get live reports from my app. By doing this I had to include some TestFlight code in my application. Of course I don't want to have this code in my release version of my app. Is there some way to only include this code in the testflight configuration (the duplicated release configuration)? The same way you can do with #ifdef DEBUG for the debug configuration (or do I have to create a separate target for this and only include the TestFlight SDK in that target?) You can

I am part of a development team with many apps spanning multiple business units and iOS teams. We are having a lot of trouble right now managing distribution certificates. Apple lets you have 3 distrution certificates on one development account, but there is no way to name the certificates uniquely, so they all look the same. The only identifying information on the different certificates is the date on which it was generated. Apple, why can't we rename these distribution certificates so that we can manage them better??? We need the ability to allow multiple build boxes to archive and

My app is currently a paid app. I would like to convert the app to a free app with IAP and grandfather (give all users who paid for the app) the IAP features for free. I thought I could use receipt validation to either (1) determine original purchase date of app - but this seems to be only available for IAP or (2) Use original Application Version (which appears to be the build version not the app version). However, when I test this in testflight, the original version number is always '1.0'. Various sources say this is a testflight issue and that the release app would correctly identify the

My application update has been rejected. Into the rejection message, they wrote "Application crashes at launch". I then tried my application but couldn't make it crash. So I used TestFlight and noticed that when I was launched my app from TestFlight or AppStore, it was crashing at launch. But if I launch my app normally, it does work without any crashes. The thing is this bug occurred since iOS 10 update. Now my application on store also crashes when launched from AppStore while it was working fine 2 weeks go. Apple sent me a crash log: Incident Identifier: 001969F1-F275-4AC3-AFE1-E0426957B702

After uploading the app via adHoc deployment I see this message on the iTunesConnect. "TestFlight doesn’t support apps with Watchkit extension" Does anyone have a idea why this is shown and what is the solution? Looks like Apple TestFlight is not yet ready for WatchKit apps. You can temporarily disable WatchKit extension inclusion by deleting this row from main iOS app General Settings: The only way is via old school Ad Hoc or enterprise signing (and HockeyApp) There is currently no solution, WatchKit apps cannot be distributed over TestFlight yet. I would estimate it will be enabled sometime