Android Release ResourcesNotFoundException for MapView Marker after Update

MapView throws an android.content.res.Resources$NotFoundException: Resource ID #0x0 after the OTA when using an image marker:

        <Marker
          coordinate={coordinate}
          title={titleName}
          image={require('../assets/map/marker-yellow.png')}
          description={longMessage}
          key={keyName}
        />

This happens only in release mode and on android after the over the air update.
Under ios the OTA has no issues and the marker is shown before and after the update.
Rendering the image directly is successful on android even after the OTA in release mode:

        <Image source={require('../assets/map/marker-yellow.png')} />

expo diagnostics:
Expo CLI 3.28.0 environment info:
System:
OS: macOS 10.15.6
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
npm: 6.14.5 - ~/.nvm/versions/node/v14.4.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
IDEs:
Android Studio: 4.0 AI-193.6911.18.40.6626763
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
npmPackages:
expo: ^39.0.0 => 39.0.3
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3
react-native-web: ~0.13.7 => 0.13.14
react-navigation: ^3.11.1 => 3.13.0
npmGlobalPackages:
expo-cli: 3.28.0
Expo Workflow: bare

Hey @jph,

Could you try reproducing this in a newly created project with a different asset? If you are able to reproduce it, could you please create a Github Issue so we can track this bug?

If it seems to be project specific, we can continue discussions here.

Cheers,
Adam

Hi Adam,

thank for helping on this topic.
I found out that the OTA works when I change the Marker to:

<Marker
      coordinate={coordinate}
      title={titleName}
      description={longMessage}
      key={keyName}
>
   <Image source={require('../assets/map/marker-yellow.png')} />
</Marker>

Using the image tag instead of the image parameter solves the problem in my case.