TestFlight experience

Targets iOS
1

If you are interested, two issues occurred when trying to set up an app via Testfight.
Apart from all the business and contact details, privacy policy etc (which seem over the top for testers)

After uploading, Apple emailed to say it was ‘good to go’
But it still couldnt be downloaded by testers: ‘no builds available’
Testers were seeing a message to say ‘Missing Compliance’
This proves to be a question about ‘does the app use encryption’, so I had to go to App Connect , select the app, ‘amend’ and confirm it didnt use encryption.

After that , a yellow triangle ’ Complete test information is required to submit a build for external testing’

All the fields required were completed, including pointless ones such as licence information and testing information.

The fix for this one was to add a non-existent user name and password , and tick the ‘SignIn required’ box
Then remove the user name and password, and untick the ‘SignIn Required’ box
Then save.

Just in case this helps anyone else.

4 Likes
2

What was the fix for this?

3

In that particular case, it was the sign in box (see above). Where are you getting stuck?

4

I use Appwrapper to notarise and upload. I check first and get all green ticks. It uploads and they accept it but they send this message
" We noticed one or more issues with a recent delivery for the following app:

  • AppName
  • Version 7.3.1
  • Build 7.3.1

Although delivery was successful, you may want to correct the following issues in your next delivery. Once you’ve corrected the issues, upload a new binary to App Store Connect.

ITMS-90886: ‘Cannot be used with TestFlight because the signature for the bundle at “Crossword Wizard Player.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.’"

5

Ok.
I havent encountered that one before, but picking it apart:

When you created a provisioning profile at the Developer site, what did the app identifier look like?
com.yoursite.appname or com.yoursite.* (wildcard?)

In the IDE, what does the app ID look like?

Anything unusual, like maybe several periods or spaces in the ID?

6

Never use wildcards and same specific in the app

Is TestFlight only for IOS? Maybe I added a user in a MacOS App and it is complaining about that?

7

I’ve only ever used it for iOS myself -
(my MacOS apps want to do more than the App Store limitations allow - my testers get a downloadble dmg from me direct)
but I’m pretty sure it’s OK for both.

But step by step, does your IDE have a Bundle Identfier set up against MacOs?
image

image

8

Exactly the same.
It’s not stopping me from doing updates and you are correct I can get testers to download direct, was just curious about the error.
Just put it in the mystery basket :slight_smile:

9

FWIW, there’s a plist entry that you can make to indicate compliance so you don’t have to to that every time.

10

Like Martin, my apps get accepted but I get the same warning “” We noticed one or more issues with a recent delivery etc. etc,"

Although the provProfile I add in AppWrapper is not a Development but a Distribution profile, nevertheless the app identifier looks like this:

com.apple.application-identifier
E6KX394XXX.com.yoursite.appname

where E6KX394XXX is my Deverloper ID Application code in KeyChain (the one used by AppWrapper for signing the app).

In future, when I create a Development Provisional Profile, will it be OK if that too contains the “E6KX394B95” part?