Peter Hijma
Peter Hijma
Got the same error today.
I get this as well, not locally, but with the automated tests inside play.google.com. I've got a bit more info, but no simple snippet for reproduction. I'm using moor `4.4.0`...
> Thanks for the additional information! Judging from the error code, it looks like the database is somehow getting used after being closed. I'm not yet sure how that could...
The problem for me seems a combination of deleting/creating databases (I'm using encryption and the user should be able to login/logout and create a new db + password every time)....
Looks like they are rolling it out gradually? Right now I see the old play store in my browser again.
@timtraversy So apparently the store changed for more users. Any idea how to proceed? I looked a bit into it myself, but getting the version from the HTML page itself...
Thanks for the response @Atinux I'll clarify my goals: I protect my frontend using `@nuxt/auth` globally. This works very well, also in combination with `@nuxt/content`. The pages I created inside...
I had the same problem with the form example. Fixed this case locally inside `FormItem.vue` by removing the import from `radix-vue`, so it uses the one from Nuxt automatically: ```typescript...
> ? I do not quite understand the issue. The content pages are not protected. As mentioned everything in /about/ is protected. > > Can somebody clearify the issue here?...