expo: MapView from React-Native-Maps appears as a grey block on Android

Edit from Expo, see the latest status of this issue here.

Summary

When running any app following the instructions on https://docs.expo.dev/versions/latest/sdk/map-view the map appears as a gray block on android. NOTE iOS seems to be working fine?

Managed or bare workflow? If you have made manual changes inside of the `ios/` or `android/` directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

Package versions

"dependencies": {
    "expo": "^46.0.0",
    "expo-status-bar": "~1.4.0",
    "react": "18.0.0",
    "react-dom": "18.0.0",
    "react-native": "0.69.3",
    "react-native-web": "~0.18.7",
    "react-redux": "^8.0.2",
    "react-native-maps": "0.31.1"
  },

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: Linux 5.18 Pop!_OS 21.10
      Shell: 5.1.8 - /bin/bash
    Binaries:
      Node: 16.13.1 - /usr/local/lib/node/nodejs/bin/node
      npm: 8.1.2 - /usr/local/lib/node/nodejs/bin/npm
    npmPackages:
      expo: ^46.0.0 => 46.0.2 
      react: 18.0.0 => 18.0.0 
      react-dom: 18.0.0 => 18.0.0 
      react-native: 0.69.3 => 0.69.3 
      react-native-web: ~0.18.7 => 0.18.7 
    npmGlobalPackages:
      expo-cli: 6.0.1
    Expo Workflow: managed

Reproducible demo

https://snack.expo.dev/xdxj1hUb7

Stacktrace (if a crash is involved)

N/A

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 25 (12 by maintainers)

Most upvoted comments

It is not SDK 46 problem! @brentvatne @da45

With SDK 45, Expo Go 2.25.1 grey block on android, crash on ios. With SDK 46, Expo GO 2.25.1 grey block on android, crash on ios.

But, With SDK 45, Expo Go 2.24.3 work.

How to downgrade Expo 45 with Expo Go 2.24.3.

- Delete Expo Go app from Simulator and Real Device.
1. expo upgrade 45
 - Downgrade to sdk 45, because  Expo Go 2.24.3  doesn't support Expo SDK 46.
3. expo start
  - Expo , automatically install expo go 2.24.3.

Now you can wait for fix Expo Go problem 😃

hlthi on Aug 13, 2022

you can create a development build of your app with your own api key, without needing to use ‘bare workflow’: https://docs.expo.dev/development/introduction/

brentvatne on Aug 12, 2022

Granted there isn’t a misconfiguration in your config file, it could potentially be related to https://github.com/expo/expo/issues/18530. I never confirmed what happens on android emulator, but Google Maps did seem to render on a physical Android device following the documentation.

iM-GeeKy on Aug 9, 2022

Based on your suggestion I moved to the expo development build rather than the bare workflow. And the map showed up right away no API key necessary.

However, I continued to plug along and move my firebase implementation to the legit version of firebase rather than using the JS SDK that I was using with expo go.

And the map immediately started crashing lol. Like it started expecting an API key when firebase got added.

I’ve moved to using mapbox instead while I wait for this issue to be addressed

[edit] removed my salty comments. I just picked a bad week to pick up react native lol

swordensen on Aug 13, 2022