Kubernetes client (Universal App) Development essay-the App also needs to be packaged before logistics, universalapp

Kubernetes client (Universal App) Development essay-the App also needs to be packaged before logistics, universalapp

 

Think of a joke: Tang Miao and his entourage came to the front of the Buddha, ready to learn the scriptures, the Buddha asked softly: Have you brought a USB flash drive? Four mentoring students immediately fell to the ground. Well, it's a long journey, but I want to tell you that the preparations must be in place.

The package and release of the Universal App are not very different from those of the traditional Windows Phone/Windows Store App project. However, some people may encounter problems in these steps, even developers who have published several applications are no exception. Therefore, it is necessary to make a summary of this seemingly tedious process.

Preparations before packaging

 

1. Modify the compilation Mode

During program debugging, we usually select the debug mode, but do not forget to switch to the Release mode during Release. Otherwise, the verification program will not be executed after the program is packaged, let alone uploaded to the app store. To ensure that the program runs on all devices, we choose Any CPU, in this way, we can ensure that our UAP runs on all platforms that can run (including Windows RT flags based on ARM architecture and flags Based on x86 architecture, such as Surface Pro.

 

 

2. Modify the Manifest File

 

The Manifest file records some basic metadata of the project, including the project name, applied permissions, Project Logo and Publisher Information. Only such information is complete and accurate, only packaged files can be automatically verified during upload.

In the project, we can find the appxmanifest file of the project.

 

You can also find the entry to modify the Manifest file through the options in the menu.

 

 

Next we will check whether the content of the Manifest file is complete one by one.

 

On the Application tab, we need to enter the basic information of the project, and confirm whether to modify the corresponding screen rotation direction and how to notify the user when the screen is locked.

 

Unlike Windows projects, the Windows Phone project also requires you to specify whether to allow the App to be installed on the SD card.

 

On the Visual Assets tab, We need to map all Logo images used. Generally, if the image naming rules in the Assets folder are correct, the image can be detected and loaded automatically.

 

It should be noted that the Badge Logo image requirements are strict, and only the white and transparent colors are required, even if one pixel appears in another color, it will be detected during the automatic verification program and will not pass, so be careful when modifying these images, make sure that only the white and transparent colors are included.

 

On the Capabilities page, you must enter the permissions applied for by the project. For example, the project must run on the network, so you must apply for Internet permissions. The most important thing to note is that if you have applied for network permissions for any Windows App, you must add the Privacy Statement entry to the Setting menu, otherwise, it will not pass the manual review phase. For details about how to add a privacy statement, refer to the previous blog: implementation method and experience of Setting Page for the development of the Al App.

 

 

For Windows Phone, you also need to apply for device sensors. If the gyroscope, magnetic field sensor, NFC, front/back camera, and other resources are applied in the App, you need to declare them here.

 

 

On the Declarations tab, We need to declare other resources used by the App. For example, if the blog garden project uses background tasks, we need to declare the portal of background tasks here.

 

If the App uses a special notification event, you can declare it on the Content URIs page. Note that Windows 8.1 only supports https secure pages and does not support http.

 

The Packaging page is critical. Any Filling error here will cause the project to pass the automatic review during upload. Fortunately, if we select to map the project to the App in the store in the following steps, most projects on this page will be automatically filled out. If we choose to only package and entrust others for release, then the information must be complete. The information to be filled in this page can be found on the corresponding developer account page.

Another note is the final Generate app bundle option. If you select always, if the previous Visual Assets have images of various sizes, a bundle is generated during packaging ). In this way, you must upload a bundle to update the project later. Otherwise, the project cannot pass the upload review. This also means that the images in the Assets folder can only be increased and cannot be reduced.

 

 

Of course, you can right-click the manifest file and select view code to modify or update all the above items. It seems that this is also a more suitable method for geek.

 

Start Packaging

After the Manifest file is modified, we can start the formal packaging.

Here we select Create App Packages

 

Here, there are two options: Select Yes to directly log on to the Microsoft Dev account and bind the project to the App in the store, in this way, the developer information in the Manifest file is automatically updated to the corresponding information of the Microsoft Dev account. This method is applicable when you release your own projects.

If No is selected, You do not log on to the account and only package it. This situation is applicable when you entrust a third party to release a project, or you want to package a package to others for testing. After the test is complete, you can directly submit the application with this test package, this is more in line with the general workflow to avoid inconsistency between your test package and the package submitted to the store.

We strongly recommend that you select "No" and use the second method.The next article details how to submit an application.

First, log on to the Microsoft Dev account.

 

After logging in, all projects submitted by the developer are displayed. We can also reserve a new name for the new project.

 

Select the version information for the project, the output location, whether to package and generate CPU information.

 

You can package the project. After the package is completed, the project location is displayed, and the developer is reminded to execute the verification program (Windows App Certification Kit) for the project ). After the upload, the server will first execute this program to automatically verify the project for the first time. If there is any irregularity, it will not pass. Therefore, in order to ensure the upload success, we usually execute a verification program on the local machine first.

 

 

If the verification program passes on the local machine, you can upload the application to the store. Due to space limitations, we will continue to introduce precautions for store uploads in future articles.

 

Summary

This article describes the packaging steps of the Universal App before uploading the store according to the process, and analyzes the minor differences between Windows and Windows Phone App packaging and precautions that may easily cause upload failure.

 

The released applications and code can be found below:

Windows Phone Store App link:

Bytes

 

Windows Store App link:

Http://apps.microsoft.com/windows/zh-cn/app/c76b99a0-9abd-4a4e-86f0-b29bfcc51059

 

GitHub open source link:

Https://github.com/MS-UAP/cnblogs-UAP

 

MSDN Sample Code:

Https://code.msdn.microsoft.com/CNBlogs-Client-Universal-9c9692d1