Details

    • Type: Improvement
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: Release 7.1.0
    • Fix Version/s: Release 7.1.1, Hyperloop 3.0.4
    • Component/s: Windows
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      2018 Sprint 07 SDK

      Description

      Apparently Microsoft starts rejecting our HAL.DLL in WACK (Windows Apps Certification Kit) just because Windows system has HAL.DLL in system library. We need to rename it in order to pass the cert.

      I had the same issue and i wrote to Microsoft in order to discover what was the real problem and i finally find out: the problem is that the app package includes the HAL.dll library which has unfortunately the name of a Windows system library, so they told me to rename it if it is a different library because the current WACK (Windows Apps Certification Kit) which now is used for the store certification doesn’t accept it.
      The reason why the local WACK certification doesn’t detect this problem is that the new WACK is not yet available, it will be released with the next Windows update.
      Conclusion: i think the HAL library needs to be renamed.
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                amukherjee Abir Mukherjee
                Reporter:
                kiguchi Kota Iguchi
                Reviewer:
                Ewan Harris
              • Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                    Git Source Code