Persistent Xcode validation errors

Question

Created 4d

Replies 2

Boosts 0

Participants 2

We recently updated the codebase of our existing iOS application to improve compatibility with the latest versions of iOS. For several months, our attempts to deploy the updated application to TestFlight for testing and validation have consistently failed due to four recurring Xcode validation errors. Please see the attached document "X-Code Validation Errors.txt" for details on these errors.

<see: XCode Validation Errors (forum).txt>

Our application is developed using Visual Studio 2022 for PC with the .NET MAUI framework, as Microsoft no longer supports Visual Studio for Mac. After a successful build and testing using a virtual iPhone interface, Visual Studio connects remotely to the MacBook (Mac OS 15.1) sending the necessary project files that automatically triggers the Xcode (16.1) validation to begin.

We have made numerous edits to both the plist.info and the project file in an attempt to resolve the validation errors with little to no success. We are confident that is a configuration mismatch between what the plist says and the structure of the project itself.

We are hoping that someone here in the developer group has some answers for us. Our team is relatively new iOS development and have spent hours trying to resolve this issue. What are we doing wrong and what specifically do we need to change to correct these errors so that we can finally get this project into TestFlight?

I have attached copies of our plist.info, project structure, and error messages.

Please help

XCode Validation Errors (forum).txt

Info.plist

project..png

Boost

Answer 1

ssmith_c OP

4d

You're using a third-party tool and you're new to iOS development, so your way ahead is likely to be a little rocky.

I suggest you start by examining the built app bundle on the Mac, see if its plist, its resources and the error messages from Xcode are self-consistent. The Info.plist you posted here doesn't look like an Info.plist in an iOS app bundle - your file is plain text, Info.plist files are xml.

Then, on the Mac, in Xcode, build an iOS app from the template and try to send that to Test Flight. Understand the requirements for icons files and how they are fulfilled. Compare what is built by Xcode, the first-party tool, with what your tool is building.

0

Answer 2

mrwww76 OP

3d

I agree that the plist did not post to the forum as expected. I have attached screen shots of the plist in question.

When we view the plist contained in the IPA file generated by Xcode, we can see the key names, but the values are obfuscated in the file so we cannot verify.

plist 1 of 2.png

plist 2 of 2.png

0