Rodrigo Gomez Palacio

Hello. Please make sure you are running in a supported environment. Example: **Expo Go is not a supported environment.** See the repo README for more details

Please provide more information regarding your build so I can help you.

Howdy, As a reminder, these are the supported environments. [The Expo run commands](https://docs.expo.dev/workflow/customizing/) (expo run:[android|ios]) [Custom clients](https://blog.expo.dev/introducing-custom-development-clients-5a2c79a9ddf8) [EAS Build](https://docs.expo.dev/build/introduction/) Please make sure you are building and running in one of...

@ilgiapa Are you getting the same error or a different error? Can you please include logs? Furthermore, if you eject, do you still see the error? Is your project a...

Howdy, y'all, That is correct. It does not work in Expo Go. If you're running in vanilla react native, you would need `import OneSignal from 'react-native-onesignal';` and if you're running...

Howdy David, Thanks for reporting this and for your patience. Have you tried renaming the assets manually? Of course, this is not a long-term solution but at least we will...

I am also looking for a way to do this. @pplante this didn't work for me. I have also never used `jest-circus` though. Are there any additional steps needed?

As per our group discussion earlier, let's drop the two "prettier run" commits from this PR until after we land user-model. This will avoid otherwise terrible merge-conflict mishegas. All other...

prefer `unknown` over `any`, or if you know it'll be non-null use `object`

drop `OS` prefix from classes/files