Grzegorz Leoniec

I did not need that on the M1 and a fresh Flutter 3.0.5 project. Just for reference.

Yeah I did it already and it worked. But to be honest that’s should be four fields to add a read write user and an admin user on first startup...

Hey does anything change now as storybook 7 supports vite natively? https://storybook.js.org/blog/first-class-vite-support-in-storybook/ nuxt/nuxt#418

@ryanheise any progress, new learnings or workarounds on that issue?

@rwrz I did apply your changes onto the latest version, and it works so far for me. Anyone can check it out by using the following dependency: ```yaml # just_audio:...

> > @rwrz I did apply your changes onto the latest version, and it works so far for me. > > Anyone can check it out by using the following...

Is the -1004 Error always a failing proxy? If so, it should be safe to remove, as it would always be beneficial to just keep it alive.

@mattwr18 thanks but the issue is more in the backend then the frontend. I do not understand the relation behavior with proprieties. It does not behave like I would except.

@roschaefer but then we do not have any indication or referencing of a user that we could Display.

@roschaefer I dont think that that would solve the issue to be honest. At least not at first glance!