Win10 UWP series: issues that need attention when updating UWP-TargetDeviceFamily, win10uwp

Win10 UWP series: issues that need attention when updating UWP-TargetDeviceFamily, win10uwp

A few days ago, I submitted CurrencyExchanger to Microsoft for Master authentication. The result failed and some errors were reported. It seems that Microsoft has carefully checked the results.

Errors mainly include:

Visual feedback helps users recognize whether their interactions with your application are detected, interpreted, and handled as they intended.

That is to say, if a list item does not have any action after it is clicked, there should be no touch feedback. By default, the ListView item of UWP has the Tilt effect. In the past, WP8 was implemented through another Toolkit. Now it comes with it. Instead, we need to find a way to remove it. The solution is to customize the ItemContainerStyle of ListView and remove the VisualStateGroup in it.

 

Another error:

Windows 10 applications should properly navigate back through pages when using the Windows 10 system back button.

During development, the system mainly tests PC and mobile phones. The mobile phone has a hardware return key. Therefore, after handling the return key event, the PC does not have a return key, but the PC has a tablet mode, yes, you can display the return key, which also needs to be processed. The solution is to add the SystemNavigationManager. GetForCurrentView (). BackRequested event.

 

Another error is functional. The search currency cannot be properly searched. After checking the code, the search content is case-insensitive. You can search for lower-case letters, and the upper-case letters cannot be searched, careless error. You can unify ToUpper or ToLower.

Another error is as follows:

The following recommendation is optional and not required for STARTS compliance. With Windows 10 developers can write a single application that can be installed across a variety of device families including Mobile, Desktop, and XBOX. By default, Windows 10 applications target all device families. In the application manifest, this is called out as the ‘Universal’ Target Device Family. Such applications will be tested against all device form factors where this application may be deployed. Alternatively, developers can limit the device families for which an application can be deployed. For example, if ‘Desktop’ is specified and the Target Device Family, that application can only be installed on PC devices. When published, this application will only be available in the Store running on PCs – it will not be available in the Phone store.
 
The manifest file has Universal as TargetDeviceFamily. The application currently targets only desktop and mobile. It is recommended that the manifest entry is restricted only to supported devices and that a minimum of two device families are supported.

This means that since only PC and Mobile are supported, do not set TargetDeviceFamily to Universal. I modified TargetDeviceFamily in the Package. Modify manifest file and set it to only Desktop and Mobile.

 

There is another error:

The application should adapt properly to portrait or landscape view if supported.

This is because some fonts are truncated when running on models with low resolution such as 635. In addition, the calculator interface is not completely displayed on the horizontal screen. Therefore, you should try to test different resolution models to maintain the interface availability. I adjusted the size of the Flag icon and only supported the portrait screen status.

 

Then we fixed several bugs and started uploading the store. The following error occurs during the analysis package after uploading:

XD. UWP. CurrencyExchanger_3.1.3.0_x86_x64_arm_bundle.appxupload28.0 MB

This package is applicable to the minimum version 10.0.0.0, but relies on the Microsoft. VCLibs.140.00 14.0.22929.0 framework for the minimum version 10.0.10042.0. Update the minimum value in the package to specify the value of 10.0.10042.0 or a larger value. This package is applicable to the minimum version 10.0.0.0, but relies on the Microsoft. NET. Native. Framework.1.2 1.2.23231.0 framework for the minimum version 10.0.10049.0. Update the minimum value in the package to specify the value of 10.0.10049.0 or a larger value. This package is intended for the lowest version 10.0.0.0, but relies on the Microsoft. NET. Native. Runtime.1.1 1.1.23406.0 framework for the lowest version 10.0.10049.0. Update the minimum value in the package to specify the value of 10.0.10049.0 or a larger value. This project was developed in version 10586. The Package. appxmanifest file contains the following version numbers:

<Dependencies>    <TargetDeviceFamily Name="Windows.Mobile" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" />    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" />  </Dependencies>

So it is assumed that the MinVersion is changed to 10.0.10586.0, but an error is reported during compilation, saying that MaxVersionTested cannot be smaller than Minversion. Therefore, the number of MaxVersionTested is changed to 10586, but it still cannot be.

This is strange. It was not changed during the last upload. We can see that the reference version of VC ++ is incorrect and the Sqlite component is upgraded again.

The UWP package speed is very slow and has been repeated several times. Whether it is to upload three packages or one bundle package, it is the same error.

After repeated comparisons, you can only suspect that TargetDeviceFamily has changed the Mobile and Desktop back to the original Universal, and then the upload is successful.

Why is this not found yet? Is it possible to publish the Universal only once after the Al is published?

If you have encountered a similar problem, you are welcome to discuss it.