iOS Build fails: Framework signing error, missing SwiftSupport, unsupported SDK (Ad-Hoc & App Store)

App Inventor for iOS
1

The Android version of the app has been in production for some time without issues.

The iOS version also works correctly using AI Companion.

Before generating the build, I completed the following steps:

· Registered as an Apple Developer

· Downloaded the Certificate Signing Request from MIT App Invento r

· Created an iOS Distribution Certifica te

· Created an Ad-Hoc Provisioning Prof ile

· Associated with the correct Ap p ID

· Added the target d evice

· Verified that both certificate and profile are active and valid unti l 2027

Screenshots confirm:

· The iOS Distribution certificate is valid

· The Ad-Hoc Provisioning Profile is valid

· The App ID matches the project

· The device is correctly registered

A. App Inventor Compiler Error

The compiler fails with:

ERROR: Failed to sign framework: PSRedisClient.framewor k

This indicates that App Inventor is not signing internal frameworks, which prevents the creation of a valid .ip a.

B. Apple Transporter Rejects the Build

· When a .ipa is produced, Transporter reports:

· ERROR ITMS-90426: Missing SwiftSupport f older

· ERROR ITMS-90167: Unsupport ed SDK

· ERROR ITMS-90161: Invalid Provisioning Profile

· Internal frameworks appear unsigned

C. Ad-Hoc Installation Fails

Even with:

· A valid certificate

· A valid Ad -Hoc profile

· A registered device

· Apple Configurator 2

The .ipa cannot be installed.

The MIT App Inventor compiler shows:

“ERROR: Failed to sign framework”

PSRedisClient.framewor k

image
image879×1401 175 KB

2

This looks like a build pipeline issue rather than a configuration problem.

The error Failed to sign framework: PSRedisClient.framework indicates that embedded frameworks are not being properly code signed during the packaging step.

This also explains the downstream errors:

  • Missing SwiftSupport folder
  • Unsupported SDK
  • Invalid IPA for Ad-Hoc/App Store distribution

Since the certificate, provisioning profile, and App ID are all valid, the failure is likely happening in the App Inventor iOS build process (specifically during framework signing and export).

This would need to be fixed in the buildserver (e.g., ensuring embedded frameworks are signed correctly and SwiftSupport is included during export).

3

I don't quite understand your post. If the system is failing to sign the frameworks, it will not return an IPA file nor upload to App Store Connect. The build pipeline is designed that if a step fails nothing else follows. Yet, you claim to both receive a signing error (earlier in the process) and that you also have the Ad Hoc or Transport errors?

1 Like
4

The same problem is happening with me

I used an old mobileprovision to build an IPA, which transporter wont accept since it isnt signed. Using a newer mobileprovision will always fail just like in the example here.

5

Where did you try to build the IPA — on the main, code2, or test server?

6

ai2a

7

Have also tried code2

8
9

I have never uploaded to apple connect before

10

There is no keystore file to download

11

From which builder and which AI2 account (you should only have one) did you download the "Certificate Request"

  • main server,
  • code2 server,
  • iOS test server?

image
image288×370 6.67 KB

The (your) keystore is created automatically after you build the first app (APK, AAB or IPA—Ad Hoc).

I can´t upload my APP to ios