-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(share_plus): Present Share Sheet on the top ViewController #254
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): Present Share Sheet on the top ViewController #254
Conversation
Thanks @searchy2 ! Can you update also the pubspec.yaml and bump the version number to |
Bumped! |
I tested this and seems to work, however CI is complaining with the following error:
Could you solve this formatting issue? then I will merge and release. |
I'll probably need your help with the formatting.
Any idea what's wrong? Also, does the format tool format iOS code? |
@miquelbeltran Can you help me fix the formatting? |
can you also please merge with |
- Present share sheet on the currently visible view controller.
cc5790b
to
1dafbb2
Compare
Done! |
Perfect, now it seems we have a formatting issue, could you run |
That didn't work and threw an exception. I'll need you to run it for me. |
What's the exception? if you want me to run it for you, you need to give me access to https://github.com/searchy2/plus_plugins/tree/share_ios_present_fix |
I'm running into the same issue as before:
I've invited you to the repo, thank you for your help here! |
@searchy2 can you enable “Allow edits by maintainers”? I just checked out your PR and there were still unmerged changes from |
It's checked, just updated from main again. |
Can you run |
going to unblock this, may need to create a new PR |
continuing in #307 |
Description
Update iOS share target to present on the top ViewController. This fixes "Unable to present" errors when the app is already presenting such as in an add to app scenario.
Related Issues
#251
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. Updating the
pubspec.yaml
and changelogs is not required.No tests need to be updated.
///
).No doc changes needed.
flutter analyze
) does not report any problems on my PR.warning - The path F:\Development\FlutterPlusPlugins\packages\share_plus is not posix - example\pubspec.yaml:9:11 - path_not_posix
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?