-
Notifications
You must be signed in to change notification settings - Fork 9
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 Untracked] Clarify subscribeToSessionUpdates behavior #7473
Conversation
@@ -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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add that the time attached to the session end event corresponds to the last time the app was closed/backgrounded?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, you mean the duration of the session, right? The time of the event will still be the time that the app is foregrounded again, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, sorry that's right. The time for both events will be at foreground, but it's the duration of the session that this would refer to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hey @jacksonemiller , let me know when this one's ready for a tech writer review! |
Hey @jacksonemiller : Just checking in about the status of this PR. Thanks! |
@josh-mccrowell-braze Hey, sorry for leaving this open for so long with no updates. We had a team discussion about it last week. I'll update it today and then get reviews from my team before opening it up for yalls review. |
@jacksonemiller No worries! Just wanted to make sure it doesn't go stale. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This SGTM to describe today's behavior. If we do make an update in the future, we can just update this again
@internetisaiah This is now ready for a review, my team has okay-ed it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this!
Pull Request/Issue Resolution
Description of Change:
Follow up to this GitHub issue.
Is this change associated with a Braze feature/product release?
✔️ Pull Request Checklist
assets
>js
>broken_redirect_list.js
⭐ Helpful Wiki Shortcuts
❗ ATTN: For PR Reviewers
❗ ATTN: Internal Reviewing Chart
Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @internetisaiah for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.
Quality Infrastructure
Platform Infrastructure
Datalake
SDKs
Currents
Technology partners
Channels
In-App Messages
Channels
Frontend Infrastructure & Experience (FIX)
Core Objects
Core Messaging
Messaging Experience
Message Components
Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
SMS
User Targeting
Reporting