Skip to content

[APP-15050] Add APIs for device tokens and firebase configs#824

Merged
martha-johnston merged 10 commits intomainfrom
martha/push-notifications
Mar 24, 2026
Merged

[APP-15050] Add APIs for device tokens and firebase configs#824
martha-johnston merged 10 commits intomainfrom
martha/push-notifications

Conversation

@martha-johnston
Copy link
Contributor

https://viam.atlassian.net/browse/APP-15050

This PR adds UploadDevicePushToken, DeleteDevicePushToken, and GetDevicePushTokens so each device token for every user can be stored and accessed in the mongo user collection. It also adds SetFirebaseConfig, GetFirebaseConfig and DeleteFirebaseConfig, so that an app owner can store their firebase config json in a new mongo firebase collection in order to sent push notifications to any app through Viam triggers

@martha-johnston martha-johnston force-pushed the martha/push-notifications branch from bc4b65b to 6d714de Compare March 23, 2026 14:37
@martha-johnston martha-johnston marked this pull request as ready for review March 23, 2026 14:39
Copy link
Member

@clintpurser clintpurser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall LGTM - a few qs, one nit, and one minor thing i might prefer we change. but up to you because its not that serious.

string config_json = 3;
}

message SetFirebaseConfigResponse {}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q - should this perhaps return the ID of the newly set firebase config?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's why we even added GetFirebaseConfigRequest, so you could see what bundle id was associated with your org

}

message GetFirebaseConfigResponse {
string bundle_id = 1;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q - is the app id enough here? is there some unique UUID we might want to return, or some other information?

maybe date set, and by which user? as well as the associated app id?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess, bundle_id should already be unique. so relying on that as the unique identifier might just work.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I think the goal is just knowing what bundle id/app is associated with your org based on what we discussed in the scope

@martha-johnston martha-johnston added ready-for-protos add this when you want protos to compile on every commit safe to test committer is a member of this org labels Mar 24, 2026
@martha-johnston martha-johnston added ready-for-protos add this when you want protos to compile on every commit safe to test committer is a member of this org protos-compiled and removed protos-compiled ready-for-protos add this when you want protos to compile on every commit safe to test committer is a member of this org labels Mar 24, 2026
@martha-johnston martha-johnston merged commit 0ade502 into main Mar 24, 2026
15 of 23 checks passed
@martha-johnston martha-johnston deleted the martha/push-notifications branch March 24, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-protos add this when you want protos to compile on every commit safe to test committer is a member of this org

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants