-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat: ability to set Icon in Share dialog #3049
Comments
That is really automatic, that icon means you are sharing text, if you share a http/https url you'll see the safari icon first and then the favicon of the website you are sharing, and if you share a file url like the one you get from the camera plugin when you take a picture a preview of the image appears. |
@jcesarmobile Okay. Docs currently state: |
Yeah, that sentence is wrong, I've removed it in #3051 In ShareOptions section you can see the ? on all params, that means they are optional. It also says |
It also seems that by not setting text, then when sharing by Gmail/Mail apps the the email subject is not populated. So that lets me choose between:
I see other apps with sharing links that seem to have both a custom icon and populated email subjects. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out. |
Feature Request
Describe the Feature Request
The interface that opens from the Share plugin
Share.share(...)
on iOS appears to have a default icon and there's no way to configure it.This feature request is to update the plugin such that the default Icon doesn't appear.
Platform Support Requested
I've specifically noticed the issue on iOS and not on the Android devices and emulators that we use. However, I suppose it's Android has the same issue and we just haven't seen it.
Describe Preferred Solution
Default to the app icon
Describe Alternatives
Share.share(...)
The text was updated successfully, but these errors were encountered: