From 682bdb478e6b28f400ea493ba96fc5895f52c00e Mon Sep 17 00:00:00 2001 From: david Date: Thu, 30 May 2024 14:31:41 -0400 Subject: [PATCH 1/3] fcm docs --- .../android/integration/standard_integration.md | 4 ++-- .../android/migrating_to_firebase_cloud_messaging.md | 12 ++++++++++-- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md index bd109e81a5d..81e3321e29d 100644 --- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md +++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md @@ -86,8 +86,8 @@ Choose **JSON**, then select **Create**. Be sure to remember where you downloade ![The form for creating a private key with "JSON" selected.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create.png %}){: style="max-width:65%;"} -{% alert warning %} -Private keys could pose a security risk if compromised. Store your JSON credentials in a secure location—you'll delete your key after you upload it to Braze. +{% alert info %} +If your service account was created within a different GCP project ID than the Firebase Cloud Messaging project, you will need to modify the JSON file's `project_id` field. {% endalert %} ### Step 6: Upload your JSON credentials to Braze diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md index bce7b52d019..2e7d438c0cf 100644 --- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md +++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md @@ -107,8 +107,8 @@ Choose **JSON**, then select **Create**. ![The form for creating a private key with "JSON" selected.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create.png %}){: style="max-width:65%;"} -{% alert warning %} -Private keys could pose a security risk if compromised. Store your JSON credentials in a secure location for now—you'll delete your key after you upload it to Braze. +{% alert info %} +If your service account was created within a different GCP project ID than the Firebase Cloud Messaging project, you will need to modify the JSON file's `project_id` field. {% endalert %} ### Step 7: Upload your JSON credentials to Braze @@ -153,6 +153,10 @@ If you delete your new credentials, you cannot restore them later. You'll need t Your new credentials start working as soon as you upload them to Braze. To test them, select **Test Credentials**. If you get an error, you can always [revert your credentials](#reverting-your-credentials). +### Do I need to also migrate development or unused apps? + +Unused or development apps will also show a warning banner. You can either upload new credentials to these apps, or delete the app if they are unused. Be careful not to delete apps that are still in use by your other team members. + ### Where can I check error messages? You can review push notification errors in your [message activity log]({{site.baseurl}}/user_guide/administrative/app_settings/message_activity_log_tab/). @@ -172,3 +176,7 @@ You'll continue to see this warning message if there's at least one Android app ### After migrating, how long until I send push notifications again? After migrating, you can start sending push notifications using your new credentials right away. + +### What if my Service Account was created in a different project than my Firebase Messaging Project? + +If your service account's project ID is different than your Firebase Cloud Messaging project or Sender ID, you will need to modify your service account JSON file and change the `project_id` field accordingly. From fc72d78e57d5448a61aa38edec902ae44a4b77a6 Mon Sep 17 00:00:00 2001 From: isaiah robinson <95643215+internetisaiah@users.noreply.github.com> Date: Fri, 31 May 2024 14:43:59 -0700 Subject: [PATCH 2/3] Update standard_integration.md --- .../android/integration/standard_integration.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md index 81e3321e29d..8df08cda445 100644 --- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md +++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration.md @@ -82,12 +82,14 @@ Select **Add Key** > **Create new key**. ![The selected service account with the "Add Key" menu open.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create-new-key.png %}) -Choose **JSON**, then select **Create**. Be sure to remember where you downloaded the key—you'll need it in the next step. +Choose **JSON**, then select **Create**. If you created your service account using a different Google Cloud project ID than your FCM project ID, you'll need to manually update the value assigned to the `project_id` in your JSON file. + +Be sure to remember where you downloaded the key—you'll need it in the next step. ![The form for creating a private key with "JSON" selected.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create.png %}){: style="max-width:65%;"} -{% alert info %} -If your service account was created within a different GCP project ID than the Firebase Cloud Messaging project, you will need to modify the JSON file's `project_id` field. +{% alert warning %} +Private keys could pose a security risk if compromised. Store your JSON credentials in a secure location for now—you'll delete your key after you upload it to Braze. {% endalert %} ### Step 6: Upload your JSON credentials to Braze From 76a6560366c685af69ae3a1ad2b27a1125b13fd2 Mon Sep 17 00:00:00 2001 From: isaiah robinson <95643215+internetisaiah@users.noreply.github.com> Date: Fri, 31 May 2024 14:52:00 -0700 Subject: [PATCH 3/3] Update migrating_to_firebase_cloud_messaging.md --- .../migrating_to_firebase_cloud_messaging.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md index 2e7d438c0cf..6b51da1ddf5 100644 --- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md +++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md @@ -103,12 +103,14 @@ Creating a new key will not remove your legacy ones. If you accidentally delete ![The selected service account with the "Add Key" menu open.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create-new-key.png %}) -Choose **JSON**, then select **Create**. +Choose **JSON**, then select **Create**. If you created your service account using a different Google Cloud project ID than your FCM project ID, you'll need to manually update the value assigned to the `project_id` in your JSON file. + +Be sure to remember where you downloaded the key—you'll need it in the next step. ![The form for creating a private key with "JSON" selected.]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create.png %}){: style="max-width:65%;"} -{% alert info %} -If your service account was created within a different GCP project ID than the Firebase Cloud Messaging project, you will need to modify the JSON file's `project_id` field. +{% alert warning %} +Private keys could pose a security risk if compromised. Store your JSON credentials in a secure location for now—you'll delete your key after you upload it to Braze. {% endalert %} ### Step 7: Upload your JSON credentials to Braze @@ -153,9 +155,9 @@ If you delete your new credentials, you cannot restore them later. You'll need t Your new credentials start working as soon as you upload them to Braze. To test them, select **Test Credentials**. If you get an error, you can always [revert your credentials](#reverting-your-credentials). -### Do I need to also migrate development or unused apps? +### Do I need to migrate to FCM for my unused apps or development apps? -Unused or development apps will also show a warning banner. You can either upload new credentials to these apps, or delete the app if they are unused. Be careful not to delete apps that are still in use by your other team members. +No. However, your unused apps and development apps will continue to show a warning message asking you to migrate. To remove this message, you can either upload new credentials, or delete these apps from your workspace. If you choose to delete these apps, be sure to check with your team first in case someone is using them. ### Where can I check error messages? @@ -177,6 +179,6 @@ You'll continue to see this warning message if there's at least one Android app After migrating, you can start sending push notifications using your new credentials right away. -### What if my Service Account was created in a different project than my Firebase Messaging Project? +### What if I created my service account using a different project than my FCM project? -If your service account's project ID is different than your Firebase Cloud Messaging project or Sender ID, you will need to modify your service account JSON file and change the `project_id` field accordingly. +If you created your service account using a different Google Cloud project ID than your FCM project ID, you'll need to manually update the value assigned to the `project_id` in your JSON file after you [create a new one](#step-6-generate-json-credentials).