Bump expo-server-sdk from 2.3.3 to 3.6.0

[dependabot-preview]

Bumps expo-server-sdk from 2.3.3 to 3.6.0.

Release notes

Sourced from expo-server-sdk's releases.

v3.6.0

New Features

• Support for the accessToken constructor option for projects that have opted in to requiring an access token to send push notifications: expo/expo-server-sdk-node#39

v3.5.1

Bug Fixes

• isExpoPushToken now accepts an argument of any type. It also is statically typed to let TypeScript know the return value indicates whether the argument is a possible Expo push token. (#36)

v3.5.0

New Features

• Export TypeScript types for ExpoPushSuccessTicket, ExpoPushErrorTicket, ExpoPushSuccessReceipt, and ExpoPushErrorReceipt (#33)
• Make private methods actually private in TypeScript (b5dfdc8)

v3.4.0

New Features

• Adds convenience syntax for sending the same push notification message to multiple recipients (4658ede)

v3.3.0

• Added the channelId field type for Android notifications
• Added the status field type for push tickets

v3.2.0

• Added the subtitle field type for iOS notifications
• Fixed the message field type

v3.0.1

This patch version includes support for TypeScript 3.0. It also uses and improves support for TypeScript's "strict" option.

v3.0.0

Version 3.0.0 of the Expo Node SDK comes with support for the new push notification receipts. The README of this repo demonstrates how to use the new API.

Breaking changes

• TypeScript: The SDK uses TypeScript instead of Flow. We've found the TypeScript ecosystem and software to be more stable and the inference to be almost as powerful as Flow's. In the interest of stability, the SDK is now written in TypeScript and the npm package includes the original TS source.
• JavaScript Modules: CommonJS-style require() calls, as opposed to JavaScript import statements, must now explicitly import either the default export or the named Expo export. Any of these work:
  • const { Expo } = require('expo-server-sdk');
  • const { default: Expo } = require('expo-server-sdk');
  • import Expo from 'expo-server-sdk';
  • import { Expo } from 'expo-server-sdk';
  • Does not work: const Expo = require('expo-server-sdk');
• Asynchronous Push Receipts: The sendPushNotificationsAsync method now returns an array of push tickets instead of push receipts. The difference is that tickets specify whether Expo successfully received the notifications, and receipts specify whether Apple or Google did. A push ticket may contain error information (formatted the same as errors in push receipts) or an "id" field with the receipt ID. Sometime later -- usually within a couple minutes but up to half an hour later -- you must retrieve the push receipts with these IDs to learn whether Apple or Google received the notifications. The push receipts will tell you if your push credentials are correctly configured, for example, and also tell you whether you must stop sending notifications to the device that generated that receipt.
• Removed singular sendPushNotificationAsync: The method sendPushNotificationAsync has been removed because we highly recommend using the batch method, sendPushNotificationsAsync, for efficiency. No fundamental functionality was removed but the SDK no longer provides the less efficient convenience method.

New APIs

• Expo client instances have a method named getPushNotificationReceiptsAsync() that accepts an array of receipt IDs and returns a promise that resolves to an object whose keys are the receipt IDs and values are the receipts. If there is no receipt for a given ID, either because it hasn't been generated yet or because it was removed after a day for being stale, the receipt ID will be absent fro the object.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)