Forum Discussion

Kashyap_Pandya's avatar
Kashyap_Pandya
Copper Contributor
Jun 05, 2023

Login Error, after converting .exe into MSIX Format

We are trying to upload our Application on Microsoft Store. Our Application Original Format is ".exe". In Order to upload on Microsoft Store we are converting our app into "MSIX" format. We are ge...
PaoloLazzaroni's avatar
PaoloLazzaroni
Copper Contributor
Jun 05, 2023

Kashyap_Pandya 

When converting your application from ".exe" to the "MSIX" format and encountering a "Login Error" when submitting the app to the Microsoft Store, it seems to be related to the permissions for generating the "derby.log" file in the default installation location for Windows Apps.

In the Windows App sandbox environment, certain restrictions are in place to ensure the security and integrity of the system. By default, apps installed in the "C:/Program Files/WindowsApps" directory do not have write access or permissions to generate files.

To resolve this issue, you can consider the following options:

  1. Change the location of the "derby.log" file: Instead of generating the log file in the installation directory, you can modify your application to create the "derby.log" file in a location that allows write access for the app. You can use the application's data directory or a user-accessible location such as the user's documents folder.

  2. Request the necessary capabilities in the app manifest: When submitting your app to the Microsoft Store, you can include capabilities in the app manifest that request additional permissions. In your case, you would need to include the necessary capability to generate and write the "derby.log" file. Review the Microsoft Store documentation for details on how to specify capabilities in your app manifest.

  3. Utilize the ApplicationData.LocalFolder: Instead of writing directly to the installation directory, you can modify your application to write the "derby.log" file to the local app data folder, which is accessible by the application. This folder is typically obtained using the Windows.Storage.ApplicationData.Current.LocalFolder API in UWP apps.

Consider implementing one of these approaches based on your application's requirements and the guidelines provided by the Microsoft Store. It's also recommended to consult the Microsoft Store documentation and reach out to their support or developer forums for specific guidance on app submission and permissions.

Akshay_Vadariya's avatar
Akshay_Vadariya
Copper Contributor
Jun 07, 2023

PaoloLazzaroni 

Hello,

we are getting following errors, please guide for further.

 

  • PaoloLazzaroni's avatar
    PaoloLazzaroni
    Copper Contributor
    Jun 08, 2023

    Akshay_Vadariya 

     

    Unable to parse manifest. Edit the manifest file to fix errors.

/*[local-name()="Package" and namespace-uri="http://schemas.microsoft.com/appx/manifest/foundation/windows10"]
/*[local-name()="Applications" and namespace-uri))="http://schemas.microsoft.com/appx/manifest/foundation/windows10"]
/*[local-name()="Application" and namespace-uri="http://schemas.microsoft.com/appx/manifest/foundation/windows10"]
/*[local-name()="Extensions" and namespace-uri()="http://schemas.microsoft.com/appx/manifest/foundation/windows10"]
/*[local-name()="Extension" and namespace-uri="http://schemas.microsoft.com/appx/manifest/uap/windows10"]
/@Category 'windows.appExecutionAlias' violates enumeration constraint of 
'windows.fileTypeAssociation
windows.protocol
windows.autoPlayContent
windows.autoPlayDevice
windows.shareTarget
windows.search
windows.fileOpenPicker
windows.fileSavePicker
windows.cachedFileUpdater
windows.contactPicker
windows.cameraSettings
windows.accountPictureProvider
windows.printTaskSettings
windows.lockScreenCall
windows.contact
windows.appointmentsProvider
windows.alarm
windows.webAccountProvider
windows.dialProtocol
windows.appService
windows.mediaPlayback
windows.print3DWorkflow
windows.lockScreen
windows.aboveLockScreen
windows.personalAssistantLaunch
windows.voipCall'. 

The attribute 'Category' with value 'windows.appExecutionAlias' failed to parse.

     

     

    The error you provided seems to be a formatting error in the manifest of a Windows app. The specific error pertains to the 'Category' attribute with the value 'windows.appExecutionAlias' failing to be parsed correctly. This value is invalid because it violates the enumeration constraint for the 'Category' attribute, which only accepts specific predefined values.

    To resolve the error, you need to modify the app's manifest and correct the 'Category' attribute so that it has a valid value. The allowed values for the 'Category' attribute are:

    - windows.fileTypeAssociation
    - windows.protocol
    - windows.autoPlayContent
    - windows.autoPlayDevice
    - windows.shareTarget
    - windows.search
    - windows.fileOpenPicker
    - windows.fileSavePicker
    - windows.cachedFileUpdater
    - windows.contactPicker
    - windows.cameraSettings
    - windows.accountPictureProvider
    - windows.printTaskSettings
    - windows.lockScreenCall
    - windows.contact
    - windows.appointmentsProvider
    - windows.alarm
    - windows.webAccountProvider
    - windows.dialProtocol
    - windows.appService
    - windows.mediaPlayback
    - windows.print3DWorkflow
    - windows.lockScreen
    - windows.aboveLockScreen
    - windows.personalAssistantLaunch
    - windows.voipCall

    Make sure that the value of the 'Category' attribute in your manifest corresponds to one of these allowed values, and ensure that the formatting of the manifest is correct.

Resources