Asset validation failed (90022)
Missing required icon file. The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file.
Asset validation failed (90713)
Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'com.....'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key
TestFlight
RSS for tagTestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.
Posts under TestFlight tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
I have been investigating a recent breakage where apps being installed via Testflight are crashing on launch with no helpful crash reports, or even console-accessible logging. More detail: The app launches just fine on iPadOS 18 beta (ipad) but the same build doesn't work on iPadOS 17.6.1
At my wit's end, I checked the entire build environment - was I using XCode beta still somewhere?
Well, in the XCode Cloud workflow, I had selected "Release" for the latest released version of XCode. And MUCH to my surprise, I see that XCode 16 RC is selected. Why? That's not released yet...
Anyway, this is just a friendly PSA to check your XCode Cloud workflows if you choose "release" when new XCode releases are upcoming... or peg your XCode Cloud environment versions.
And I still don't have an explanation why Testflight XCode 16 RC is producing builds that crash on iPadOS 17.6.1 (for us) but not the latest iPadOS 18 public beta...
I've submitted several requests for Family Controls Distribution access for all of my app targets over two weeks ago and have not gotten any response. The app I've been working on for over a year is finally ready to beta test to 200+ waitlisted users but this final roadblock is killing me! Anyone know what to do? Is there anyone else I could reach out to other than the apple request form to get help with this? Thank you!
I get the message as seen in the attached image. I recently enrolled in the Apple Developer program last month. Initially, I was working for a client and everything was working fine locally. Builds were executing fine and running as well in emulators and physical devices.
But when I archive the build and distribute it to TestFlight via AppStore Connect, I always get this error message as shown below. There are no warnings or errors in the console or in Xcode. I already took care of everything and all compliance related issues. I am not sure what even is wrong at this time.
I resubmitted the builds at-least 8 times but still getting same message.
Moreover, as a test run, I submitted a build containing a simple "Hello World" component as well. It's getting the same error. I have wrote to Apple Support as well but haven't heard back from them yet.
If anyone knows how to resolve this please please guide me. This is really annoying and frustrating now since testers are not able to test the application.
I have a Safari Extension deployed to test flight built and deployed using CLI tools in Azure Devops. It appears to be building, signing, and deploying properly. But when users try to install on TestFlight, they see an error saying something about an invalid provisioning profile. This seems to just be on the "installer" portion of the app. The extension shows up in safari settings and is otherwise useable. The users just aren't seeing the splash screen that instructs them to go to Safari Settings.
I'm not really sure what's wrong here. This is what my build pipeline looks like
- task: Bash@3
displayName: "Build export.plist file"
inputs:
targetType: 'inline'
script:
/usr/libexec/PlistBuddy -c "Add :method string mac-application" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :provisioningProfiles dict" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :provisioningProfiles:$(APP_IDENTIFIER) string $(InstallDistProvisioningProfile.provisioningProfileUuid)" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :signingCertificate string '$(InstallDistCerts.signingIdentity)'" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :signingStyle string manual" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :teamID string $(APPLE_TEAM_ID)" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :iCloudContainerEnvironment string Production" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :stripSwiftSymbols bool true" $(Pipeline.Workspace)/export.plist &&
/usr/libexec/PlistBuddy -c "Add :compileBitcode bool false" $(Pipeline.Workspace)/export.plist
- task: Xcode@5
displayName: "Build Safari Extension"
inputs:
action: "archive"
sdk: "macosx"
packageApp: true
xcodeVersion: "15"
args: "-verbose CODE_SIGNING_REQUIRED=Yes CODE_SIGNING_ALLOWED=Yes"
exportOptions: "plist"
exportOptionsPlist: '$(Pipeline.Workspace)/export.plist'
exportMethod: "mac-application"
archivePath: '$(Build.ArtifactStagingDirectory)/SafariDesktopExtension.xcarchive'
signingOption: "default"
- script: |
xcodebuild -exportArchive \
-archivePath $(Build.ArtifactStagingDirectory)/SafariDesktopExtension.xcarchive \
-exportPath $(Build.ArtifactStagingDirectory) \
-exportOptionsPlist $(Pipeline.Workspace)/export.plist
displayName: 'Export Distribution-signed App'
- task: DownloadSecureFile@1
displayName: "Download Provisioning Profile"
name: downloadProvisioningProfile
inputs:
secureFile: $(PROVISIONING_PROFILE_DIST)
- script: |
cp "$(downloadProvisioningProfile.secureFilePath)" "$(Build.ArtifactStagingDirectory)/SafariDesktopExtension.app/Contents/embedded.provisionprofile"
displayName: "Embed provisioning profile in Top-Level Executable"
- script: |
cp "$(downloadProvisioningProfile.secureFilePath)" "$(Build.ArtifactStagingDirectory)/SafariDesktopExtension.app/Contents/PlugIns/SafariDesktopExtension Extension.appex/Contents/embedded.provisionprofile"
displayName: "Embed provisioning profile in Extension"
- script: |
codesign --deep --force --verify --verbose --sign "$(InstallDistCerts.signingIdentity)" --entitlements "$(rootFolder)/safari/SafariDesktopExtension/SafariDesktopExtension/SafariDesktopExtension.entitlements" $(Build.ArtifactStagingDirectory)/SafariDesktopExtension.app
displayName: "Codesign"
- task: Bash@3
displayName: "Package Application"
inputs:
targetType: "inline"
script: |
productbuild --sign "$(InstallInstallerCert.signingIdentity)" --component "$(Build.ArtifactStagingDirectory)/SafariDesktopExtension.app" /Applications "$(Build.ArtifactStagingDirectory)/SafariDesktopExtension.pkg"
I'm sure there's a bit of garbage here as I'm new to developing in the apple ecosystem. But it appears to work and the resulting .pkg can be submitted successfully.
Effectively, that's building an archive using a plist for export options, exporting the archive for distribution, copying the distribution provisioning profile for the top-level executable (the one that's not working) and the extension itself, code signing, and packaging using the installer cert.
The provisioning profile (attached to a Mac distribution certificate) mentioned has the correct application identifier and matches the entitlements.
I'm not really sure what's going on here and the generic "invalid provisioning profile" error isn't helping. Any help would be appreciated. I'd also love to know if this could hold up a release.
When I install and open my React Native iOS app on my iPhone device using the TestFlight app, it shows an empty white screen. But, it works fine on my XCode Simulator and my iPhone device when run through XCode on both debug or release modes. What could be the reason for getting an empty white screen when running my app on TestFlight?
My Mac is on 15.1.
Xcode will not validate Mac apps — even for TestFlight.
I have been patient in not doing a full reset back to 14 and then back to 15.0, assuming this will go away soon.
Am I being naive?
Is there a chance validating apps on 15.1 is something that is months away and I need to do the annoying work of resetting my entire Mac back to 14->15?
Hi,
I created a leaderboard in my application, and a method to record a new score:
GKLeaderboard.loadLeaderboards(IDs: [leaderboardID]) { (leaderboards, error) in
if let error = error {
print("Error loading leaderboards: \(error.localizedDescription)")
}
guard let leaderboard = leaderboards?.first else {
print("Leaderboard not found")
return
}
leaderboard.submitScore(score, context: 0, player: self.localPlayer) { error in
if let error = error {
print("Error reporting score: \(error.localizedDescription)")
} else {
print("Score reported successfully!")
}
}
}
}
When debuging, this method is correctly called and I have a success, so I tried to test it with an internal TestFlight release.
The leaderboard is never updated.
Is there a way to perform a test of a leaderboard before publishing the app?
I have the same question for achievements:
let achievement = GKAchievement(identifier: identifier)
achievement.percentComplete = percentComplete
GKAchievement.report([achievement]) { error in
if let error = error {
print("Error reporting achievement: \(error.localizedDescription)")
}
}
}
Thanks!
The app I broke is out of stock, and I tried to send an EMail and call Apple but they did not support and asked me to send an EMail to the App Review department, until now it has been more than 6 days and I still have not received a response.
My account is a new download account, I attached Apple's policy, but when the error occurred, I did not receive any notification from Apple.
Anyone who has encountered this case, please guide me on how to contact and resolve it.
Sorry if I post too many articles with the same content.
From 1st Sept some of the user was on testflight Apps suddenly unable to open the application need to install app store version and reinstall the testflight again then able to use.
another issue is it will suddenly show beta expired even I check Appconnect the application is still show 50+ days to expire date
Hi everyone, on August 31st all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps were in compliance with Apple's policies. I then uploaded a new version and sent it to the review team but I received the following error "There was an error processing your request. Please try again later."
Hello everyone, on August 31st, all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps are in compliance with Apple's policies. I then uploaded a new version and sent it to the review team, but I received the following error "There was an error processing your request. Please try again later."
I have contacted Apple via Email and Phone but no one cares about my problem.
Has anyone had the same situation as me, I am really worried.
ERROR ITMS-90349: "Invalid Info.plist value. The value of the EXExtensionPointldentifier key, com.apple.contact.provider.extension, in the Info.plist of "MainApp.app/Extensions/ContactProviderExtension.appex" is invalid.
We were working on new iOS18 Contacts Provider extension and when try to test the feature in testflight we were unable to submit the build and getting the above error. The extensionPointldentifier 'com.apple.contact.provider.extension' was auto generated by xcode and apple doc mentioned the same value to use for Contacts Provider extension support. But it is not accepting in testflight.
https://developer.apple.com/documentation/contactprovider/contactproviderextension
Any help will be appreciated.
I have a beta tester signed up for TestFlight. They originally accepted the invite using both the wrong Apple ID and wrong device. We want to change the device and Apple ID they are using.
I had them open TestFlight on the wrong device, select our App and select "Stop Testing". I've also removed them from the test group.
I've then waited for 24 hrs and re-added them to the test group using the same email as before. Their status is "Invited".
However, they keep getting the error
Couldn't redeem TestFlight invitation code ""
This invitation has been revoked or is invalid. Request a new invitation from the developer.
I developed an app for visionOS in Xcode 16 (the beta one). The app's deployment target is set to visionOS 1.2 in Xcode, which is also displayed in the app metadata in App Store Connect. Both debug and release builds deployed to a couple of authorised devices work. However, a build deployed to TestFlight refused to install, saying that VisionOS 2.0 is required. When I hacked a build with Xcode 15, it worked. Does it mean I cannot build apps for visionOS versions before 2.0 with Xcode 16?
Aug 22, same issue. Just started happening a few hours ago. Was working fine this morning.
For the last hour or so, builds to TestFlight from our Xcode Cloud workflow are sitting in the "TestFlight Internal Testing - iOS" step with no log messages... Normally this step is pretty quick, but it's as if something is hanging there. This seems to affect multiple branches (we use GitHub).
Is something hosed on the TestFlight side/anyone else experiencing this?
Edit ah shortly after I posted this it finished :face-palm:. Perhaps this was related to the Xcode Cloud outage earlier
On App Store Connect, when a new TestFlight build is uploaded, it's no longer possible to add a group to the build. (FB14892147)
I've seen this error message for 2+ hours.
Other developers are reporting this issue: https://x.com/manuel_kehl/status/1826678066392793188
Apple's developer system status page doesn't report an outage: https://developer.apple.com/system-status/
Thank you for investigating this issue.
When installing the app in TestFlight app, I am receiving error "Device limit reach".
I am trying to delete the devices with Edit and delete button beside the device list but they come back. It is not getting deleted and I am not able to install the app for testing.
Any suggestion on how to proceed with this?
Missing App Icon (1024x1024) Error During App Store Submission
Hello everyone,
I'm encountering an issue when trying to distribute my iOS app using the Transporter tool. The submission process is blocked by an asset validation error stating:
Asset validation failed (90704): Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG in the asset catalog of apps built for iOS, iPadOS, or watchOS. Without this icon, apps can't be submitted for review.
I’ve tried several workarounds:
Added the ForegroundFile and Color properties to the MauiIcon.
Resized the image to 1024x1024 and included it in the bundle.
Verified the settings in my .csproj file and Info.plist.
Despite these efforts, the issue persists. Could anyone provide guidance on what to inspect within the contents of the generated IPA file or suggest any other solutions?
I've added the relevant project files and info.plist for reference.
Below is the .csproj file:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFrameworks>net8.0-android;net8.0-ios</TargetFrameworks>
<OutputType>Exe</OutputType>
<RootNamespace>Mobile</RootNamespace>
<UseMaui>true</UseMaui>
<SingleProject>true</SingleProject>
<ImplicitUsings>enable</ImplicitUsings>
<ApplicationTitle>iAMS Mobile</ApplicationTitle>
<ApplicationId>com.acsys.acsysmobilemaui</ApplicationId>
<ApplicationIdGuid>XXXXXX</ApplicationIdGuid>
<ApplicationDisplayVersion>1.1.1</ApplicationDisplayVersion>
<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">11.0</SupportedOSPlatformVersion>
<SupportedOSPlatformVersion Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'android'">24.0</SupportedOSPlatformVersion>
</PropertyGroup>
<PropertyGroup Condition="$(TargetFramework.Contains('-ios'))">
<ApplicationVersion>2.0.024.0812</ApplicationVersion>
</PropertyGroup>
<PropertyGroup Condition="$(TargetFramework.Contains('-ios')) and '$(Configuration)' == 'Release'">
<RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
<UseInterpreter>true</UseInterpreter> <!--Added by Sathish on Apr 30 2024: Resolved App random crash issue-->
<CodesignKey>Apple Distribution: Acsys Technologies Ltd. (24K9VYD2A5)</CodesignKey>
<CodesignProvision>AcsysMobileMAUIAppStore</CodesignProvision>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net8.0-ios|AnyCPU'">
<CreatePackage>false</CreatePackage>
<MtouchDebug>true</MtouchDebug>
<CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>
<BuildIpa>False</BuildIpa>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|net8.0-ios|AnyCPU'">
<CreatePackage>false</CreatePackage>
<CodesignKey>Apple Development: sathishkumar muthusamy (F66HZ6XBT7)</CodesignKey>
<CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>
<MtouchLink>None</MtouchLink>
<CodesignProvision>AcsysMobileMAUDevelopment</CodesignProvision>
<BuildIpa>False</BuildIpa>
</PropertyGroup>
<ItemGroup>
<!-- App Icon -->
<MauiIcon Include="Resources\AppIcon/appicon.png" ForegroundFile="Resources\AppIcon/appiconfg.svg" Color="#000000" BaseSize="128,128" Resize="false" />
<!-- Splash Screen -->
<MauiSplashScreen Include="Resources\Splash\splash.svg" Color="#ffffff" BaseSize="256,256" />
<!-- Images -->
<MauiImage Include="Resources\Images\*" />
<MauiFont Include="Resources\AppIcon\Fonts\*" />
</ItemGroup>
</Project>
Here's the content of the iOS Info.plist file:
<?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>LSRequiresIPhoneOS</key>
<true/>
<key>MinimumOSVersion</key>
<string>11.0</string>
<key>UIDeviceFamily</key>
<array>
<integer>1</integer>
</array>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>armv7</string>
</array>
<key>UIUserInterfaceStyle</key>
<string>Light</string>
<key>UIStatusBarStyle</key>
<string>UIStatusBarStyleDarkContent</string>
<key>UIViewControllerBasedStatusBarAppearance</key>
<true/>
<key>UISupportedInterfaceOrientations</key>
<array>
<string>UIInterfaceOrientationPortrait</string>
</array>
<key>XSAppIconAssets</key>
<string>Assets.xcassets/appicon.appiconset</string>
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
</dict>
<key>NSBluetoothAlwaysUsageDescription</key>
<string>Required to enable BLE functionalities</string>
<key>NSBluetoothPeripheralUsageDescription</key>
<string>Required to enable BLE functionalities</string>
<key>NSCameraUsageDescription</key>
<string>Required to access your camera for Open/Close image verification</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>This app needs access to the photo gallery for picking photos and videos.</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>Required to Access Photo Library</string>
<key>NSFaceIDUsageDescription</key>
<string>Acsys Mobile requires Face ID to unlock the app</string>
<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>Acsys Mobile requires GPS to get site location</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>Acsys Mobile requires GPS to get site location</string>
<key>UIBackgroundModes</key>
<array>
<string>fetch</string>
<string>remote-notification</string>
<string>audio</string>
</array>
<key>CFBundleIdentifier</key>
<string>com.acsys.acsysmobilemaui</string>
<key>CFBundleDisplayName</key>
<string>iAMS Mobile</string>
<key>LSApplicationQueriesSchemes</key>
<array>
<string>mailto</string>
</array>
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
<key>XIEnableUITracking</key>
<false/>
<key>NSMicrophoneUsageDescription</key>
<string>We need access to the microphone to play sound for notifications.</string>
<key>UIApplicationSupportsIndirectInputEvents</key>
<true/>
</dict>
</plist>
Thank you for your help!
Environment:
macOS Sonoma 14.5
Xcode 15.4
Visual Studio Code Version 1.92.2
.NET MAUI
Additional Information:
This issue has been blocking my app submission for several days, and any assistance would be greatly appreciated.