Watchkit Error Uploading to App Store Invalid Icon
| title | description | ms.prod | ms.assetid | ms.technology | author | ms.author | ms.appointment | no-loc |
|---|---|---|---|---|---|---|---|---|
| Deploying watchOS Apps to the App Store | This document describes how to deploy watchOS apps built with Xamarin to the App Store. Information technology takes a wait at distribution provisioning profiles and iTunes Connect, and information technology also provides some troubleshooting tips. | xamarin | DBE16040-70D2-4F61-B5F3-C8D213DBC754 | xamarin-ios | davidortinau | daortin | 03/17/2017 | Objective-C |
Deploying watchOS Apps to the App Store
[!Important] Be sure to review Apple's Watch Kit Submission Guide, and run across the Troubleshooting section for whatsoever problems you may take.
-
Ensure you have:
- Distribution Provisioning Profiles created for your projects.
- The Deployment Target (
MinimumOSVersion) for the iOS parent app set to 8.2 or earlier (8.3 is not supported).
-
In iTunes Connect:
- Create your iOS app entry (or add together a New Version to an existing app).
- Add Watch icon and screenshots.
-
Then in Visual Studio for Mac (Visual Studio is not currently supported):
- Right-click the iOS app and choose Set Equally Startup Project.
- Modify to the App Store configuration.
- Employ the Archive feature create an application annal.
-
Finally, switch to Xcode 6.ii+
- Go to the Window > Organizer and cull Athenaeum.
- Select the awarding and annal from the list.
- (Optionally) Validate... the annal.
- Submit... the archive and follow the steps to upload to iTunes Connect for review and blessing.
Read specific tips related to these items below. See the Troubleshooting section if you have problems.
Distribution Provisioning Profiles
To build for App Store deployment y'all need to create a Distribution Provisioning Contour for each App ID in your solution.
If you have a wildcard App ID, but one Provisioning Profile will be required; but if yous have a divide App ID for each projection then you'll need a provisioning contour for each App ID:
Once you've created all three profiles, they'll appear in the list. Remember to download and install each ane (by double-clicking on it):
You can verify the provisioning profile in the Project Options by selecting the Build > iOS Parcel Signing screen and selecting the AppStore | iPhone configuration.
The Provisioning Contour list volition prove all matching profiles - you should run across the matching profiles that you've created in this driblet-downwards list.
iTunes Connect
Follow the app distribution overview, in particular:
- Configuring an app in iTunes Connect
- Publishing to the App Store
When configuring the app in iTunes Connect, don't forget to add the Lookout icon and screenshots:
The icon file should exist 1024x1024 pixels, and volition take a circular mask applied to it when it is displayed. The icon should not accept an alpha channel.
At least one screenshot is required, upwardly to 5 may exist submitted. They should be 312x390 pixels and demonstrate your Spotter App in activity. You tin employ the 42mm watch simulator to accept screenshots at this size.
Visual Studio for Mac
-
Ensure that the iOS app is the startup project. If not, right-click to set it:
-
Cull the AppStore build configuration:
-
Choose the Build > Archive bill of fare item to start the annal process:
You tin can also choose the View > Archives... menu item to see archives that have been created previously.
Xcode
Xcode will automatically show archives created in Visual Studio for Mac.
-
Start Xcode and choose Window > Organizer:
-
Switch to the Archives tab and select the annal that was created with Visual Studio for Mac:
-
Optionally Validate... the archive, then cull Submit... to upload the app to iTunes Connect.
-
Choose the development team (if you belong to more than one) and then ostend the submission:
-
Visit iTunes Connect once more to come across the uploaded binary. Go to your app'due south configuration folio and cull Prerelease from the top bill of fare to see the Builds list:
You tin so submit the app for blessing on the Versions folio. Refer to the iOS app distribution overview for more information.
Troubleshooting
Here are some errors you might encounter while submitting to the App Shop, and the steps yous tin take to gear up them.
Archive bill of fare option is not visible in Visual Studio for Mac
Follow the steps above to configure the solution for archiving. If you cannot set the startup projection correctly, ensure the build configuration is first fix to Debug or Release before attempting to change the startup project. Then set the build configuration back to AppStore.
Invalid Icon
Invalid Icon - The scout application '...watchkitextension.appex/WatchApp.app' contains an icon file '...watchkitextension.appex/WatchApp.app/AppIcon27.5x27.v@2x.png' with an blastoff channel. Icons should not accept an blastoff channel. Follow the instructions for removing the alpha channel from your icons.
CFBundleVersion Mismatch
CFBundleVersion Mismatch. The CFBundleVersion value '1' of scout awarding '...watchkitextension.appex/WatchApp.app' does not match the CFBundleVersion value '1.0' of its containing iOS application `YouriOS.app`. All the projects in your solution - the iOS App, the Sentry Extension, and the Watch App - should be using the aforementioned version number. Edit each Info.plist file so that the version number matches exactly.
Missing Icons
Missing Icons. No icons found for scout awarding '...watchkitextension.appex/WatchApp.app'. Please make sure that its Info.plist file includes entries for CFBundleIconFiles. Follow the instructions in the working with icons to add together all the required images to the Watch App project.
Missing Icon
Missing Icon. The watch application '...watchkitextension.appex/WatchApp.app' is missing icon with proper name pattern '*44x44@2x.png' (Dwelling house Screen 42mm). Ensure y'all have the latest version of Visual Studio for Mac, and that your AppIcon.appiconset contains a consummate set of images. If y'all are withal seeing this mistake, view the source of the Contents.json to confirm it contains an entry for all the required images. Alternatively, once y'all accept ensured you're using the latest version of Xamarin, delete and re-create the AppIcon.appiconset.
[!Of import] There is a known problems in Visual Studio for Mac's Watch icon support: it expects an 88x88 pixel paradigm for the 29x29@3x image (which should be 87x87 pixels).
Yous cannot set this in Visual Studio for Mac - either edit the prototype asset in Xcode or manually edit the Contents.json file.
Invalid WatchKit Back up
Invalid WatchKit Back up - The bundle contains an invalid implementation of WatchKit. The app may have been congenital or signed with non - compliant or pre - release tools. This message may appear during validation and submission, or in an automatic e-mail from iTunes Connect after an obviously successful upload.
[!Of import] You lot must Archive your app in Visual Studio for Mac and and so switch to Xcode 6.2+ to validate and upload to iTunes Connect.
Utilize the Stable Xamarin channel, and Xcode vi.2+.
Invalid Provisioning Profile
Invalid Provisioning Contour. The provisioning profile included in the package ...iOSWatchApp.watchkitapp [iOSWatchApp.app/PlugIns/...iOSWatchApp.watchkitextension.appex/WatchApp.app] is invalid. [Missing lawmaking - signing certificate.] Distribution Provisioning Profiles must exist supplied for all iii projects in a sentry app solution: the iOS App, the Watch Extension, and the Watch App - either explicitly (iii profiles) or via a single wildcard profile. Cheque that the provisioning profiles be in the iOS Dev Center and that you have downloaded and added them to your Mac.
Invalid Lawmaking Signing Entitlements
ITMS - 90046: Invalid Lawmaking Signing Entitlements. Your application bundle 'south signature contains code signing entitlements that are not supported on iOS. Specifically, value '...watchkitextension' for key 'application-identifier' in '...watchkitextension' is not supported. The value should exist a string startign with your TEAMID, followed by a dot '.' followed past the bundle identifier. Ensure your provisioning profiles are gear up-upwards correctly on the Apple Dev Middle, and that you have downloaded and installed them. Too bank check they are gear up in Visual Studio for Mac'south backdrop window for each projection.
Invalid Compages
Invalid compages: Apps that include an app extension and framework must back up arm64. You lot can only add Watch Apps Unified API (64-flake) Xamarin.iOS apps. Correct-click on the iOS app project then go to Options > Build > iOS Build > Advanced tab and ensure that the Supported Architectures for the AppStore-iPhone configuration includes ARM64 (eg. ARMv7 + ARM64).
This bundle is invalid.
ITMS - 90068: This bundle is invalid. The value provided for the key MinimumOSVersion '8.3' is not acceptable. Your parent iOS application must have the MinimumOSVersion set up to '8.ii' or earlier.
Not-public API usage
Your app contains non - public API usage. Please review the errors, and resubmit your application. Ensure yous are using the latest version of Xcode and Xamarin's tools. Your code should not access whatsoever non-public APIs.
Build Error MT5309
Error MT5309: Native linking error: clang: mistake: no such file or directory: This error is likely the result of your having renamed your Xcode installation from Xcode.app. For instance, this error will occur if you rename your installation to XCode half dozen.2.app.
Related Links
- Apple WatchKit Submission Guide
Source: https://github.com/MicrosoftDocs/xamarin-docs/blob/live/docs/ios/watchos/deploy-test/appstore.md
0 Response to "Watchkit Error Uploading to App Store Invalid Icon"
Post a Comment