TMS-90398: Invalid WatchKit Support for ipa built & submitted with XCode 14 rc1

Question

DominikPich OP

Created Sep ’22

Replies 5

Boosts 4

Views 3.5k

Participants 6

submission errror

Hi, I updated to xcode14 rc1 on weekend and builds of my ios app incl my watch companion app work well on phone & watch devices

But upon submission I get TMS-90398: Invalid WatchKit Support

TMS-90398: Invalid WatchKit Support - The bundle contains an invalid implementation of WatchKit. The app may have been built or signed with non-compliant or pre-release tools. Visit developer.apple.com for more information.

right xcode?

Now, I did verify that I use the right XCode by looking at the Contents of the Info.plist within the compiled/bundled up apps::

ios app:

DTXcodeBuild: 14A309
DTSDKBuild: 20A360

contained watch app & watch extension:

DTXcodeBuild: 14A309
DTSDKBuild: 20R362

bitcode?

I verified there is no bitcode as I read thats deprecated

I have no idea what to check at this point :(

Boost

Answer 1

Developer Tools Engineer OP

Apple

Sep ’22

Can you please file a report using Feedback Assistant, and attach a build log and (if possible) a copy of your Xcode project and any xcconfig files?

0

Answer 2

Developer Tools Engineer OP

Apple

Sep ’22

Please note that if you're manually copying the "WK" stub from the SDK via a custom .ipa assembly process, you'll need to manually remove the arm64e slice from that binary using the lipo tool. Otherwise, using the standard Xcode Archive action will do this for you automatically.

0

Answer 3

zbnzbn OP

Oct ’22

@DominikPich have you found a solution? We are facing the same issue with Xcode 14.0 (14A309). This is a pretty old project and watch App has been there for years. No problem with Xcode 13.

0

Answer 4

Batman04 OP

Oct ’22

TMS-90398: Invalid WatchKit Support - The bundle contains an invalid implementation of WatchKit. The app may have been built or signed with non-compliant or pre-release tools. Visit developer.apple.com for more information

when i trying upload to test flight XCode 14.0.1 ios 16.0.075 any update in this issue

0

Answer 5

zbnzbn OP

Oct ’22

I finally got this fixed and build was accepted by TestFlight. Turned out it's the VALID_ARCHS settings. If I remember correctly it was carried over from Xcode 11 to 12, that the VALID_ARCHS in Build Settings ended up under User_Defined. All I needed to do was to change this setting to $(ARCHS_STANDARD) in both WatchApp and Watch Extension.

Before the change I couldn't even build it onto Watch Simulator, showing the error in Xcode console: WatchKit 1 apps aren't supported on this version of watchOS. Quitting "(null)". This was fixed as well.

0