Felix Mosheev

This lib doesn't supports connection via service account, therefore, I've generated a refresh token for the service account with the givven form

Due to this issue I have cache miss every build :|, pls let's fix it 🙏🏼

New build  Old build  both of them are mapped to the same cache-key ``` d7fe8e51825b14d0a67f622d69785219de9a0d33b498c2fb8042f0bf27804c0bd2f37d826feaa07eee82fbd09d963f38e217c68f02eeecc332dbd1a3a9b4ff99 ```

```yml name: Build & Deploy on: push: tags: - 'v1.*' jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v1 with: node-version: 12.x - uses: bahmutov/npm-install@v1 - name: Build...

@timbuckley can you help?

Since monoreo hoisting all the packages on the root `node_module` all the paths to `react-native` stuff are wrong. I've tried not hoist them, then `mobx`(which was installed at the root...

Actually I've managed to run the ios version inside monorepo, unfortunately I've busy as well, so I put the project on hold for now.

Regarding hot reload, you may check out [i18next-hmr](https://github.com/felixmosh/i18next-hmr), example folder which contains an example setup for popular frameworks. It works perfectly with next.js on a daily basis :]

This is exactly the problem that `i18next-hmr` solves, when the translations are change, your browser (& server) will reflect the new translation (without reloading dev server or the browser state)....

> Why is the example here `getInitialProps` is not mandatory, for client side HMR you will need `i18next-http-backend` (this lib), it works with Webpack's HMR mechanisem.