React-native-snap-carousel: Maximum update depth exceeded!

Created on 1 Oct 2019  路  10Comments  路  Source: meliorence/react-native-snap-carousel

Bug report!

Have you followed the required steps before opening a bug report?

(Check the step you've followed - put an x character between the square brackets ([]).)

Have you made sure that it wasn't a React Native bug?

I think, it's about react native snap carousel library.

Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?

I tried on IOS only.

Is the bug reproductible in a production environment (not a debug one)?

I didn't try on production env.

Environment

(Write your answer here.)

Expected Behavior

(Write what you thought would happen.)

Actual Behavior

When I try to build with last version of react native (0.60.1) the app crashed because of that error!

(Write what happened. Add screencasts/screenshots!)

Reproducible Demo

(Paste the link to a Snack example in which the issue can be reproduced. Please follow the guidelines for providing a Minimal, Complete, and Verifiable example.)

Steps to Reproduce

(Write your steps so that anyone can reproduce the issue in the Snack demo you provided.)

1.
2.
3.

bug

All 10 comments

image
image

The problem appear only with v.3.8.1.
v.3.8.0 working well!

Hi @orcunorcun,

This is some serious issue indeed! It clearly has to do with the migration from componentWillReceiveProps to componentDidUpdate, but I don't understand why the former didn't trigger any error while the latter does...

I have the same crash when I try to render a list with the props loop={true} and loopClonesPerSide={0}. If I put loopClonesPerSide={1} it works.

I am facing the same problem with v3.8.0, and even if i add loopClonesPerSide={1} as @nromptea42 says, still same error nothing changes

+1

Also experiencing this and to add some color, I haven't changed my data or functions in anyway that would yield an infinite loop. No setStates anyway that would interfere and cause this. It also came out of nowhere and have proven that it only breaks like this when loop={true}.

Any update on this? I just updated from 3.8.0 to 3.8.4 and, with no other changes, it crashes with the aforementioned error. I've turned loop to false for now, but ideally would like that value to be true.

happens for me too, I turned off loop props it worked, but I need the loop prop to be true :(

It may be a matter of data

Was this page helpful?
0 / 5 - 0 ratings

Related issues

AndrePech picture AndrePech  路  4Comments

KarlosQ picture KarlosQ  路  4Comments

siderakis picture siderakis  路  3Comments

Dr1992 picture Dr1992  路  4Comments

ajonno picture ajonno  路  4Comments