Alessandro Magnolo

in my experience the component works with Vaadin 23, but it breaks if compiled for production using Vite.

I confirm that problem is solved with WildFly 26.1.2.Final (tested with Vaadin 23.2.8, OpenJDK 17.0.5). This issue can be closed.

When was this implemented? The key binding "." doesn't work for me, and it's not in the documentation... any chance it was lost?

can you reopen this issue or should I open a new feature request?

Actually, hiding hidden files should be the default behavior: they are **hidden** for a reason, and _by definition_ showing them in a terminal navigator is a bug. So the patch...

Same issue, notifications sent twice, but only on IOS, no problem in android. I moved from classic to EAS build, and to latest SDK.

I confirm that the problem is that the push token changes when the native app, built with EAS, is updated by the end user. The old token, stored in the...

> @theorytank for IOS [`Application.getIosIdForVendorAsync()`](https://docs.expo.dev/versions/latest/sdk/application/#applicationgetiosidforvendorasync) and for Android [`Application.androidId`](https://docs.expo.dev/versions/latest/sdk/application/#applicationandroidid) Maybe we should instead use the [native device push token](https://docs.expo.dev/versions/latest/sdk/notifications/#getdevicepushtokenasync-devicepushtoken) as a unique id?

It is unclear whether this is an Expo/EAS bug or the official documentation is misleading, as it never mentions that you can get several different valid Expo push tokens for...

> @amagnolo I actually tried that and so far consistent, however I'd really like to figure out how to replicate the issue to prove it. Install, uninstall, re-install? I've tried...