TestFlight for Mac shows "Not Available for Testing"

We have discovered this can be caused by not including a Deployment provisioning profile in your submitted build, or if the build doesn't run at all it also produces a Not Available for testing result.

Apps will start in this state but should transition to available for testflighting after ~15 mins.

Thanks @brinkin. It's been multiple days and the app still shows as "Not Available for Testing".

Hi, did you manage to find out the reason of this status? I am dealing with the same issue and have only found "internalBuildState": "PROCESSING_EXCEPTION"  using AppStoreConnectAPI https://api.appstoreconnect.apple.com/v1/buildBetaDetails/{ID}

{

    "data": {

        "type": "buildBetaDetails",

        "id": "{ID}",

        "attributes": {

            "autoNotifyEnabled": true,

            "internalBuildState": "PROCESSING_EXCEPTION",

            "externalBuildState": "PROCESSING_EXCEPTION"

        },

        "relationships": {

            "build": {

                "links": {

                    "self": "https://api.appstoreconnect.apple.com/v1/buildBetaDetails/{ID}/relationships/build",

                    "related": "https://api.appstoreconnect.apple.com/v1/buildBetaDetails/{ID}/build"

                }

            }

        },

        "links": {

            "self": "https://api.appstoreconnect.apple.com/v1/buildBetaDetails/{ID}"

        }

    },

    "links": {

        "self": "https://api.appstoreconnect.apple.com/v1/buildBetaDetails/{ID}"

    }

}

Is there a way to get more details on that PROCESSING_EXCEPTION ?

I am facing exactly the same problem with a Qt macOS app. The app can be released to the store, works fine everywhere, but TestFlight is not available "Not Available for Testing".

The binary data is as follows:

Interestingly the "Build SDK" and "Build Platform" fields are empty.

Has anyone an idea/suggestion how to get TestFlight to work? Are there specific prerequisits necessary (for instance a minimum macOS version, specific signing, etc.)?

Interestingly the Build SDK and Build Platform fields are empty.

I don’t know if this is the cause of your TestFlight problem, but there’s two likely places that App Store Connect is looking for this info:

• Info.plist

• Mach-O load commands.

Consider the following commands run against an app I just built with Xcode:

% cat Test689377.app/Contents/Info.plist               
<?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>BuildMachineOSBuild</key>
    <string>20G224</string>
    …
    <key>CFBundleSupportedPlatforms</key>
    <array>
        <string>MacOSX</string>
    </array>
    …
    <key>DTCompiler</key>
    <string>com.apple.compilers.llvm.clang.1_0</string>
    <key>DTPlatformBuild</key>
    <string>13C90</string>
    <key>DTPlatformName</key>
    <string>macosx</string>
    <key>DTPlatformVersion</key>
    <string>12.1</string>
    <key>DTSDKBuild</key>
    <string>21C46</string>
    <key>DTSDKName</key>
    <string>macosx12.1</string>
    <key>DTXcode</key>
    <string>1320</string>
    <key>DTXcodeBuild</key>
    <string>13C90</string>
    <key>LSMinimumSystemVersion</key>
    <string>10.15</string>
    …
</dict>
</plist>
% vtool -show-build Test689377.app/Contents/MacOS/Test689377
Test689377.app/Contents/MacOS/Test689377:
Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform MACOS
    minos 10.15
      sdk 12.1
        …

I suspect it’s the latter that’s causing App Store Connect to not show the above-mentioned info.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Finally I got testflight working by adding the "com.apple.application-identifier" and "com.apple.developer.team-identifier" tags to the app.entitlements file. Now, TestFlight is enabled but the app crashes with a "Code signature invalid" crash.

@HMoc

I have added both the entitlements into the "entitlement.mac.plist" and "entitlement.mas.plist" but still I am getting the same status. Is there anything else we can do to process the build

I eventually got to the bottom of this. See TestFlight, Provisioning Profiles, and the Mac App Store.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"