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

[SDK-4833] Remove GCM references #7387

Merged
merged 2 commits into from
May 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -195,19 +195,7 @@ Braze.configure(this, brazeConfig)
If you'd like manually register FCM tokens instead, you can call [`Braze.setRegisteredPushToken()`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze/-braze/registered-push-token.html) inside your app's [`onCreate()`](https://developer.android.com/reference/android/app/Application.html#onCreate()) method.
{% endalert %}

### Step 8: Remove unnecessary permissions

With your new push integration set up, the following permissions are no longer needed by Braze in your project's `braze.xml` file:

```xml
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
<permission android:name="YOUR-APPLICATION-PACKAGE-NAME.permission.C2D_MESSAGE" android:protectionLevel="signature"/>
<uses-permission android:name="YOUR-APPLICATION-PACKAGE-NAME.permission.C2D_MESSAGE" />
```

### Step 9: Remove automatic requests in your application class
### Step 8: Remove automatic requests in your application class

To prevent Braze from triggering unnecessary network requests everytime you send silent push notifications, remove any automatic network requests configured in your `Application` class's `onCreate()` method. For more information see, [Android Developer Reference: Application](https://developer.android.com/reference/android/app/Application).

Expand Down
2 changes: 1 addition & 1 deletion _docs/_help/help_articles/push/push_error_codes.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Check out these common error messages for push messaging:
{% tabs %}
{% tab Android %}
### Push bounced: MismatchSenderId
`MismatchSenderId` indicates an authentication failure. Google Cloud Messaging (GCM) authenticates with a couple key pieces of data: senderID and FCM API key. These should both be validated for accuracy. For more information see the [Android documentation](https://firebase.google.com/docs/cloud-messaging/http-server-ref#error-codes) about this issue.
`MismatchSenderId` indicates an authentication failure. Firebase Cloud Messaging (FCM) authenticates with a couple key pieces of data: senderID and FCM API key. These should both be validated for accuracy. For more information see the [Android documentation](https://firebase.google.com/docs/cloud-messaging/http-server-ref#error-codes) about this issue.

Common failures may include:
- Bad [senderID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
Expand Down
1 change: 0 additions & 1 deletion _includes/image_specs.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,6 @@ We recommend the following payload sizes:
| --- | --- |
| iOS (pre-iOS 8) | 0.256 KB |
| iOS (post-iOS 8) | 2 KB |
| Android (GCM) | 2 KB |
| Android (FCM) | 4 KB |
{: .reset-td-br-1 .reset-td-br-2}

Expand Down