WIN10 UWP Series: Issues to note when you update your UWP--targetdevicefamily

Original: Win10 UWP series: Issues to note when updating the UWP--targetdevicefamily

The days before the Currencyexchanger submitted to Microsoft to participate in the master certification, the results did not pass, feedback some errors, it seems that the Microsoft check is more careful.

The main errors are:

Visual feedback helps users recognize whether their interactions with your application is detected, interpreted, and hand LED as they intended.

This means that there should be no touch feedback if a list item is clicked without any action. The UWP ListView item defaults to take the tilt effect, before WP8 the time also through the other toolkit to realize, now comes with, but must think of ways to remove. The solution is to customize the Itemcontainerstyle of the ListView and remove the VisualStateGroup inside.

One more error:

Windows applications should properly navigate back through pages and using the Windows System back button.

In the development of the main for the PC and mobile phone to test, the phone has a hardware return key, so processing the return key event, the PC does not return the key, did not do, but the PC has a tablet mode, can display the return key, this place also need to deal with. The solution is to increase the processing systemnavigationmanager.getforcurrentview (). Backrequested event can be.

Another error is functional, the search currency can not be normal search, after the check code is the search content forgot to carry out the case conversion, you can search for lowercase letters, capital letters will not be searched, is a careless error. Unified ToUpper or ToLower is possible.

One more error is this:

The following recommendation is optional and isn't required for starts compliance. With Windows developers can write a single application so can be installed across a variety of device families includ ing Mobile, Desktop, and XBOX. By default, the Windows applications target all device families. In the application manifest, which is called out as the ' Universal ' Target Device Family. Such applications'll is tested against all device form factors where the this application could be deployed. Alternatively, developers can limit the device families for which a application can be deployed. For example, if ' Desktop ' is specified and the Target Device Family, which application can only are installed on PC devices. When published, this application'll only is available in the Store running on Pcs–it would not be available in the Pho NE store.

The manifest file has Universal as targetdevicefamily. The application currently targets only desktop and mobile. It is recommended, the manifest entry is restricted only to supported devices and that a minimum of the device Familie S is supported.

This means that since only PC and mobile are supported, do not set targetdevicefamily to universal. I took it for granted that the targetdevicefamily was modified in the Package.appsmanifest file, set to desktop and mobile only.

There is one more error:

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

This is because some fonts are truncated when running on a model with a low resolution of 635. And in the horizontal screen when the calculator interface is not displayed completely. So when publishing, try to test the different resolution models to maintain the usability of the interface. I adjusted the flag icon size, and only support the vertical screen status, removed the horizontal screen support.

Then fix a few minor bugs and start uploading the store. The following error occurred during the parsing of the package after uploading:

Xd. UWP. Currencyexchanger_3.1.3.0_x86_x64_arm_bundle.appxupload28.0 MB

This package is for the minimum version 10.0.0.0, but it relies on the framework microsoft.vclibs.140.00 14.0.22929.0 for the minimum version 10.0.10042.0. Update the minimum value in the package to specify a value of 10.0.10042.0 or a larger value. This package is for the minimum version 10.0.0.0, but it relies on the framework microsoft.net.native.framework.1.2 1.2.23231.0 for the minimum version 10.0.10049.0. Update the minimum value in the package to specify a value of 10.0.10049.0 or a larger value. This package is for the minimum version 10.0.0.0, but it relies on the framework microsoft.net.native.runtime.1.1 1.1.23406.0 for the minimum version 10.0.10049.0. Update the minimum value in the package to specify a value of 10.0.10049.0 or a larger value. The project was developed in version 10586 with the following version numbers in the Package.appxmanifest file:

<Dependencies>    <targetdevicefamilyName= "Windows.mobile"minversion= "10.0.0.0"maxversiontested= "10.0.0.0" />    <targetdevicefamilyName= "Windows.desktop"minversion= "10.0.0.0"maxversiontested= "10.0.0.0" />  </Dependencies>

So take for granted minversion to 10.0.10586.0, but compile and error, said maxversiontested can not be less than minversion, so maxversiontested also changed to 10586, or not.

This is strange, the last time the upload did not change this place ah. See has said VC + + Reference version error, and re-upgrade the SQLite components, the result is not.

The UWP's packaging is slow and repeated several times, with the same error, whether it's a three-pack upload or a bundle package.

After repeated contrast, can only doubt targetdevicefamily, will move mobile and desktop back to the original universal, and then upload the success.

Temporarily did not find out what is the cause of this, have you released a universal after the release of Universal only?

If you also have encountered similar problems welcome discussion.

WIN10 UWP Series: Issues to note when you update your UWP--targetdevicefamily