I tried to upload my App to iTunes Connect resp. AppStore and got the following error:

&gt; Failed to locate or generate matching signing assets
&gt;
&gt; Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues.

&gt; Missing iOS Distribution signing identity for ... 
      Xcode can request one for you.
&lt;/pre&gt;

Before I set up a new development machine, exported the developer accounts via Xcode 7 from the old to the new machine. 

What can I do to fix this?

Xcode 7 error: &quot;Missing iOS Distribution signing identity for ...&quot;

When I added my latest build for internal testing with Test Flight, I saw that it had a &quot;Missing Compliance&quot; status.

Is this a major problem? Why does this appear? How can I resolve this issue?

[![Test flight status Missing Compliance][1]][1]

  [1]: http://i.stack.imgur.com/XBXUa.png

Missing Compliance status in Test Flight

I used Xcode 6.1.1 to upload a new version of a prerelease app to iTunes Connect so I could distribute it to my external beta testers. I&#39;ve done this with two versions of the same app previously and it worked fine.

But this time, the upload was stuck in &quot;Processing&quot; state for over a week. I tried again (same version, new build number) and it&#39;s now been over 24 hours with no change.

The app passed validation fine.

What gives?

My prerelease app has been &quot;processing&quot; for over a week in iTunes Connect, what gives?

Is it possible to detect at runtime that an application has been installed through TestFlight Beta (submitted through iTunes Connect) vs the App Store? You can submit a single app bundle and have it available through both. Is there an API that can detect which way it was installed? Or does the receipt contain information that allows this to be determined?

How to tell at runtime whether an iOS app is running through a TestFlight Beta install

I set up my application for TestFlight. For external users it is waiting for review. But if I want to invite internal users, I select them and press invite. iTunes Connects says they are invited now, but none of the invited emails gets an invitation email.

Do you know what I am doing wrong?

No TestFlight invite email gets sent for internal users

I&#39;ve been using TestFlight for a while but this is the first time I&#39;m submitting a build for beta testing directly from iTunesConnect since Apple bought TestFlight itself.

I&#39;ve been experiencing a weird behaviour (or maybe just the Apple&#39;s expected behaviour).

I&#39;ve added the user to my team (they&#39;ve admin role), and I&#39;ve selected them as part of the TestFlight tester in the dedicated panel. I&#39;ve uploaded a build, switched the TestFlight Beta Testing on in the Build tab and selected the Internal Testers (just one in the screenshot below) I would like to receive that build.

