leecade / leecade/react-native-swiper
CRITICAL BUG
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Which OS ?
iOS
Version
Which versions are you using:
- react-native-swiper v1.5.13
- react-native v0.47.1
Expected behaviour
Swiper should slide from index 0 to n
Actual behaviour
If the index is set to 0, it displays #0 screen for sometime and than (index - 1) screen is displayed on the same initial activeDot.
This happens only first time.
How to reproduce it>
Normal case scenario.
Steps to reproduce
- Open a new screen with Swiper
- Observe the first screen
- After very short time the last screen is displayed
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 issue on iOS with react-native-swiper v1.5.13 and react-native v0.47.1, following the listed three steps. Trace the initial index and active dot behavior; done means the first screen remains displayed at index 0 instead of switching to the last screen after the initial render.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100