One of the common rule is to encrypt data of our clients in the storage system. I want to show you, how we could do the very simple implementation of such encryption in our node.js APIs, by using Sequilize hooks.
Since Expo has released SDK 40, we are obligate to migrate to submodule expo-notifications. It is the right way of development, but this library seems to have some problems, which we have to face up to.
Unfortunately, from time to time, I face some problems with my credentials for PUSH notifications. When I try to send PUSH through Expo PUSH Broadcaster, it responds with an error "Could not find APNs credentials for {bundleIdentifier} (@{user}/{app_slug}). You may need to generate or upload new push credentials". When I am writing this - I have no idea why it is happening, but I know how to fix it fast.
Some time ago, I wrote an article, how to build standalone apps with Expo. It's not a very complicated process, but if you lack knowledge about DevOps, you could be a bit confused. So, I was looking for a solution: how to make it easier. Unexpectedly, Github extended a helping hand by providing Github Actions - easy to configure set for CI and CD for projects based on their repositories. I've checked it, and it works great!
I prepared a small extension for all Expo and VS Code users. We can use our IDE to send a request to Expo PUSH broadcaster without any other tools.
Releasing a mobile app could be very painful. The deployed codebase is hard to switch on users' devices. If you are a front-end-based developer, as I was, it's harder to get used to that you couldn't just update your app on the client's side. It's not a matter of clicking F5 on the keyboard anymore.