I'm having the exact same issue. This is not an answer to your question, but I think the problem comes from the update to Expo 52 with the new architecture, which, as far as I understand it, is unavoidable if you wanna use Expo Go for testing. They're working on it, but there isn't a proper solution yet. You can browse through this issue on the react-native-maps github for more information:

https://github.com/react-native-maps/react-native-maps/issues/5206

If you've found something that works in the meantime, I'd love to hear it