Florian Daniel

@schiller-manuel of course you where right! I checked our code again and we had an unchecked `window.location` usage burried somewhere. Your provided example works without a problem!

I want to describe our use-case: We are offering our app in the european union and in the US. With the EU having the GDPR (data privacy law), we have...

We currently have a solution with version 1.13X: in vite.config.ts ``` import svgr from "vite-plugin-svgr"; import tsConfigPaths from "vite-tsconfig-paths"; import { tanstackStart } from "@tanstack/react-start/plugin/vite"; import viteReact from "@vitejs/plugin-react"; import...

I run into the same issue but for me it is not user consent that I run before `await SentryFlutter.init` but some other async initialization logic that determines the Sentry...

we are also coming across this issue now. we expected it would be easy to implement, because in angular it is. but sadly impossible in nativescript to have a nice...

@csimpi but how do you handle the wait time? The splashscreen already disappears at this point :(

I tried that, but you can see the animation. This is my route structure and instead of a resolver i do the async logic and the navigation in the SplashComponent....

Also facing the same issue. I believe it is due to a circular dependency between `router.tsx` importing `routeTree`, and `routeTree.gen` imports `router.tsx` router-->routeTree->router

Me and my colleagues have it frequently whenever we start the project initially. It self-resolves, so if we just wait usually at after a minute or so and the project...

Sorry no, it happens again and again everytime we start the vite dev server. However from my recollection it does not happen every time but pretty frequently.