contactsimonwilson

React native exposes DevSettings.reload, which should act as a suitable replacement. We have re-exported reloadAsync in our project `export const reloadAsync = __DEV__ ? DevSettings.reload : reloadUpdatesAsync; `

> same here with slightly different error message_ > > `Fetching the token failed: Please set your Project ID. A valid Firebase Project ID is required to communicate with Firebase...

> I think this problem might be in expo go. After the new update, I am facing this problem. I try to install the expo-notifications older version, but the same...

> > No it does not work in dev right now. It used to work in older versions. But as described above: it still works in production app. > >...

> Really good change imo! Do I understand correctly that this keeps the current client-facing behaviour where shit is the key used to activate? Yes, exactly. This maintains full backwards...

Converted back to draft because after more consideration, the API could be even more flexible (onStart/onEnd)

I'm facing the same limitation @drcmda would you be happy with something like the following? https://github.com/contactsimonwilson/drei/commit/bf14aaf5ea7e6ea949b3f2c336311376499526be Happy to make a PR. Should this item be tagged as a bug or...

Can confirm that downgrading from1.1287.0 to 1.1285.0 fixes the issue with dots on the agenda (at least in our use case)

@Rapsssito what subdirectory would you like the config plugin in? I've written one for a project I'm working on and would be happy to make a PR.

Sure do. Check the plugin directory of this repo. https://github.com/includable/react-native-email-link