Atividades de "ezarmer"

For me personally, it should not matter where support comes from. Being told on Discord that I must ask my question via the support website is, well, frankly rude and unprofessional. If the community can help answer questions then it takes some burden off of the support team. So, why wouldn't you want this?

The 2 biggest issues I have with the support are: One line answers with no explanation or details. For example: "Add an override to the X method" and then a link to code on GitHub Similar to item 1, single line responses that are a link to documentation that doesn't answer the question and in most cases we've already read.

Bare-minimum support is to provide a link to documentation. Don't do the bare minimum only.

World-class support attempts to understand what the user is asking and provide a slightly more in-depth answer, an example, or short code snippet. Strive to be world-class.

Speaking of documentation. Either keep up with your documentation or hire a technical writer to do that. Documentation in general seems to be outdated.

One thing I would like personally is a notice that the ticket investigation has started, or even has been seen, on a post.

I've seen one ticket today that's over 9 days old without even initial feedback on it, just a chaser by the OP.

I've logged a P1 ticket for us today as we can't do any work with the feed out, but no idea if it's even been seen by the support team.

I agree with you. It would be nice to know that someone has acknowledge the fact that we've posted a ticket.

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 implements ITransientDependency 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.

The only issue I'm facing now is the hamburger menu doesn't display all of the menu options. It just displays home as seen below in the image.

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.