Latest version now gives this error (assuming it is trying to use mkcert without installing it)
Some pre-requirements are missing. If you want the application to work as expected, you need to install the following tool(s):
- mkcert. (Installation link: https://github.com/FiloSottile/mkcert)
If you have already installed the tool(s), please check the PATH environment variable.
As seen in the error message, we're using the
mkcert
command during the solution creation process. So you should downloadmkcert
by following the installation guide.Is this a new feature as it has not been needed before from what I can remember?
No, it's not. If you create a microservice or app project with Kubernetes Configuration checked in the Additional Options step, then it uses the
mkcert
command to create the certificate.
That might be true but I get this error message now as soon as I start the ABP Studio which I have not gotten before. If it is only required for Kubernetes it perhaps should not be required?
Latest version now gives this error (assuming it is trying to use mkcert without installing it)
Some pre-requirements are missing. If you want the application to work as expected, you need to install the following tool(s):
- mkcert. (Installation link: https://github.com/FiloSottile/mkcert)
If you have already installed the tool(s), please check the PATH environment variable.
As seen in the error message, we're using the
mkcert
command during the solution creation process. So you should downloadmkcert
by following the installation guide.
Is this a new feature as it has not been needed before from what I can remember?
Please update the contents of the page RoadMap https://docs.abp.io/en/commercial/latest/road-map#backlog-items
This page should also be updated https://docs.abp.io/en/commercial/latest/aspnet-zero-vs-abp-commercial
So, we can understand what the next releases will be.
Example, when will this feature be implemented?
Thanks
2 months later, the Road map page is still severely outdated, claiming that 8.2 will be released in June
https://abp.io/docs/latest/release-info/road-map
Latest version now gives this error (assuming it is trying to use mkcert without installing it)
Some pre-requirements are missing. If you want the application to work as expected, you need to install the following tool(s):
- mkcert. (Installation link: https://github.com/FiloSottile/mkcert)
If you have already installed the tool(s), please check the PATH environment variable.
Hi,
Ah, so it is only a "typo" where it should have been "key" but instead was "AccessTokenKey"? Seems reasonable when looking at the code more in detail now, was a bit stressed last time around just trying to get it to work and the name AccessTokenKey made it look like something more than just the usual keypair.
Is storage actually used anywhere in the MAUI app currently?
Please also note the part about Exported = true being needed (or implemented / solved elsewhere)
BTW, at least for me, the small emoji icon seems broken now but worked fine before, so you will have to imagine a thumbs up here :)
https://abp.io/docs/latest/release-info/road-map
Is very out of date now that 8.2 has been released several weeks ago.
Hi,
When trying to build a MAUI Blazor (and probably MAUI Xamarin as well I guess) you will get build errors from OAuthSecureStorage as the AccessTokenKey property is not defined.
I can't reproduce the problem.
abp new Qa -u maui-blalzor
dotnet build
Did you build it in Release mode as that is needed to activate the mentioned code? Will build fine in debug mode but not in Release mode as AccessTokenKey isn't declared.
public Task<string> GetAsync(string key) { #if DEBUG return Task.FromResult(Preferences.Get(key, string.Empty)); #else return SecureStorage.Default.GetAsync(AccessTokenKey); #endif } public Task RemoveAsync(string key) { #if DEBUG Preferences.Remove(key); #else SecureStorage.Default.Remove(AccessTokenKey); #endif return Task.CompletedTask; }
The code generated by ABP Suite (and probably the normal MAUI projects in all version) does not seem to be compatible with newer versions of Android. When you try to build it in Release mode with SDK 33 or higher (which is a requirement these days), you will get this error message:
Thanks. We will update the template, and your ticket will be refunded.
Thanks.
Still waiting for a reply here.