Publishing Plugins

Publish a plugin

Run pebble publish in the plugin's project, the same way as for an app (see Publishing an App):

$ pebble login
$ pebble publish

The first time, the command creates the plugin's listing: it asks for a name, a description and a plugin category. Plugins have no screenshots. Pass --icon-small and --icon-large, or let the appstore generate a line icon from the description. Later runs upload a new release to the same listing.

Sign users in with OAuth

A plugin that calls an API on the user's behalf can sign them in to it without shipping your client secret in the .pbw. The appstore keeps the secret and runs the token exchange; the plugin only receives the user's tokens.

1. Declare a connector in package.json, under pebble.plugin, with a slug of your choice:

   "oauth": { "my-service": {} }
   

2. Register an OAuth app with the service and set its redirect URI to:

   https://appstore-api.repebble.com/api/oauth/broker/callback
   

3. Give the appstore the service's settings. pebble publish offers to do this after uploading; to do it later, or to change them:

   $ pebble oauth-connector set --slug my-service
   

   It asks for the authorization URL, token URL, scopes, client ID and client secret. The same settings are on the plugin's OAuth connector page in the Developer Dashboard.

4. In the plugin, start the sign-in and keep the tokens in secure storage:

   var tokens = await Pebble.oauth.authorize('my-service');
   await Pebble.secureStorage.setItem('access_token', tokens.access_token);
   

   tokens has access_token and, when the service issues a refresh token, broker_refresh. When the access token expires, pass broker_refresh to Pebble.oauth.refresh('my-service', brokerRefresh) for a new one.

authorize also works on the emulator: it opens the service's sign-in page in your browser, signed in as your pebble login account. The connector must be set up first.