Keith Kurak

I get this, too - whether I try a small or big clean up.

Hi! Based on the information provided, we tried to reproduce under Expo 46 with the provided eas.json and specified packages installed, but did not see the error (or any other)....

I got this same error, as well. I haven't tried upgrading babel-eslint, but it goes away if you downgrade eslint to 4.13.1. There's a thread about it on the eslint...

Hi @Adam-Schlichtmann! Is there a particular device for which you experience this issue (e.g., iPad)? I can't reproduce on my iPhone, as it does not let me tap outside of...

Hi @AmedeoOfficial! When you run this snack, can you see what value for the [accuracy](https://docs.expo.dev/versions/latest/sdk/location/#locationheadingobject) prop you get in that same object coming back from `watchHeadingAsync`? 358 and 17 aren't...

@AmedeoOfficial accuracy level 3 means "within 20 degrees", and the difference between 358 and 17 is 19 degrees, so this seems like it could be intended behavior. I did try...

@superyarik thanks for the detailed information and reproduction! I've been able to see the same issue on Android 13. As a workaround, it looks like `uri` returns the correct value...

@LyunKi Hi! Can you confirm if you still experience the issue after upgrading to the latest version of the Expo SDK (run `npx expo upgrade` and accept all prompts). I...

Thanks for the additional info. Does this happen all the time for you, or is it intermittent? I have noticed it on a few systems on the latest version at...

On the **Using Firebase** doc, when it describes `expo-analytics-firebase`, wondering if we can do more to make it clear what this package does, so it's also clear that it's by...