Merge pull request #7622 from braze-inc/develop

Deploy - July 2, 2024

.github/PULL_REQUEST_TEMPLATE

@@ -0,0 +1,38 @@
+<!--
+Thank you for contributing to Braze Docs! Read comments like this one for help filling out your Pull Request (PR). For more information about contributing to Braze Docs, see:
+braze.com/docs/contributing/.
+-->
+
+### Summary
+<!-- In one or two sentences, describe your changes. -->
+My PR...
+
+### Related PRs, issues, or features (optional)
+<!--
+For related GitHub issues and features, add "Fixes #ISSUE_NUMBER".
+For Jira tickets, add the ticket number and a link to the ticket, like: [BD-NUMBER](LINK).
+-->
+- N/A
+
+### Feature release date (optional)
+<!-- If this PR is related to an upcoming Braze feature, add the date below, like: 15 May 2024. -->
+- N/A
+
+### Contributor checklist
+<!-- After you've filled out the previous sections, select "Create Draft Pull Request", then review your PR before filling out the following checklist. -->
+- [ ] I confirm that my PR meets the following:
+    - I signed the [Contribution License Agreement (CLA)](https://www.braze.com/docs/cla).
+    - My style and voice follows the [Braze Style Guide](https://docs.google.com/document/u/2/d/e/2PACX-1vTluyDFO3ZEV7V6VvhXE4As_hSFwmnFFdU9g6_TrAYTgH1QmbRoEDDdn5GzKAB9vdBbIdyiFdoaJcNk/pub).
+    - My content contains correct spelling and grammar.
+    - All links are working correctly.
+    - If I renamed or moved a file or directory, I set up [URL redirects](https://www.braze.com/docs/contributing/content_management/redirecting_urls) for each file.
+    - If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see [Updating an image](https://www.braze.com/docs/contributing/content_management/images/#updating-an-image)).
+    - If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.
+
+### Submitting for review
+
+If your PR meets the above requirements, select **Ready for review**, then add a reviewer:
+- **Non-Braze contributors:** Add `braze-inc/docs-team` as the reviewer.
+- **Braze employees:** Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the [tech writer assigned to your specific vertical](https://confluence.braze.com/pages/viewpage.action?pageId=75039896). If you're not sure which tech writer to add, you can add `braze-inc/docs-team` instead. 
+
+Thanks for contributing! We look forward to reading your work.

_docs/_contributing/yaml_front_matter/metadata.md

@@ -147,15 +147,15 @@ hide_toc: true
 
 ### Hide heading from table of contents
 
-The `toc_headers` key is used to hide all headings of the same level from the in-page table of contents (TOC) on the right side of the page. This key accepts the following string values.
+By default, the table of contents (TOC) displays all heading levels. To show only specific heading levels, use the `toc_headers` key to explicitly list the desired levels. Any heading levels not listed will be hidden from the TOC.
+
+This key accepts the following string values:
 
 - `h1`
 - `h2`
 - `h3`
 - `h4`
 
-`toc_headers` will hide all headings matching its assigned value; it cannot be used to hide specific headings from the TOC.
-
 {% tabs local %}
 {% tab usage example %}
 ```markdown

_docs/_developer_guide/platform_integration_guides/react_native/push_notifications.md

@@ -254,7 +254,9 @@ If you want to use an additional Firebase Messaging Service (FMS), you can speci
 }
 ```
 
-## Enabling rich push notifications for iOS
+## Configuring app extensions with Expo
+
+### Enabling rich push notifications for iOS
 
 {% alert tip %}
 Rich push notifications are available for Android by default.
@@ -278,7 +280,9 @@ To enable rich push notifications on iOS using Expo, configure the `enableBrazeI
 }
 ```
 
-## Enabling push stories for iOS
+Lastly, add the bundle identifier for this app extension to your project's credentials configuration: `<your-app-bundle-id>.BrazeExpoRichPush`. For further details on this process, refer to [Using app extensions with Expo Application Services](#app-extensions).
+
+### Enabling push stories for iOS
 
 {% alert tip %}
 Push stories are available for Android by default.
@@ -305,6 +309,18 @@ Next, configure the `enableBrazeIosPushStories` property to `true` and assign yo
 }
 ```
 
+Lastly, add the bundle identifier for this app extension to your project's credentials configuration: `<your-app-bundle-id>.BrazeExpoPushStories`. For further details on this process, refer to [Using app extensions with Expo Application Services](#app-extensions).
+
+{% alert warning %}
+If you are using Push Stories with Expo Application Services, be sure to use the `EXPO_NO_CAPABILITY_SYNC=1` flag when running `eas build`. There is a known issue in the command line which removes the App Groups capability from your extension's provisioning profile.
+{% endalert %}
+
+### Using app extensions with Expo Application Services {#app-extensions}
+
+If you are using Expo Application Services (EAS) and have enabled `enableBrazeIosRichPush` or `enableBrazeIosPushStories`, you will need to declare the corresponding bundle identifiers for each app extension in your project. There are multiple ways you can approach this step, depending on how your project is configured to manage code signing with EAS.
+
+One approach is to use the `appExtensions` configuration in your `app.json` file by following Expo's [app extensions documentation](https://docs.expo.dev/build-reference/app-extensions/). Alternatively, you can set up the `multitarget` setting in your `credentials.json` file by following Expo's [local credentials documentation](https://docs.expo.dev/app-signing/local-credentials/#multi-target-project).
+
 [1]: {% image_buster /assets/img/react-native/push-notification-test.png %} "Push Campaign Test"
 [2]: https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/b2-rich-push-notifications/
 [3]: https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/b3-push-stories/

_docs/_developer_guide/platform_integration_guides/swift/analytics/tracking_sessions.md

@@ -71,7 +71,7 @@ App-specific details will display only if the user has used more than one app.
 
 ## Subscribing to session updates
 
-To listen to session updates, use the [`subscribeToSessionUpdates(_:)`][1] method:
+To listen to session updates, use the [`subscribeToSessionUpdates(_:)`][1] method. Session start and end events will only be logged when the app is running in the foreground. If you register a callback to session end events and the app is backgrounded, the callback will fire when the app is foregrounded again. Session duration, however, is still measured as the time from app open or foregrounding until app closing or backgrounding.
 
 {% tabs %}
 {% tab swift %}

_docs/_developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes.md

@@ -115,7 +115,7 @@ braze.getUser().setCustomUserAttribute(YOUR_ATTRIBUTE_KEY_STRING, YOUR_ARRAY_OF_
 braze.getUser().addToCustomAttributeArray(YOUR_ATTRIBUTE_KEY_STRING, "new string");
 
 // Removing an element from a custom attribute with an array value
-braze.getUser().removeFromCustomAttributeArray("custom_attribute_array_test", "value to be removed");
+braze.getUser().removeFromCustomAttributeArray(YOUR_ATTRIBUTE_KEY_STRING, "value to be removed");
 ```
 
 ### Unsetting a custom attribute

_docs/_developer_guide/platform_integration_guides/web/analytics/tracking_sessions.md

@@ -34,7 +34,7 @@ If you have set a session timeout, then the session semantics all extend to that
 
 To detect sessions via your user, find your user on the dashboard and navigate to **App Usage** on the user profile. You can confirm that session tracking is working by checking that the session metric increases when you would expect it to.
 
-![A user profile component showing how many sessions have occurred, when the app was first used, and when it was last used.][session_tracking_7]
+![A user profile component showing how many sessions have occurred, when the app was first used, and when it was last used.][session_tracking_7]{: style="max-width:50%"}
 
 [session_tracking_1]: {{ site.baseurl }}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview/#customizing-braze-on-startup
 [session_tracking_3]: {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-2-configure-the-braze-sdk-in-appboyxml