Mickaël Tricot

Thanks @enix79 for confirming that you have also encountered the problem. I have tried to fix it by setting the `autoPadding` to `true` / `false` but that did not work....

Removing the custom snap point also fixes it for me: - `snapPoints={[window.innerWidth < 1024 ? 0.8 : 0.5]}` → sticky modal footer is displayed on large screens ✅ but hidden...

Thanks @Temzasse for considering fixing this. 👍 If I understood correctly, the suggested solution is not ideal in our case, because the bottom sticky content goes aside on large screens....

No worries @Temzasse, thanks for taking the time to dig into it.

Hello, unfortunately I am still having the described issue ("Could not find a working container runtime strategy" when used with Testcontainers), with nock 14.0.6. It's working fine with nock 13.x.

Hello @Jokero I am experiencing the same issue, and as mikicho mentioned earlier, the best way to resolve it would be to provide a reproduction repository. I haven't had time...

We've noticed the same errors. I believe (but not 100% sure) that it started with [Next.js v14.2.7](https://github.com/vercel/next.js/releases/tag/v14.2.7). We also have an custom `afterCallback` on `handleAuth`.

Hello, Thanks for this nice addition (`withPageAuthRequired`). 👍 Can you please suggest a way to `returnTo` the original URL when it contains parameters (e.g `/protected-page/[slug]`)?