Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

func moveToViewController(at index: Int) is invalid when you load first time #478

Open
zhuifengzhe opened this issue Oct 27, 2017 · 4 comments

Comments

@zhuifengzhe
Copy link

Before submitting issues ...

  • Make sure you are using XLPagerTabStrip latest release or master branch version.
  • Make sure your Xcode version is the latest stable one.
  • Check if the issue was already reported or fixed. We add labels to each issue in order to easily find related issues. If you found a match add a brief comment "I have the same problem" or "+1".
  • Please do not use the issue tracker for personal support requests. Stack Overflow is a better place for that where a wider community can help you!

When submitting issues, please provide the following information to help maintainers to fix the problem faster:

  • Environment: XLPagerTabStrip, Xcode and iOS version you are using.
  • In case of reporting errors, provide Xcode console output of stack trace or code compilation error.
  • Any other additional detail such as example code that you think it would be useful to understand, reproduce and solve the problem.
@calda
Copy link

calda commented Oct 30, 2017

Also seeing this problem. Had to downgrade to 7.0.

@calda
Copy link

calda commented Oct 30, 2017

The root issue seems to be that canMoveTo(index:) is now returning false in instances where it returned true in 7.0 (ex: SegmentedPagerTabStripViewController.viewDidLoad)

@mouness2020
Copy link

temporary solution

let when = DispatchTime.now() + 0.1 DispatchQueue.main.asyncAfter(deadline: when) { self.moveToViewController(at: self.objectsVC.count - 1, animated: false) }

@bivant
Copy link

bivant commented May 30, 2019

Looks like the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants