Skip to content
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: flexible notification request handling #40

Merged
merged 14 commits into from Feb 25, 2023
12 changes: 12 additions & 0 deletions README.md
Expand Up @@ -124,6 +124,12 @@ The `customerio-expo-plugin` supports the following configuration options. In mo
<td><code>undefined</code></td>
<td>Set the path to your <code>google-services.json</code> file.</td>
</tr>
<tr>
<td><code>android.setHighPriorityPushHandler</code></td>
<td>boolean</td>
<td><code>undefined</code></td>
<td>This is optional, if you choose to use a 3rd party plugin to handle notification permissions, but want our SDK to handle the notifications, this sets `io.customer.messagingpush.CustomerIOFirebaseMessagingService` as high priority.</td>
</tr>
xtreem88 marked this conversation as resolved.
Show resolved Hide resolved
<tr>
<td><code>ios.pushNotification</code></td>
<td>object</td>
Expand All @@ -148,6 +154,12 @@ The `customerio-expo-plugin` supports the following configuration options. In mo
<td><code>undefined</code></td>
<td>This is optional, it allows the plugin to work with static libraries. Options are <code>static</code> and <code>dynamic</code></td>
</tr>
<tr>
<td style="white-space:nowrap;"><code>ios.disableNotificationRegistration</code></td>
<td>boolean</td>
<td><code>undefined</code></td>
<td>This is optional, it removes the the `registerPushNotification` handler and allows you to use any 3rd party plugin to handle the permission request </td>
</tr>
</tbody>
</table>

Expand Down