Whether you use react-native-firebase or react-native-push-notifications, there’s a bit of prior configuration you need to do for each native platform and, as you might expect, things will flat out not work for you if they are not done properly.
The configurations are pretty straight forward for either platform so you can just check them out here for firebase and here for react-native-push-notification. If you have any issues with that feel free to leave a comment below.
If you are managing multiple firebase projects, be sure to use the proper console to test the proper project. I for one, found myself…
Performing firebase-storage file management operations with Node.js turned out to be a bigger hassle than I had imagined so here’s a walkthrough of how I managed to get it working.
All the relevant steps have been setup in the snippet above but I’d like to highlight a few points
Even though your project is a firebase project with authentication, database, storage etc. all sourced from firebase, firebase-storage actually relies on google-cloud/storage and requires using their APIs to manage your firebase-storage’s contents.
This is also why we need to install @google-cloud/storage with line 56 and import Storage from it on line…
When I first started with redux this is what it looked like
And gosh was it a hassle! Switching between a dozen files to create new actions, setup new types and add new cases to the reducer just to manage one new piece of redux state! Then there’s dispatch! And then extra complexities when it comes to something as simple as routing to a new section of your app when you are dealing with an asynchronous function with an action. But if there is an easier way to handle all this, I may have just stumbled across it. …
What to say . . .