Łukasz Kosmaty

@RRaideRR I think https://github.com/expo/expo/pull/23345 resolved the issue. This change was backported to SDK 49 as well. However, you tested it using `[email protected], which doesn't include that patch. Can you try...

Hey @hems 👋 Sorry for the late reply. Can you rebuild the js files in the `expo-location` by running `yarn build` in the `expo-location` package? After that, I think we...

I've rebased your code in https://github.com/expo/expo/pull/27724. > One of my concerns is that this could potentially break web applications that were relying on his unexpected/unwanted behaviour, in other words, this...

https://github.com/expo/expo/pull/26688 should fix this bug. If you're still facing the same issue on the newest expo version, feel free to open a new ticket. Be

Hi @matthieugicquel, thank you for your report. Unfortunately, the long snapshot for the image component is due to the `nativeViewRef` prop being present. The testing library prints all the props,...

Thanks for your PR. It seems that you are trying to disable a dev menu in your e2e test. There is a more efficient method to achieve this. Here are...

I've spent some time investigating this issue. Here are my findings: - it's not caused by `expo-modules-core` directly instead it's a combination of the `expo-splash-screen` and the current template. The...

> alternatively, how do you think if we move the expo-modules-core androidTest from expo-go to bare-expo? I think it's a great idea, but it should work properly in both projects....

I have made the decision to relocate the `expo-modules-core` androidTest to `bare-expo` at the moment. It appears to be insignificant to have all the superfluous settings simply to execute tests...

The previous one failed, but this one https://github.com/expo/expo/actions/runs/5508970647 should pass 🤷