Internal builds are not being tagged as 'internal' on TestFlight

Question

BrunoRigoWerminghoff OP

Created Jul ’24

Replies 3

Boosts 2

Participants 4

Hi,

Do we have any known issue with internal builds not being tagged properly as internal on TestFlight? Is anyone else having the same issue?

Our team is not being able to do internal builds anymore since the last week or so. The last build we have that was successfully tagged as internal was on Wed Jul 3 00:15:40.

After that mark, we can upload the builds and they show up on TestFlight, but they are not marked as internal and they can technically be used for a public release even though they shouldn't.

We thought this could be an issue with our CI workflow, as we did some changes around that time, but we tried reverting everything or building from an older commit and the problem isn't solved. We even tried building and uploading directly through Xcode, without going through our CI or any external tools, and even selecting the TestFlight Internal Only distribution method, the builds are still releasable (not internal).

On the CI side, we have confirmed multiple times that our ExportOptions.plist contains the expected key/value pair:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>destination</key>
	<string>export</string>
	<key>generateAppStoreInformation</key>
	<false/>
	<key>manageAppVersionAndBuildNumber</key>
	<true/>
	<key>method</key>
	<string>app-store-connect</string>
	<key>provisioningProfiles</key>
	<dict>
		<key>(redacted)</key>
		<string>(redacted)</string>
		<key>(redacted)</key>
		<string>(redacted)</string>
	</dict>
	<key>signingCertificate</key>
	<string>Apple Distribution</string>
	<key>signingStyle</key>
	<string>manual</string>
	<key>stripSwiftSymbols</key>
	<true/>
	<key>teamID</key>
	<string>(redacted)</string>
	<key>testFlightInternalTestingOnly</key>
	<true/>
	<key>uploadSymbols</key>
	<true/>
</dict>
</plist>

We're unsure on what else to do about it, but we definitely would prefer to have internal builds not being releasable to avoid human error.

Any ideas on what else we might be missing? Or if is this an actual TestFlight issue?

Thanks

Boost

Answer 1

Purple Monkey 42 OP

Jul ’24

Seeing the exact same thing as of about a few days ago. Our first mis-classified build was on 7/3 at 17:40 ET. I think the 'testFlightInternalTestingOnly' is no longer being honored properly.

0

Answer 2

Stainlesssteel OP

Jul ’24

Same here. Last build upload with the "internal" tag was Jun 12 for us. After that, the next upload was on Jul 9, and there the "internal" didnt show up anymore. This fits to your Jul 3 observations. We didnt change anything on our CI and older commits which used to work properly, are not working now. Neither Testflight's 'testFlightInternalTestingOnly', nor XCodes manual distribution with "Testflight internal only" set the "internal" tag in Testflight.

0

Answer 3

ChrisPugmire2 OP

Jul ’24

My unity builds are now all classified as 'internal'. I cannot find the build setting that is doing it. I definitely didn't turn it on intentionally. it seems odd this problem just occurred a few days after the opposite problem is reported.

0