Skip to content
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

Handling Result #5

Open
jayvhaile opened this issue Dec 16, 2019 · 3 comments
Open

Handling Result #5

jayvhaile opened this issue Dec 16, 2019 · 3 comments

Comments

@jayvhaile
Copy link

More information is needed than just result ok, at least the telegram id of the user, otherwise, it is not useful at all

@lynnporu
Copy link

I encountered the same problem. Imagine the following algorithm:

  1. Android app requires authorization;
  2. User logs in via Telegram and enters all the data;
  3. Bot gets an update that I process and sign up the user for my service at backend;
  4. Android app gets just "ok", no info about user logged in, no way to get some data from my backend.

@grishka
Copy link
Contributor

grishka commented Jan 31, 2020

Even though I no longer work at Telegram, I'd like to tell you that this isn't how this works. This isn't just oauth-style thing for logging users in with their Telegram accounts. This is Telegram Passport, for a very limited set of primarily financial services that do KYC checks and stuff like that. I don't think you're supposed to sign users in with this.

@lynnporu
Copy link

lynnporu commented Feb 1, 2020

Oh. Is there some way to sign in users in Android apps then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants