[sensors][android] Fix crash when using DeviceMotion module

[behenate]

Why

Currently DeviceMotion module crashes with

Tried to obtain display from a Context not associated with  one.

Fixes #28820

How

The orientation is now obtained from the current activity instead of reactContext.applicationContext

Test Plan

Tested in BareExpo

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: abf6b83

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-sensors/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "0f86ac256489e345fffd780ea1f873e4db8c17ca"
  }
]

---

Generated by PR labeler 🤖

[cjoshmarshall]

Still getting the issue with 13.0.9

[gani2009]

this seems to only happen on emulator expo go, while physical device expo go/build is working with no error. expo-sensors version is 13.0.9 too

[cjoshmarshall]

gani2009 Not really. Expo app throws error in physical device too.

[behenate]

@gani2009 @cjoshmarshall Are you both using expo-go? Updating the package version in package.json won't usually work for expo-go (unless you only want changes from the js side of the package), since the native code is embedded into the app, which was last updated on 2nd of May, therefore the fix won't be there.

[cjoshmarshall]

@gani2009 @cjoshmarshall Are you both using expo-go? Updating the package version in package.json won't usually work for expo-go (unless you only want changes from the js side of the package), since the native code is embedded into the app, which was last updated on 2nd of May, therefore the fix won't be there.

@behenate Yup, using expo-go.

[behenate]

@cjoshmarshall Hm, in that case I'd recommend creating a development build. The quickest way is probably just running npx expo run:android or npx expo run:ios to create a local build. You can read more about this here, even more here and how to create development builds with eas here

For local builds you will need Android Studio and/or Xcode depending on what platform you want to develop for

[cjoshmarshall]

@behenate Apparently it seems like it does work in local builds. But still dont quite understand the reason why it wont work in expo-go.

[behenate]

@cjoshmarshall The fix for the issue is in the native code of the package, but the native code for some selected, most popular packages is shipped with Expo Go and it's "frozen" at a specific version, because it's impossible to update it after compiling Expo Go. It's a little outdated, because we don't update Expo Go that often.

Expo Go doesn't actually use the native code from the node-modules folder (it's impossible as the app is already compiled), only the js code. So even if you have the newest version of the package in node-modules Expo Go will still be using the native code for the package from the time when it was compiled.

The current version of Expo Go doesn't contain this fix, so it still crashes.

For local builds you are compiling the code from node-modules into an app, so if you have the newest version of the package there, you can be sure you are also running the native code with all fixes.