Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry for the ugly English.
I tried to fix the issue #741 .
This issue can happen frequently, so consider merging.
Cause
There are two cause for this issue:
In changeCurrentIndexProgressive in didSelectItemAt, OldCell is nil, because OldCell is off the screen.
cellForItemAt is called when an OldCell outside the screen enters the screen with moveTo.
However, the currentIndex has not been updated, the OldCell is determined to be a NewCell.
Amendment policy
The fix was applied only inside the buttonBar related sources. Because of the following two reasons
We also considered modifying PagerTabStripViewController, but the scope of influence is too wide.
changeCurrentIndexProgressive exists only in buttonBar.