cordova-plugin-openwith
This plugin for Apache Cordova registers your app to handle certain types of files.
Overview
This is a bit modified version of cordova-plugin-openwith by Jean-Christophe Hoelt for iOS.
What's different:
- Works with several types of shared data (UTIs). Currently, URLs, text and images are supported. If you would like to remove any of these types, feel free to edit ShareExtension-Info.plist (NSExtensionActivationRule section) after plugin's installation
- Support of sharing several photos at once is supported. By default, the maximum number is 10, but this can be easily edited in the plugin's .plist file
- Does not show native UI with "Post" option. Having two-step share (enter sharing message and then pick the receiver in the Cordova app) might be a bad user experience, so this plugin opens Cordova application immediately and passes the shared data to it. Thereby, you are expected to implement sharing UI in your Cordova app.
You'd like your app to be listed in the Send to... section for certain types of files, on both Android and iOS? This is THE plugin! No need to meddle into Android's manifests and iOS's plist files, it's (almost) all managed for you by a no brainer one liner installation command.
Table of Contents
iOS
On iOS, there are many ways apps can communicate. This plugin uses a Share Extension. This is a particular type of App Extension which intent is, as Apple puts it: "to post to a sharing website or share content with others".
A share extension can be used to share any type of content. You have to define which you want to support using an Universal Type Identifier (or UTI). For a full list of what your options are, please check Apple's System-Declared UTI.
As with all extensions, the flow of events is expected to be handled by a small app, external to your Cordova App but bundled with it. When installing the plugin, we will add a new target called ShareExtension to your XCode project which implements this Extension App. The Extension and the Cordova App live in different processes and can only communicate with each other using inter-app communication methods.
When a user posts some content using the Share Extension, the content will be stored in a Shared User-Preferences Container. To enable this, the Cordova App and Share Extension should define a group and add both the app and extension to it.
Once the data is in place in the Shared User-Preferences Container, the Share Extension will open the Cordova App by calling a Custom URL Scheme. This seems a little borderline as Apple tries hard to prevent this from being possible, but brave iOS developers always find solutions... So as for now there is one and it seems like people got their app pass the review process with it. At the moment of writing, this method is still working on iOS 11.1. The recommended solution is be to implement the posting logic in the Share Extension, but this doesn't play well with Cordova Apps architecture...
On the Cordova App side, the plugin checks listens for app start or resume events. When this happens, it looks into the Shared User-Preferences Container for any content to share and report it to the javascript application.
Installation
Here's the promised one liner:
cordova plugin add cordova-plugin-openwith \
--variable IOS_URL_SCHEME=cordovaopenwithdemo
variable | example | notes |
---|---|---|
DISPLAY_NAME |
My App Name | If you want to use a different name than your project name |
IOS_BUNDLE_IDENTIFIER |
com.domain.app | Your app bundle identifier |
IOS_URL_SCHEME |
uniquelonglowercase | Any random long string of lowercase alphabetical characters |
It shouldn't be too hard. But just in case, Jean-Christophe Hoelt posted a screencast of it.
Usage
document; { // Increase verbosity if you need more logs //cordova.openwith.setVerbosity(cordova.openwith.DEBUG); // Initialize the plugin cordovaopenwith; { console; } { console; } // Define your file handler cordovaopenwith; { console; console; // description to the sharing, for instance title of the page when shared URL from Safari for var i = 0; i < intentitemslength; ++i var item = intentitemsi; console; // UTI. possible values: public.url, public.text or public.image console; // Mime type. For example: "image/jpeg" console; // shared data. For URLs and text - actually the shared URL or text. For image - its base64 string representation. console; // text to share alongside the item. as we don't allow user to enter text in native UI, in most cases this will be empty. However for sharing pages from Safari this might contain the title of the shared page. console; // suggested name of the image. For instance: "IMG_0404.JPG" console; // some optional additional info // Read file with Cordova’s file plugin if itemfileUrl }}
API
cordova.openwith.setVerbosity(level)
Change the verbosity level of the plugin.
level
can be set to:
cordova.openwith.DEBUG
for maximal verbosity, log everything.cordova.openwith.INFO
for the default verbosity, log interesting stuff only.cordova.openwith.WARN
for low verbosity, log only warnings and errors.cordova.openwith.ERROR
for minimal verbosity, log only errors.
cordova.openwith.addHandler(handlerFunction)
Add an handler function, that will get notified when a file is received.
Handler function
The signature for the handler function is function handlerFunction(intent)
. See below for what an intent is.
Intent
intent
describe the operation to perform, toghether with the associated data. It has the following fields:
text
: text to share alongside the item, in most cases this will be an empty string.items
: an array containing one or more data descriptor.
Data descriptor
A data descriptor describe one file. It is a javascript object with the following fields:
uti
: Unique Type Identifier. possible values: public.url, public.text or public.imagetype
: Mime type. For example: "image/jpeg"text
: test description of the share, generally emptyname
: suggested file nameutis
: list of UTIs the file belongs to.
Contribute
Contributions in the form of GitHub pull requests are welcome. Please adhere to the following guidelines:
- Before embarking on a significant change, please create an issue to discuss the proposed change and ensure that it is likely to be merged.
- Follow the coding conventions used throughout the project. Many conventions are enforced using eslint and pmd. Run
npm t
to make sure of that. - Any contributions must be licensed under the MIT license.