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

Layout broken on iPad, app running in Split view #172

Closed
Piidro opened this issue Oct 28, 2019 · 4 comments
Closed

Layout broken on iPad, app running in Split view #172

Piidro opened this issue Oct 28, 2019 · 4 comments

Comments

@Piidro
Copy link
Contributor

Piidro commented Oct 28, 2019

Problem Description:
Hello, seems that this library doesn't work when bulletin is opened when app is not taking 100% of the screen. When running in any split view combinations (1/4, 2/4, 3/4 or 1/3, 2/3 of the screen widths) the bulletin view is displayed as it would take the whole screen estate, therefore part of it is hidden. I have tried both showBulletin(above:animated:completion:) or showBulletin(in:animated:completion) they seem to give same result. I attach an image of the problem to further clarify the issue.

Screenshot 2019-10-28 at 11 21 34

Is there any workaround?

Steps to reproduce:
Run the app, present bulletin board when app size has been reduced with split view. Present bulletin board with either showBulletin(above:animated:completion:) or showBulletin(in:animated:completion)

Environment:

  • Device: iPad 11" Pro, iPad 12.9" Pro
  • OS: iOS 13.0, 13.1, 13.2
  • Version of BulletinBoard: 4.1.0
@arguiot
Copy link

arguiot commented Nov 5, 2019

I also have this problem @alexaubry could you have a look, please?

@Piidro
Copy link
Contributor Author

Piidro commented Feb 7, 2020

I think I managed to fix this issue. To my understanding, this is caused by animation transition in BulletinPresentationAnimationController having incorrect frame for toVC. I opened up a PR #173 with the fix. I don't know if it is the correct way to go though but you who are interested on the subject can take a look!

@arguiot
Copy link

arguiot commented Feb 7, 2020

Great, I’ll take a look and try to install it in my app to see if the issue is fixed.

@alexisakers
Copy link
Owner

The fix was released in 4.1.1, thanks for your patience.

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

No branches or pull requests

3 participants