IjzerenHein / IjzerenHein/react-navigation-shared-element
Blink issue on Android
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Hey there!
I'm facing an issue where a blink occurs on screens navigation on Android.
Demo

I've noticed the information on the README where it says that this is expected and therefor `detachInactiveScreens` is set to false on Android, however it seems to have no effect on my project.
Related libraries versions being used:
```json
"react-navigation-shared-element": "3.1.3",
"react-native-shared-element": "0.8.2",
"@react-navigation/native": "5.9.8",
"@react-navigation/stack": "5.14.9",
"react-native": "0.66.0",
```
The app is open sourced, so the code can be viewed here:
[Navigator](https://github.com/guytepper/better-rail/blob/main/app/navigators/main-navigator.tsx#L74) | [Screen 1](https://github.com/guytepper/better-rail/blob/main/app/screens/route-list/route-list-screen.tsx#L98-L108) | [Screen 2](https://github.com/guytepper/better-rail/blob/main/app/screens/route-details/route-details-screen.tsx#L32-L38)
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 with the README guidance about detachInactiveScreens, then inspect the linked Navigator, Screen 1, and Screen 2 files in the Better Rail example. Reproduce the Android navigation transition using the listed React Native and navigation-library versions, and compare the behavior with the documented setting. Done means identifying and resolving the blink during screen navigation without regressing the shared-element transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100