Steffen Forkmann

@jayshah123 are you sending this as pull request?

The part with Objects.requireNonNull(accessFineLocation); Objects.requireNonNull(accessCoarseLocation); could be removed then

@jayshah123 I can do it if you don't have time

I have something similiar but directly in Expo Go app: Error: Encountered an exception while calling native method: Exception occurred while executing exported method requestPermissionsAsync on module ExpoNotificationPermissionsModule: String resource...

there is already a fix - but unfortunately the fix is not released as a npm package

We're hit by this as well. This is really unfortunate and should be mentioned in the sdk 49 blog post.

Is there a way to fix this by expo downgrading the maps dependency for now?

 We tried to update to 2.0 beta as described. But Google isn't happy with that.

@brentvatne I mean that as you can see in the screenshot the workaround seems to fail on some devices. Before the upgrade to 2.0 beta we did not have any...

I downgraded the dependency to the one that was used in sdk 48. IIRC that was 1.3.2 and all reported issues from the Google play store prerelease report are gone....