search

banditoth / maui-archiver-vscode

Visual Studio Code extension for archiving/publishing .NET MAUI applications
MIT License
35 stars 3 forks source link

Command 'MAUI Archive: Android - List of Keystores & Check Signature' resulted in error #3

Closed GeorgeLeithead closed 5 months ago

GeorgeLeithead commented 5 months ago

I've installed your extension onto VS CODE. I have then opened a .NET MAUI project/folder, and using the

  1. I open my .NET MAUI project in Visual Studio Code.
  2. Access the Command Palette (Ctrl+Shift+P).
  3. Used the command MAUI Archive: Android - List of Keystores & Check Signature

I get the following error: image

Error: ENOENT: no such file or directory, scandir 'c:\ProgramData\Xamarin\Mono for Android'.

My keystore is at the following path, and I can successfully use any keystore here to sign my distributions: C:\Users\\AppData\Local\Xamarin\Mono for Android\Keystore

Using Visual Studio and distribute an archive, I get the list of keystores: Untitled

GeorgeLeithead commented 5 months ago

I tried using the command "MAUI Archive Settings", but only get the following settings: image

banditoth commented 5 months ago

Hey @GeorgeLeithead Thanks for giving feedback! I had no idea that people would start using the extension so quickly. Unfortunately I haven't had the chance to fully test the extension on windows yet, but I'm working on it. It seems that the burned in path to the Xamarin keystore files is wrong on windows. However, you're looking in the right place, I'll post a configuration option soon to override this path and fix it so that it points to the right place in the default path.

Stay tuned, it will be fixed today or tomorrow.

GeorgeLeithead commented 5 months ago

Hey @GeorgeLeithead Thanks for giving feedback! I had no idea that people would start using the extension so quickly. Unfortunately I haven't had the chance to fully test the extension on windows yet, but I'm working on it. It seems that the burned in path to the Xamarin keystore files is wrong on windows. However, you're looking in the right place, I'll post a configuration option soon to override this path and fix it so that it points to the right place in the default path.

Stay tuned, it will be fixed today or tomorrow.

I blame @jfversluis for his highly effective marketing campaign on X, LinkedIn, etc...

I can confirm that I am indeed on Windows 11, when I experience the issue.

The path where my keystore is located, I believe is the default on Windows, and is user specific.

banditoth commented 5 months ago

Hey @GeorgeLeithead

Seems like the problem have been fixed in version 0.1.3. Could you please check it out? Also you can override the default path in the settings now.

image