Kenneth Geisshirt

The fix has been released in v10.22.0.

@tomduncalf @cmelchior Please be aware that the changes to `Realm.Auth.EmailPasswordAuth` are cover by a private Jira ticket.

We are aware that RN 0.70 is breaking our recent v11 release candidates. We are working on releasing a new one with support of RN 0.70.

@TadasMil Thank you for reporting. I have a couple of follow-up questions. 1. Which version of Realm Web do you use? 2. When calling `GoogleAuth.initialize()`, did you set `grantOfflineAccess` to...

I think the issue is server-side. I don't know if https://www.mongodb.com/community/forums/t/error-fetching-info-from-oauth2-provider/116780 can help you. Otherwise I suggest you raise a proper support ticket - see https://support.mongodb.com/?_ga=2.190708203.1130835416.1663574736-25634361.1661946744

I am closing the issue due to no updates. Please comment and reopen the issue if needed.

@niklasgrewe Thank you for creating the issue. We will initiate a conversation with our IT security team to get a better understand what a solution should look like.

@jasontlouro Thank you for the suggestion. We are aware of the short-comings of our current implementation. As much, the feature will be added to Atlas App Services and not directly...

@Gnadhi We strongly recommend to try Hermes, Flipper and Realm JS v11.0.0.rc-1 or later. We do not plan to work on the Chrome debugger integration.

We have released v11.0.0 with support of Hermes. You might need to add Flipper to your Android app manually: https://fbflipper.com/docs/getting-started/react-native-android/