-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(share_plus): Throw error if sharePositionOrigin not in sourceView #1038
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
fix(share_plus): Throw error if sharePositionOrigin not in sourceView #1038
Conversation
Resolves #951 |
Resolves #870 |
The sharePositionOrigin must be in the coordinate space of sourceView. See https://developer.apple.com/documentation/uikit/uipopoverpresentationcontroller/1622324-sourcerect
482b288
to
d4ae457
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This will help bring clarity to this issue that seems to affect so many people.
Since sharePositionOrigin
is not mandatory for iPhones, does it keep working as well for those devices when the param is not provided?
I now made sure, that it raises a
|
# Conflicts: # packages/share_plus/share_plus/CHANGELOG.md # packages/share_plus/share_plus/pubspec.yaml
736ea84
to
7ecda36
Compare
7ecda36
to
fa356dc
Compare
# Conflicts: # packages/share_plus/share_plus/CHANGELOG.md # packages/share_plus/share_plus/ios/Classes/FLTSharePlusPlugin.m
Can this be merged @miquelbeltran ? |
on it |
Good catch and thank you @miquelbeltran :) 👍 |
released under 4.3.0, thanks to you! I ran this on my mac on both iphone and ipad simulators |
(iPad and maybe Mac): The sharePositionOrigin must be in the coordinate space of sourceView. See https://developer.apple.com/documentation/uikit/uipopoverpresentationcontroller/1622324-sourcerect, else
[LayoutConstraints] Unable to simultaneously satisfy constraints.
appears.Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process.
pubspec.yaml
andCHANGELOG.md
.///
).flutter analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?