David Pertiller

It sounds silly, but as workaround I'm feeding the ui-calendar a dummy event (date: 01/01/1900) during onInit(), so that all the events I'm loading or creating subsequently are displayed correctly.

It's worth noting that it can be achieved differently though. If I mutate the search property and just call `next()` it works: ```tsx const requireViewParameter = (to: GuardToRoute, _from: GuardFunctionRouteProps...

same here: ``` Execution failed for task ':app:checkDebugDuplicateClasses'. > A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable > Duplicate class com.google.android.gms.internal.measurement.zzhx found in modules jetified-play-services-measurement-base-20.1.2-runtime (com.google.android.gms:play-services-measurement-base:20.1.2) and jetified-play-services-measurement-impl-19.0.0-runtime (com.google.android.gms:play-services-measurement-impl:19.0.0) ```

I figured that the issue was caused by `"@capacitor-community/firebase-analytics": "^1.0.1",`. I installed the latest v4 branch of the Firebase Analytics plugin instead: `yarn add capacitor-community/firebase-analytics#feat/v4`.

Please make sure that you have specified it like this in your `package.json`: `"@capacitor-community/firebase-analytics": "capacitor-community/firebase-analytics#feat/v4",`

Oh my! I also ran into this problem on iOS for iPhone devices and simulators. What made it really hard to identify the cause of the problem is that the...

The only workaround for me was to downgrade from `[email protected]` to `[email protected]`

For reference: the backwards compatibility package is available here: [react-router-dom-v5-compat](https://www.npmjs.com/package/react-router-dom-v5-compat)

+1 for @ma-zal's solution. Thank you

I tried to inspect how the collision behavior works, but neither of these approaches was successful: - act on zoom changed: since the collisions only change when the zoom has...