nearform / nearform/react-native-workshop
Investigate devices not getting `rotation` property from expo-sensors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 1
Description
One NodeConf.eu 2023 participant had a Motorola phone running Android 9 where the object passed from expo-sensors DeviceMotion lacked a rotation property.
It did have rotationRate and a few other properties (IIRC they all related to relative changes in motion not current position). We tried using rotationRate in place of rotation (with a very different multiplier, like -0.2 or similar), but the game was almost unplayable: the ball responded to active device motions but not in an intuitive way.
We should see if this is a known issue in expo-sensors and consider what fallbacks we could offer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the expo-sensors DeviceMotion behavior on the reported Motorola phone running Android 9, comparing the available properties with other devices. Check whether the missing rotation property is a known issue and identify possible fallback guidance. Done means documenting the cause and an agreed fallback or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100