-
Notifications
You must be signed in to change notification settings - Fork 658
Introduces a SessionDataService which is bound to by clients in each … #5397
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
Conversation
…process for creating and pushing session ids.
Generated by 🚫 Danger |
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected Products
Test Logs |
|
|
||
| <application> | ||
| <service | ||
| android:name=".SessionDataService" |
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.
Will this . carry on to the app when the manifests get merged? Will this have a different name for every app depending on it's app id? Or will it always be ...firebase-sessions.SessionDataService ?
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.
I still see it show up as com.google.firebase.sessions.SessionDataService in stack traces when running in an app, but I'll make this fully qualified like the other one.
mrober
left a comment
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 knowing this is still for debugging
Introduces a new SessionDataService that is bound to by each process and used to deliver session-ids.