Once that has been completed your build should fail when you attempt to run it. As you can see from the attached image the values are trying to use a Date Datatype.
It might be related to TokenProvider in the project.
In the template, it register itself with default name but I found a problem with that logic.
- Please make sure MauiBlazorAccessTokenStore class in your project have
[ExposeServices(typeof(IAccessTokenStore))]
attribute on it and implementsITransientDependency
interface. As the final result it should be something like this:[Volo.Abp.DependencyInjection.Dependency(ReplaceServices = true)] [ExposeServices(typeof(IAccessTokenStore))] public class MauiBlazorAccessTokenStore : IAccessTokenStore, ITransientDependency { // ...
- Make sure MauiBlazorAccessTokenProvider class has also
[ExposeServices(typeof(IAbpAccessTokenProvider))]
attribute on it
[Volo.Abp.DependencyInjection.Dependency(ReplaceServices = true)] [ExposeServices(typeof(IAccessTokenStore))] public class MauiBlazorAccessTokenStore : IAccessTokenStore
I made the changes as requested and to no avail the same issue is present. Is there a way I can get someone to remote in and take a look? At this point it's really becoming a hindrance. I do understand you guys are trying to resolve the problem though.
Maybe it would help if I had more coffee :-). I didn't even realize there was the Android Adb Command Prompt. I did run the command successfully. Per documentation, I did run the command after starting the emulator and it ran successfully. Thank you for the continued support. For others facing the same issue as myself, please follow @ensin advise step-by-step as well as check the documentation link for any updated instructions that may come with future releases.
I attempted to follow the instructions. The error I have is as noted below.
C:\abp reverse tcp:44384 tcp:44384
ABP CLI 7.3.3 Unhandled exception. System.ArgumentException: Option names should start with '-' or '--'. at Volo.Abp.Cli.Args.CommandLineArgumentParser.ParseOptionName(String argument) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Args\CommandLineArgumentParser.cs:line 107 at Volo.Abp.Cli.Args.CommandLineArgumentParser.Parse(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Args\CommandLineArgumentParser.cs:line 53 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 56 at Volo.Abp.Cli.Program.Main(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli\Volo\Abp\Cli\Program.cs:line 43 at Volo.Abp.Cli.Program.<Main>(String[] args)
I will attempt to try your recommendations here soon and reply back. I think I may have been following an older blog post. I was looking for documentation but couldn’t find what I was needing.
Volo.Abp.AbpInitializationException: 'An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.AspNetCore.Components.MauiBlazor.AbpAspNetCoreComponentsMauiBlazorModule, Volo.Abp.AspNetCore.Components.MauiBlazor, Version=7.3.3.0, Culture=neutral, PublicKeyToken=null: An error occurred during the ABP remote HTTP request. (Failed to connect to localhost/127.0.0.1:44321) See the inner exception for details.. See the inner exception for details.'
I've spent all day yesterday trying to get this to work and was unable to do so. I did have ngrok also setup in the MAUI Blazor application which didn't make any difference. I have double and triple checked I have all requirements to run .MAUI installed. If I create a new MAUI HYBRID project from VS it works just fine. I thank you in advance for helping with this.