Hi, anyone has worked out the github auto deployment with Realm App? It looks like the documentation is a little bit outdated, such as it mentioned --for-source-control option, which is not working any longer.
And the key issue is after implementation, the process looks fine, but custom resolvers of graphql won’t be deployed. Even I have export the realm app from UI, and then deploy them into another app with github. Everything deployed except the custom resolvers. No error in the log. No trace to find any info.
Hey Lawrence, we don’t have this at the moment, but you can still use Firebase Auth with Realm using JWT Auth (or any other external auth service that provides Twitter OAuth).
I’m having the same issue, and it’s a bit worst, because when I manually create the Custom resolvers on the UI it generate a config/deployment draft and after I approve the draft it merges to Git which then triggers the deployment and removes the manually created Custom Resolvers.
The root cause is version of realm-cli , in their docs, v1 has been used, but in their guides when enable the auto deployment, v2 has been used (which is in beta stage).
We need to stick with v1 version, which is stated in their docs, just don’t follow the guides when enable the feature. The v2 version has many issues, such as the app id need to be presented, and the custom resolver not get synced, etc. The V1 version at least worked better with git integration.