-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Invite API - how to get sender information on receiver's side #29
Comments
I don't believe that Google provides this but it is possible to use the invitation ID as a unique identifier for each invitation, store data on your site upon sending, and then retrieve the data from your site when the recipient gets the invitation. I'll forward your feature request to the app invites team. If you're using profile data, please be mindful of the developer policies for the data you're using.
The sender of the invitation determines the text of the final invitation that gets sent so the "invitation sender" is in effect not verified - invitations could also be sent via SMS and there's no verification of the sender because the sender has control over the message. As such, the best signal that you have to work with is data that you have verified and associated to the invitation ID: if the invitation itself is spoofed, the ID lookup would fail / the invitation would not resolve. |
If you really want to get the sender information, you could just store that as part of your deep link data. Then parse it back out on the receiver's side. You can put anything you want in the deep link! |
Closing for lack of activity. |
Is there a way to get sender information (name, picture etc.) from an invitation on receiver's side as it is visually represented on https://developers.google.com/app-invites/android/ ?
Also, is there a way for us to know if for example sender is putting fake email in invitation?
I found all this this very confusing and cannot find any specific answer on official site. Thank you for your help in advance.
The text was updated successfully, but these errors were encountered: