UWP blank app failing Windows App Certification Kit HighVersionLie test?

I have a windows UWP xamarin forms app, which I am trying to get to pass the Windows App Certification Kit tests for sideloading.

It passes every test except the third 'Deployment and Launch Test' called 'HighVersionLie'.

I spent some time trying to figure out what might be going wrong with it, but couldn't find anything in my app that referenced the version of windows, couldn't get it to pass by removing add ons, etc.

In desperation I tried the simplest possible test I could think of.

  1. Open Visual Studio (2017, Community version).
  2. Click File->New Project
  3. Go to Cross-Platform, choose Mobile App (Xamarin.Forms), right side says 'Visual C#', a multiproject template for building apps for iOS, Android...
  4. Click OK.
  5. The app is created. Click on the android and ios projects and right click, then select 'unload project'.
  6. Change target from 'Debug', to 'Release'
  7. Rebuild solution
  8. right click on UWP app, click 'Store'
  9. Select 'Create App Packages'
  10. In the ensuing popup select 'I want to create packages for sideloading'
  11. Click Next
  12. Click 'Create
  13. In the 'Package Creation Completed' popup that appears, click 'Launch Windows App Certification Kit'.
  14. Leave every test checked and run the tests.

When I followed this process I got the same result that I got for my app. That is, the 'HighVersionLie' test continued to fail. Does anyone know what/if anything can be done about this? Is there anything about the properties of the app (of, apparently, ANY xamarin windows app) I can change that might get it to pass this test?

-Thanks,
Walter

Best Answers

  • wlangendorfEMwlangendorfEM ✭✭
    Accepted Answer

    I noticed online that the other people who'd had this trouble saw it go away after switching boxes, and lo and behold that was my experience.

    I put the hello world app on another machine, ran the kit, it passed. Put the real app over there, ran the kit, it passed.

    Still have no idea why one test of the kit fails for every app run on my own machine, but I guess it doesn't matter now.

Answers

  • ColeXColeX Member, Xamarin Team Xamurai
    edited March 20

    The "HighVersionLie" test checks to see if your app will crash if it is told that it is running on a new, higher version of Windows (a version which has not been released yet).

    You might also try Changing your target versions to higher values to see if that gets rid of the error

    Refer https://stackoverflow.com/a/48488741/8187800.

    BTW, could you try to upload to store and check the wack , since the result message is more accurate than using sideloading.

  • JohnHardmanJohnHardman GBUniversity mod

    I'd like to try to reproduce this. If I execute the 14 steps above, will anything be made public in the store, or will it still be only visible to me?

  • wlangendorfEMwlangendorfEM Member ✭✭

    @ColeX

    I've tried changing my target versions, but that didn't seem to help.

    I can't upload to the store because my company email isn't associated with a Partner Center account, so I can't test that kit. I'm trying to get them to change that, but no luck thus far.

    @JohnHardman Nothing will be made public in the store at that time. You will have successfully (or unsucessfully) executed the app certification kit on a basic xamarin forms app. The point of the kit is to validate that the app is safe for sideloading, but the steps above don't actually sideload it to any other machine, they just run the tests.

  • wlangendorfEMwlangendorfEM Member ✭✭
    Accepted Answer

    I noticed online that the other people who'd had this trouble saw it go away after switching boxes, and lo and behold that was my experience.

    I put the hello world app on another machine, ran the kit, it passed. Put the real app over there, ran the kit, it passed.

    Still have no idea why one test of the kit fails for every app run on my own machine, but I guess it doesn't matter now.

  • JohnHardmanJohnHardman GBUniversity mod

    @wlangendorfEM said:
    I noticed online that the other people who'd had this trouble saw it go away after switching boxes, and lo and behold that was my experience.

    That's worrying. Will try to look into that when I get a bit of time

  • wlangendorfEMwlangendorfEM Member ✭✭

    @JohnHardman

    My boss still wants me to get the tests working on the original device, so I'm still poking away at this problem. I gathered some information to try and clarify what might be different between the 2 boxes...

    In the certification results page provided by the kit afterwards:

    App name : <Unimportant, same for both>
    App publisher: <Unimportant, same for both>
    App version: <Unimportant, same for both>
    App Architecture: x64 (same for both)
    Kit Version: 10.0.17763.132 (same for both)
    OS Version: (Passing Machine) Microsoft Windows 10 Enterprise (10.0.17134.0) (Failing Machine) Microsoft Windows 10 Pro (10.0.17134.0)
    OS Architecture x64 (same for both)
    Report Time: Unimportant (reflects when I ran each kit's tests)

    -Hope this helps you reproduce the issue!
    Walter

  • JohnHardmanJohnHardman GBUniversity mod

    @wlangendorfEM

    I've started having a look - just grabbing a few minutes here and there when I can. I am definitely finding the Windows App Certification Kit both unhelpful (the messages are too vague to be any use in tracking down issues) and inconsistent (if I run the full suite of tests and it says one failed, then run just that one it passes).

    Would you happen to know any way to get verbose reporting/logging from WACK? I admit that I haven't Googled that yet - thought I'd ask first as you've been looking at WACK already :-)

    @ColeX - would you happen to know if use of any of the Xamarin.Essentials stuff or any of @JamesMontemagno 's plugins will result in WACK failures?

    I've already removed use of Win2D from my app as others have reported that it results in WACK failures (thankfully, what I used it for wasn't overly important).

  • JohnHardmanJohnHardman GBUniversity mod

    @wlangendorfEM

    I've just created a new solution (as per your steps) and run the WACK. It passed first time.

    Still trying to get my own (large/complex) app to pass though, not being helped by the vague messages that the WACK generates, and the inconsistency of their appearance.

  • wlangendorfEMwlangendorfEM Member ✭✭

    Hi @JohnHardman thanks for trying to recreate this issue. Were you using WIndows Pro or Windows Enterprise? My hello world app worked on the Enterprise, failed on the Pro, so it might be a Pro specific interaction issue.

  • JohnHardmanJohnHardman GBUniversity mod

    @wlangendorfEM said:
    Hi @JohnHardman thanks for trying to recreate this issue. Were you using WIndows Pro or Windows Enterprise? My hello world app worked on the Enterprise, failed on the Pro, so it might be a Pro specific interaction issue.

    I am using Pro.

  • wlangendorfEMwlangendorfEM Member ✭✭

    @JohnHardman Gah, this bug is inexplicable. Is your pro also version 10.0.17134.0, and were you also using Kit version 10.0.17763.132?

    Ooh, also, maybe we are using different visual studios versions. I have Community 2017, maybe you were using a different one?

  • JohnHardmanJohnHardman GBUniversity mod

    @wlangendorfEM said:
    @JohnHardman Gah, this bug is inexplicable. Is your pro also version 10.0.17134.0, and were you also using Kit version 10.0.17763.132?

    Ooh, also, maybe we are using different visual studios versions. I have Community 2017, maybe you were using a different one?

    Windows 10 Pro 10.0.17763 Build 17763
    WACK 10.0.17763.132
    Visual Studio 2017 Community

Sign In or Register to comment.