Then...nothing happens, the state is still &quot;Processing&quot; (what?? shouldn&#39;t it be immediate?) the tester doesn&#39;t receive any invitation and I&#39;m stuck. There&#39;s obviously something I&#39;m missing here. 

Beside, even if one tester has already been invited, the panel still shows &quot;To start testing, invite at least one tester&quot;. TestFlight was such a good product once...

The two snapshot below show the state of my iTunesConnect panel. Any idea?

![Build tab][1]
![Internal tester tab][2]


  [1]: http://i.stack.imgur.com/fsbkz.png
  [2]: http://i.stack.imgur.com/65g2F.png

TestFight beta testing for internal testers - Build state is &quot;processing&quot;

Is there a way to re-send an invitation to an external tester on Apple&#39;s TestFlight Beta Testing service?

(I am referring to facility for external beta testing accessed via iTunes Connect, not to the standalone TestFlight service that has been provided since before Apple acquired it.)

Within iTunes Connect, under My Apps / Prerelease / External Testers, the tester&#39;s status just shows itself as &quot;Invited&quot;. Unfortunately, this tester had a hyperactive spam filter that simply deletes all spam, so he cannot access the original invitation. And I cannot find any control on the TestFlight UI to re-send it. I have tried turning testing off and on, but this doesn&#39;t seem to help.

How to re-send external tester invitations on Apple&#39;s TestFlight service

Today I started to receive this error with fastlane and Xcode:

&gt; ERROR ITMS-90783: &quot;Missing bundle display name. The Info.plist key
&gt; CFBundleDisplayName is missing or has an empty value in the bundle
&gt; with bundle identifier &#39;com.id&#39;.&quot;

It was ok and I didn&#39;t remove this property. I think this is a bug on Apple&#39;s side.

Does anyone have the same issue and how did you fix it?

Xcode ERROR ITMS-90783: &quot;Missing bundle display name&quot;

How do I upload my app I made in Xcode to iTunes Connect to invite Beta testers to download it?

I read the documentation and I tried what it said but it never uploaded my app.

How do I upload a build to iTunes Connect for TestFlight?

This was simply an update that didn&#39;t change anything to do with the rejection reason. Here is the response from the resolution center:


&gt; Reasons
&gt; Program License Agreement
&gt; PLA 3.3.12

&gt; We found your app uses the iOS Advertising Identifier but does not include ad functionality. This does not comply with the terms of the iOS Developer Program License Agreement, as required by the App Store Review Guidelines.

&gt; Specifically, section 3.3.12 of the iOS Developer Program License Agreement states:

&gt; &quot;You and Your Applications (and any third party with whom you have contracted to serve advertising) may use the Advertising Identifier, and any information obtained through the use of the Advertising Identifier, only for the purpose of serving advertising. If a user resets the Advertising Identifier, then You agree not to combine, correlate, link or otherwise associate, either directly or indirectly, the prior Advertising Identifier and any derived information with the reset Advertising Identifier.&quot;

&gt; Please check your code - including any third-party libraries - to remove any instances of:

&gt; class: **ASIdentifierManager**&lt;br&gt;
selector: **advertisingIdentifier**&lt;br&gt;
framework: **AdSupport.framework**

&gt; If you are planning to incorporate ads in a future version, please remove the Advertising Identifier from your app until you have included ad functionality.

&gt; To help locate the Advertising Identifier, use the “nm” tool. For information on the “nm” tool, open a terminal window and enter, “man nm.” 

&gt; If you do not have access to the libraries source, you may be able to search the compiled binary using the &quot;strings&quot; or &quot;otool&quot; command line tools. The &quot;strings&quot; tool lists the methods that the library calls, and &quot;otool -ov&quot; will list the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.


The third party libraries I&#39;m using is the latest version of `parse.com sdk, latest version of flurry analytics, and version 2.2 of test flight`. Does anybody know which library is the issue? Thanks

My app was just rejected for using the Ad support framework. Which library is responsible?

I have tested push notifications as a developer account and it worked, But when i tried to put it on TestFlight for the testers to test it, it didn&#39;t show a push notification but the data is correctly received, So is there a kind of certificate that i need to generate for TestFlight?

Why push notifications is not working on testflight?

Can anyone please explain in complete details the difference between internal and external testers in [iTunes Connect Testflight beta testing][1]? The difference here is just too brief. Does internal testers need to add UDID&#39;s of upto 10 devices? Or did apple completely removed UDID requirement now? 

Can someone please explain what needs to be done to distribute and test app of upto 1000 users? If I have the clients iTunes Connect credentials, how do I share the app from his own account? 

I know that there are too many questions asked in this thread which is against stackoverflow&#39;s policy, but i only need do&#39;s and don&#39;ts of internal and external testing of this awful itunes connect [testflight beta testing][2]. 


  [1]: https://developer.apple.com/testflight/
  [2]: https://developer.apple.com/library/prerelease/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html

Difference between internal and external testers in iTunes Testflight beta testing?

I&#39;m planning to release a beta version of my iPhone app on iOS 8 devices through the new Apple TestFlight app.
What kind of Certifcate and Provisioning Profile is needed for that? Do I need a *Production* certificate and *Distribution* provisioning profile?

Available are these:

    Certificate:
    - Pending
    - Development
    - Production

    Provisioning Profile:
    - Development
    - Distribution



What kind of Certifcate and Provisioning Profile is needed for an iOS Apple TestFlight release?

I implemented Dark Mode with the current beta version of Xcode in a relatively old&#160;app. I uploaded these to TestFlight for my&#160;testers. However, this crashes immediately for anyone who has the public beta of iOS&#160;13.

I&#39;ve integrated Crashlytics into the app, and the cause of these crashes is as&#160;follows:

&gt; `UISearchDisplayController` is no longer supported when using this version of&#160;iOS. Please migrate your application to&#160;`UISearchController`.

All `UISearchDisplayController` instances have already been replaced by the&#160;`UISearchController`. The app doesn&#39;t use the `UISearchDisplayController` anymore. There is no longer any links to the `UISearchDisplayController`. Nevertheless, these crashes continue to occur, but only from the installations of&#160;TestFlight.

If the app is installed directly with Xcode as a &quot;Debug&quot; or &quot;Release&quot; on an iPhone with the public beta, the crash does not&#160;occur.

Does anyone have a solution for this problem?

Installed App from TestFlight crashes due to alleged UISearchDisplayController

My app is in internal testing on iTunes Connect, but I cannot promote it to external testing. It tells me that the test information is incomplete. 

I have tried all sorts of things, including reading [this doc][1] and [this doc][2] on Apple and re-entering all the information again. Playing with the [language specifier][3].  

This is maddening, because this exact information worked for a previous build.

[![enter image description here][4]][4]


  [1]: https://help.apple.com/itunes-connect/developer/#/deva50a6ab41
  [2]: https://help.apple.com/itunes-connect/developer/#/devdc42b26b8
  [3]: https://webcache.googleusercontent.com/search?q=cache:kbEIQaCpGS0J:https://forums.developer.apple.com/thread/22799%20&amp;cd=3&amp;hl=en&amp;ct=clnk&amp;gl=ca
  [4]: https://i.stack.imgur.com/IuQxf.png

TestFlight: Complete test information is required to submit a build for external testing

I am having trouble adding an admin to one of my iOS builds.

When I click to my build, it shows I have 2 people who can test it:

[![iTunes Connect Users][1]][1]

But this is not what I&#39;m expecting.  I am expecting 3 people.  Because if I click to the ITunesConnect Users, I see 3 people.

[![Testers][2]][2]

But for some reason, my friend `Yu Yu` shows `No Builds Available`.  Why is this the case?  Under the Users and Roles, I can confirm that Yu Yu is an admin

[![No builds available][3]][3]

What am I doing wrong?  How do I allow `Yu Yu` to see my build `10 (23)` ?

  [1]: https://i.stack.imgur.com/SnbNA.jpg
  [2]: https://i.stack.imgur.com/UwqYN.jpg
  [3]: https://i.stack.imgur.com/Jh9cS.jpg

iTunesConnect Testflight no builds available for iOS?

i was trying to install my iphone application from testflight. it installs perfectly on few devices but in some after installing about 80 percent it gives an error &quot;Unable to download aaplication, &lt;my app&gt; could not be installed at this time&quot; i am able to find out the reason for , why is it so?
This is the screenshot:

![could not be installed at this time][1]

is there anybody who will help me regarding this issue?
Thanks in advance.


  [1]: http://i.stack.imgur.com/Cgze6.jpg

iPhone app could not be installed at this time

I am a registered iOS developer and a developer friend of mine is trying to send me a testflight version. 
For some reason he can&#39;t sent me an invitation - I believe this is because I am registered as a developer and used my only apple ID for the dev apple account registration.  
Nevertheless, I am currently beta testing another app... So something weird is going on... 
Furthermore, I notice there&#39;s a &quot;Redeem&quot; button at the bottom of the testflight app so there should be a place to invite other users using invitation codes. 

So how to send a testflight invitation code?
If this is not possible, how can I resolve this issue?


How to create a testflight invitation code?

I have published an app through the testflight website to allow my colleagues to test, and as more and more of them opens the initial email and find time to go through the registration process, testers are trickling in on my testflight team.

However, the process to add them to the test seems a bit convoluted, so I thought I&#39;d verify, and ask, if I&#39;m doing it right, or if I have missed something obvious.

At the moment the whole procedure looks like this:

1. A colleague opens up the initial email, with the invitation link
2. He/she then registers the device, and registers for the test
3. I am informed of this new tester through an email and through the testflight site
4. I then have to download (or write down/copy) the list of UDID&#39;s of all the new testers since last time
5. I then have to visit the devices part of the Apple Developers site, and upload that file
6. Edit my provisioning profile to include the new devices
7. Wait for it to approve, and download the provisioning profile
8. I drag the provisioning profile into the Xcode provisioning profile organizer
9. I then go back to MonoDevelop, and ensure it is still pointing to the right profile *(I don&#39;t know if using MonoDevelop/MonoTouch complicates this process so I didn&#39;t want to leave it out, it might be irrelevant for this question)*
10. I rebuild, and republish on testflight
11. I then visit the testflight website, find the new/updated build, and ensure all my testers are informed of it

I noticed that if I do not update the version, it will &quot;silently&quot; replace the existing build, and reuse the list of testers that have already been informed, so if I just check all the new testers and complete, it&#39;ll only inform the new ones.

However, it seems a bit of a work to have to keep downloading and mucking about with the provisioning profile files.

Did I miss something obvious? Is there a way for me to make any part of this easier?

For instance, I noticed that I can create a provisioning profile inside the Xcode organizer, however that dialog box doesn&#39;t list any certificates so I can&#39;t complete that dialog. If this is a key element, leave a short answer to that effect and I&#39;ll instead repost a new question about that.

*This* question is just: Is the above procedure correct?

Publishing to TestFlight, new testers, do I really need to rebuild/download my provisioning profile?

There are plenty iOS crash reporting libraries in iOS, including [TestFlight][1] and [HockeyApp][2]. If you don&#39;t want to depend on services, you can still use libraries like [PLCrashReporter][3]. Binding these libraries is [fairly trivial][4] because their public API usually consists of a couple of classes with several initialization methods.

However, when trying to use TestFlight, and later HockeyApp in our application, our app began to randomly crash. Turns out, this *is* a known issue [reported](https://bugzilla.xamarin.com/show_bug.cgi?id=4120) [several](http://monotouch.2284126.n4.nabble.com/Re-App-crashes-before-starting-td4657864.html) [times](https://stackoverflow.com/questions/7865374/problems-getting-testflight-to-work-with-monotouch-app/7867056#7867056), but Xamarin doesn&#39;t warn about it, it is relatively obscure and we found it the hard way.

We have learned that **all iOS crash reporters prevent Mono from catching null reference exceptions:**

    try {
        object o = null;
        o.GetHashCode ();
    } catch {
        // Catch block isn&#39;t called with crash reporting enabled.
        // Instead, the app will crash.
    }

Why does this happen? Quoting Rolf, a Xamarin developer,

&gt;A null reference exception is actually a SIGSEGV signal at first. Usually the
mono runtime handles this and translates it into a nullreference exception,
allowing the execution to continue. The problem is that SIGSEGV signals are a
very bad thing in ObjC apps (and when it occurs outside of managed code), so
any crash reporting solution will report it as a crash (and kill the app) -
this happens before MonoTouch gets a chance to handle the SIGSEGV, so there is
nothing MonoTouch can do about this.

I&#39;m sure many use TestFlight in MonoTouch apps without knowing it causes crashes.  
[Isn&#39;t it ironic?][5]  


**How do you make crash reporting libraries *not* crash MonoTouch apps?**


  [1]: https://testflightapp.com
  [2]: http://hockeyapp.net
  [3]: http://code.google.com/p/plcrashreporter/
  [4]: http://docs.xamarin.com/ios/Guides/Advanced_Topics/Binding_Objective-C_Libraries
  [5]: http://fgk.hanau.net/articles/ironic.html

All Testflight Solutions on Gang of Coders

Total of 20 Testflight Solutions

Xcode 7 error: "Missing iOS Distribution signing identity for ..."