TriggeringView on Android
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, react-native, typescript
- Domain
- mobile-dev
Research direction
Start by reproducing the provided TriggeringView snippet on Android, then inspect the TriggeringView implementation and its callback handling. The issue does not name a file or test; done means onHide and onBeginDisplayed behave on Android as they do on iOS.
Written by the indexing model from the issue text.
Description
Apparently exactly the same code for the TriggeringView doesnt work properly on an Android.
Here is the code:
<TriggeringView
onHide={() => alert("Hide")}
onBeginDisplayed={() => alert("Show")}
>
<View style={{ flex: 1 }}>
<Text>Show and hide me</Text>
</View>
</TriggeringView>
The exact same code works just fine on iOS.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from bamlab/react-native-image-header-scroll-view
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bamlab/react-native-image-header-scroll-view#134 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bamlab/react-native-image-header-scroll-view#131 · 1 comment ·
All issues in bamlab/react-native-image-header-scroll-view
Similar issues
-
backend priority:P3 privacy-fix
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#13697 · 1 comment ·
Maintainers usually reply within 1 day
-
area:security documentation effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100