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

How to start with the Java API #1

Open
dmasoft opened this issue Feb 11, 2014 · 13 comments
Open

How to start with the Java API #1

dmasoft opened this issue Feb 11, 2014 · 13 comments

Comments

@dmasoft
Copy link

dmasoft commented Feb 11, 2014

I'm trying to develope a command line Java client for send message to other telegram users, but I cannot find how to configure my App id and my primary data center. As far as I know, these are the two basic things to begin the comunication.
Does anyone know where can I find an example of the API usage with all the steps I should do?

@RvanBaarle
Copy link

I have the same problem, I think the best solution, although not great, is to look at their app which uses it here: https://github.com/ex3ndr/telegram

@dmasoft
Copy link
Author

dmasoft commented Feb 25, 2014

I give up to get my own app_id and app_hash, so I toke one from the demo apps. Anyway I am not able to send messages with the Java Api. I can't get the user's contacts and the messages I'm sending does not arrive to me.

@SireInsectus
Copy link

dmasoft, Did you ever get past the issue of getting an app_id? We are having the same problem (#8) with no resolution whatsoever. I'm inclined to use the ID and Hash in the demo apps as well just to move development forward - I just wanted to get the guys a chance to fix the problem before we go down that road.

@dmasoft
Copy link
Author

dmasoft commented Mar 11, 2014

Sirelnsectus, I am at the same point that you. I can get a true answer from the telegram api when I run the saveDeveloperInfo method. Bu t I haven't receive no sms to complete my registration process. By now I'm using the app_id from the demo apps, but for sure this will be a problem in the future.
This web https://core.telegram.org/myapp Still tells me that my app is not ready. Also, the mail address in this web ( api_support@telegram.org) does not exists.

I hope anyone give us some light about this confusing process.

@leovandenberg
Copy link

Hi,

I am using the API-ID from the messenger app and I can do some basic stuff.

Unauthorized: TLRequestHelpGetNearestDc, TLRequestHelpGetConfig, TLRequestAuthSendCode

After I receive the code I can do the following:

  • TLRequestAuthSignIn or TLRequestAuthSignUp
  • TLRequestContactsImportContacts (only my own data is imported)
    • TLRequestContactsGetStatuses (only my own status is returned)

This is the point where I am stuck. I have no clue how to add or connect additional users/connections which are needed to get to the messaging-part working.

Any help is very much appreciated. .

Leo

@SireInsectus
Copy link

leovandenberg, if you have figured out how to add/connect additional users please share with us.

We currently have sample code to Register for an API-ID. If anyone has any other samples they would be will to contribute I'm sure everyone else would appreciate it. With that, can we close this issue?

https://github.com/SireInsectus/telegram-api-samples

@leovandenberg
Copy link

Hi,

I'm only able to import my own data. I have also figured out how to send and receive messages.
To do this I had to seek through the provided messenger code and a lot of "try and error".
The source code doesn't contain much comments so it is a lot of guessing for me. Not the thing I expect from a high level API.

My main goal is to add automatic (and secure) messaging to another application, however every small step with the Telegram API takes another day and I have reached the point where I start to think of other solutions such as XMPP libraries; maybe not with the security levels of Telegram, but with a lot of available sample code and tutorials.

@SireInsectus
Copy link

When you say messaging to another application, do you mean for production
of a message and consumption of a message by a computer, a computer and an
individual or between to two individuals?

-//---------//
///\UNCHIE-///\ONSTER.com
Jacob-D-Parr--|--559-640-7277
General-Manager-/-Owner
www.MunchieMonster.com http://www.munchiemonster.com/

On Fri, Mar 14, 2014 at 4:42 PM, leovandenberg notifications@github.comwrote:

Hi,

I'm only able to import my own data. I have also figured out how to send
and receive messages.
To do this I had to seek through the provided messenger code and a lot of
"try and error".
The source code doesn't contain much comments so it is a lot of guessing
for me. Not the thing I expect from a high level API.

My main goal is to add automatic (and secure) messaging to another
application, however every small step with the Telegram API takes another
day and I have reached the point where I start to think of other solutions
such as XMPP libraries; maybe not with the security levels of Telegram, but
with a lot of available sample code and tutorials.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-37708136
.

@ex3ndr
Copy link
Collaborator

ex3ndr commented Apr 6, 2014

I have released new version of Api with fat/shadow jar, so it is much easier to include to your project.
For basic implementation you may investigate my telegram-bot project.

@contecavour65
Copy link

I see that to use your example i must install Gradle plugin. It's mandatory? Can you help me to install it?

@suresh888
Copy link

i tried an example from https://github.com/SireInsectus/telegram-api-samples but it is not working and i am not using build.gradle please help me
This is the trace of the last try...
run:
TelegramApi#1001:Phase 0 in 2 ms
TelegramApi#1001:Phase 1 in 164 ms
TelegramApi#1001:Timeout Iteration
TelegramApi#1001:Connection iteration
TelegramApi#1001:#1: waitForDc
TelegramApi#1001:Phase 2 in 8 ms
TelegramApi#1001:Sender iteration
TelegramApi#1001:#1: Creating proto for dc
TelegramApi#1001:#1: Creating key
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
TelegramApi#1001:Phase 3 in 11 ms
TelegramApi#1001:>> #0: help.getConfig#c4f9186b
TelegramApi#1001:Timeout Iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
TelegramApi#1001:Sender iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
TransportRate:Transport: #1 173.240.5.253:443 #1.0
TransportRate:tryConnection #1
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.253:443 #1.0
Authorizer:Solved PQ in 42 ms
TransportRate:Transport: #1 173.240.5.253:443 #1.0
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: pingDelay for internal_actions
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1001:Salt check timeout
MTProto#1001:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: check for connector
TransportRate:Transport: #1 173.240.5.253:443 #1.0
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: pingDelay for internal_actions
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1002:Creating context...
TransportRate:tryConnection #1
MTProto#1002:Ping delay disconnect for 75 sec
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1002:Salt check timeout
MTProto#1002:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
TransportRate:Transport: #1 173.240.5.253:443 #1.0
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1003:Creating context...
TransportRate:tryConnection #1
MTProto#1002:sendMessage #8 account.registerDevice#446c712c
TelegramApi#1001:#MTProto #1002 created in 2413 ms
TelegramApi#1001:Connection iteration
TelegramApi#1001:Connection iteration
ActorDispatcher:Dispatching action: schedule for scheduller
TelegramApi#1001:Sender iteration
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001:sendMessage #9 help.getConfig#c4f9186b
TelegramApi#1001:#> #0 sent to MTProto #1001 with id #9
TelegramApi#1001:Sender iteration
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: pingDelay for internal_actions
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1003:Salt check timeout
MTProto#1003:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1001:Creating context...
TransportRate:tryConnection #1
TransportTcpPool#1002:Context created.
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1002#Scheduller:Forgetting message: #3
TransportTcpPool#1003:Context created.
ActorDispatcher:Dispatching action: check for connector
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
Scheduller:Total size: 16
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 24
Scheduller:Prepare package: account.registerDevice#446c712c of size 100
Scheduller:Total size: 124
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 136
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
TransportTcpPool#1001:Context created.
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1001:Creating context...
TransportRate:tryConnection #1
MTProto#1002#Scheduller:Adding msg_ack: 0
MTProto#1002#Scheduller:Adding package: #6 ping_delay_disconnect#f3427b8c (6039611633297260548, 1)
MTProto#1002#Scheduller:Adding package: #7 get_future_salts#b921bd04 (6039611633297260552, 3)
MTProto#1002#Scheduller:Adding package: #8 account.registerDevice#446c712c (6039611633297260556, 5)
MTProto#1002#Scheduller:Adding package: #12 ping#7abe77ec (6039611633297260560, 7)
MTProto#1002#Scheduller:Sending Package (6039611633297260564, 8)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1003#Scheduller:Forgetting message: #5
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 12
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 20
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 32
MTProto#1003#Scheduller:Iteration: count: 3, confirm:0
MTProto#1003#Scheduller:Building package
MTProto#1003#Scheduller:Adding msg_ack: 0
MTProto#1003#Scheduller:Adding package: #10 ping#7abe77ec (6039611637592227844, 1)
MTProto#1003#Scheduller:Adding package: #11 get_future_salts#b921bd04 (6039611637592227848, 3)
MTProto#1003#Scheduller:Adding package: #13 ping#7abe77ec (6039611637592227852, 5)
MTProto#1003#Scheduller:Sending Package (6039611637592227856, 6)
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Scheduller:Forgetting message: #2
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
Scheduller:Prepare package: help.getConfig#c4f9186b of size 44
Scheduller:Total size: 52
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 64
MTProto#1001#Scheduller:Iteration: count: 3, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Adding msg_ack: 0
MTProto#1001#Scheduller:Adding package: #4 get_future_salts#b921bd04 (6039611637592227864, 1)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Scheduller:Adding package: #9 help.getConfig#c4f9186b (6039611637592227868, 3)
MTProto#1001#Scheduller:Adding package: #14 ping#7abe77ec (6039611637592227872, 5)
MTProto#1001#Scheduller:Sending Package (6039611637592227876, 6)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 88
TransportTcpPool#1001:Context created.
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 12
MTProto#1001#Scheduller:Iteration: count: 1, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Single package: #15 ping#7abe77ec (6039611637592227880, 7)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 88
TransportTcpPool#1002:onSuccess
TransportTcpPool#1002:reset
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.253:443 #1.0
TransportTcpPool#1001:onSuccess
TransportTcpPool#1001:reset
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.253:443 #1.0
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003#Transport3:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:BadMessage: 48 #6039611637592227876
MTProto#1001:Reschedule messages because bad_server_salt #6039611637592227876
MTProto#1001#Scheduller:Resending as new #4
MTProto#1001#Scheduller:Resending as new #9
MTProto#1001#Scheduller:Resending as new #14
TransportTcpPool#1003:onSuccess
TransportTcpPool#1003:reset
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.253:443 #1.0
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
Scheduller:Prepare package: help.getConfig#c4f9186b of size 44
Scheduller:Total size: 52
MTProto#1001#Scheduller:Iteration: count: 2, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Adding package: #4 get_future_salts#b921bd04 (6039611637592227884, 9)
MTProto#1001#Scheduller:Adding package: #9 help.getConfig#c4f9186b (6039611637592227888, 11)
MTProto#1001#Scheduller:Sending Package (6039611637592227892, 12)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1001:Salt check timeout
MTProto#1001:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 12
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 20
MTProto#1001#Scheduller:Iteration: count: 2, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Adding package: #14 ping#7abe77ec (6039611637592227896, 13)
MTProto#1001#Scheduller:Adding package: #16 get_future_salts#b921bd04 (6039611637592227900, 15)
MTProto#1001#Scheduller:Sending Package (6039611637592227904, 16)
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: bad_server_salt#edab447b
MTProto#1002:BadMessage: 48 #6039611633297260564
MTProto#1002:Reschedule messages because bad_server_salt #6039611633297260564
MTProto#1002#Scheduller:Resending as new #6
MTProto#1002#Scheduller:Resending as new #7
MTProto#1002#Scheduller:Resending as new #8
MTProto#1002#Scheduller:Resending as new #12
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
Scheduller:Total size: 16
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 24
Scheduller:Prepare package: account.registerDevice#446c712c of size 100
Scheduller:Total size: 124
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 136
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1002#Scheduller:Adding package: #6 ping_delay_disconnect#f3427b8c (6039611637592227908, 9)
MTProto#1002#Scheduller:Adding package: #7 get_future_salts#b921bd04 (6039611637592227912, 11)
MTProto#1002#Scheduller:Adding package: #8 account.registerDevice#446c712c (6039611637592227916, 13)
MTProto#1002#Scheduller:Adding package: #12 ping#7abe77ec (6039611637592227920, 15)
MTProto#1002#Scheduller:Sending Package (6039611637592227924, 16)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1002:Salt check timeout
MTProto#1002:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
MTProto#1002#Scheduller:Iteration: count: 1, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1002#Scheduller:Single package: #17 get_future_salts#b921bd04 (6039611637592227928, 17)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: bad_server_salt#edab447b
MTProto#1003:BadMessage: 48 #6039611637592227856
MTProto#1003:Reschedule messages because bad_server_salt #6039611637592227856
MTProto#1003#Scheduller:Resending as new #10
MTProto#1003#Scheduller:Resending as new #11
MTProto#1003#Scheduller:Resending as new #13
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 12
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 20
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 32
MTProto#1003#Scheduller:Iteration: count: 3, confirm:0
MTProto#1003#Scheduller:Building package
MTProto#1003#Scheduller:Adding package: #10 ping#7abe77ec (6039611637592227932, 7)
MTProto#1003#Scheduller:Adding package: #11 get_future_salts#b921bd04 (6039611637592227936, 9)
MTProto#1003#Scheduller:Adding package: #13 ping#7abe77ec (6039611637592227940, 11)
MTProto#1003#Scheduller:Sending Package (6039611637592227944, 12)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1003:Salt check timeout
MTProto#1003:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
MTProto#1003#Scheduller:Iteration: count: 1, confirm:0
MTProto#1003#Scheduller:Building package
MTProto#1003#Scheduller:Single package: #18 get_future_salts#b921bd04 (6039611637592227948, 13)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 88
TransportTcpPool#1001:onSuccess
TransportTcpPool#1001:reset
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.253:443 #1.0
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:BadMessage: 48 #6039611637592227880
MTProto#1001:Reschedule messages because bad_server_salt #6039611637592227880
MTProto#1001#Scheduller:Resending as new #15
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 12
MTProto#1001#Scheduller:Iteration: count: 1, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Single package: #15 ping#7abe77ec (6039611637592227952, 17)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1001:Salt check timeout
MTProto#1001:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
MTProto#1001#Scheduller:Iteration: count: 1, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Single package: #19 get_future_salts#b921bd04 (6039611637592227956, 19)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 184
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1002: onSessionCreated
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 152
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1002:pong: 4702864102057897325
MTProto#1002#Scheduller:Forgetting message: #6
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: msgs_ack#62d6b459
MTProto#1002:msgs_ack: 6039611637592227916
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 1112
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: future_salts#ae500895
MTProto#1002#Scheduller:Forgetting message: #7
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1002:pong: -1146569514451205599
MTProto#1002#Scheduller:Forgetting message: #12
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 104
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: rpc_result#f35c6d01
MTProto#1002:rpc_result: 6039611637592227916
MTProto#1002:Auth key invalidated
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1001: onSessionCreated
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: pong#347773c5
MTProto#1001:pong: 7385558222277831306
MTProto#1001#Scheduller:Forgetting message: #14
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #16
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 200
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 1112
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 296
ActorDispatcher:Dispatching action: new for response
MTProto#1001:Ignoring messages #6039611641650853889
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1001: onSessionCreated
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: msgs_ack#62d6b459
TelegramApi#1001:<< #0 confirmed in 3594 ms
MTProto#1001:msgs_ack: 6039611637592227888
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #4
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: rpc_result#f35c6d01
MTProto#1001:rpc_result: 6039611637592227888
MTProto#1001:rpc_result: 6039611637592227888 #2e54dd74
TelegramApi#1001:<< #0 deserialized config#2e54dd74 in 1 ms
TelegramApi#1001:<< #0 config#2e54dd74 in 3605 ms
MTProto#1001#Scheduller:Forgetting message: #9
Exception================ null
MTProto#1002#Transport2:Start reading message: preBUILD SUCCESSFUL (total time: 4 seconds)

@pentix
Copy link

pentix commented Feb 7, 2015

Is

https://my.telegram.org/auth

what you are looking for?
You can register your App there and you get an appid as well as
two server addresses of the Telegram Network.

@Raakh
Copy link

Raakh commented Sep 19, 2015

Can you please send me compiled working code to my email ghayel@gmail.com? I shall be grateful to you

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

9 participants