React-native-swiper: Android Blank Render & Pagination Issues

Created on 17 Mar 2018 · 10Comments · Source: leecade/react-native-swiper

I have a dynamic swiper and I'm using the width resize on component mount hack so that the initial render isn't blank.

The problem with this is it messes up my pagination - the dots get stuck and don't always update. If I remove the width declaration from the swiper the pagination works perfectly.

I've tried a combination of width/height declarations but the pagination only works consistently when removed.

Anyone have a similar issue or know a solution?

Source

djpetenice

👍5

All 10 comments

Does this happen in Android, iOS or both?

krvajal on 1 Apr 2018

I'm only developing for Android. I've managed to resolve this with the resize hack on the height only.

djpetenice on 3 Apr 2018

I'm with you on this. Honestly, the anger and loathing I feel towards this library might just be enough to compel me to write another. I feel like people use this because the name is so "formal" and similar to components supported by react-native-community but... this is truly a terrible library.

wkoutre on 14 Apr 2018

👎2 👍1

Please check out this bug in react native. It seems to happen when using native navigation libraries. Maybe it is somehow related to the problem you are facing
https://github.com/facebook/react-native/commit/a1295e1

krvajal on 15 Apr 2018

Mmm no I don't think so, as I can replicate the issue at will with either a brand new project -- single screen (no navigation whatsoever) -- or on any existing projects whereby I strip out the navigation and have the screen in question render on load by default.

I've spent hours debugging implementations of this library, and though I appreciate it being offered, the actual code just isn't very maintainable. Do I think there are 350 legitimate open issues? Of course not. I just think there needs to be a cleaner lib available, especially one that's actively maintained and so... I will write it! In due time...

wkoutre on 15 Apr 2018

Same issue on IOS

havinhthai on 18 Apr 2018

I was facing this problem using Native base, fixed removing parent Content component, try this by removing the View component, the library itself is entirely made in javascript, so you can test the best layout structure and make a PR with fixes.