telegram-s/telegram-bot

Telegram S Edition Android App

This is second version of Telegram app.

This version based on open-source telegram-api, mtproto and tl-core libraries.

Building project

Build variants

There are multiple configurations of building app, some of them:

1. gradle assembleDevDebug - Development build for IDE, recomended for daily usage
2. gradle assembleCommonRelease - Release version for Google Play. Release versions need additional configuration for signing keys.
3. gradle assembleCommonDebuggable - Release version with debugging enabled for testing
4. gradle assembleBetaRelease - Builds beta-version of an app. Includes russian translations.
5. gradle assembleMdpiRelease - Release version for MDPI devices
6. gradle assembleHdpiRelease - Release version for HDPI devices
7. gradle assembleXhdpiRelease - Release version for XHDPI devices
8. gradle assembleXxhdpiRelease - Release version for XXHDPI devices
9. gradle dist - Building release distributive
10. gradle lightDist - Building release light version of distributive

Build from Sources

1. Checkout sources with all submodules
2. Select required build configuration and run required gradle command

Using from IDE

This sources are prepared for IntelliJ IDEA and Android Studio. Unfortunately IntelliJ IDEA has some bugs with gradle android projects, but i can't do something with this.

More information

####Telegram project

http://telegram.org/

Telegram api documentation

English: http://core.telegram.org/api

Russian: http://dev.stel.com/api

MTProto documentation

English: http://core.telegram.org/mtproto

Russian: http://dev.stel.com/mtproto

Type Language documentation

English: http://core.telegram.org/mtproto/TL

Russian: http://dev.stel.com/mtproto/TL

Licence

Project uses MIT License

telegram-bot's Issues

onError 169: 400 PEER_ID_INVALID

Incoming message from user #41151607: bot work please
onError 169: 400 PEER_ID_INVALID //when trying to send message to this user

Telegram bot user and this #41151607 are the different users. What can I do with this? Thanks.

Cant build bot through Gradle.

telegram-bot-master$ ./gradlew copyToLib

FAILURE: Build failed with an exception.

• What went wrong:
  Could not determine the dependencies of task ':app:copyToLib'.

  Configuration with name 'default' not found.

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.297 secs

Always TimeoutException on Android

I'm developing on Android and i've tested my app on emulator and real device. At first i've used the last jar distributed, but after some timeout exception i've seen other issue and i've reverted to the v11 implementation.
Now i'm sending the code to my phone, switching datacenter and then sign in with phone, phone's hashcode and signkey but it always return me timeout exception.
I'm also following the guideline on the Telegram docs and it seems to be the good way, also the docs tell me that it should return error, but it will return me always timeout exception.
There's a way to get out of this? I'm getting mad, i don't know if i'm missing something or if the api are inconsistent.

MTProto#1002:Auth key invalidated

I am trying to run this project but I am getting IOException. I have following log details in my console. Is this because of AppInfo parameters like app_id & app_hash? I have tested app_id & app_hash with Telegram Android client, and its working fine.

Use test DC? (write test for test servers): production
Using production servers
TelegramApi#1001:Phase 0 in 2 ms
TelegramApi#1001:Phase 1 in 123 ms
TelegramApi#1001:Timeout Iteration
TelegramApi#1001:Phase 2 in 6 ms
TelegramApi#1001:Sender iteration
TelegramApi#1001:Connection iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
TelegramApi#1001:#1: waitForDc
TelegramApi#1001:#1: Creating proto for dc
TelegramApi#1001:#1: Creating key
api#1001#Downloader:DownloadFileThread iteration
TelegramApi#1001:Phase 3 in 7 ms
Loading fresh DC list...TelegramApi#1001:>> #0: help.getConfig#c4f9186b
TelegramApi#1001:Timeout Iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
TelegramApi#1001:Sender iteration
api#1001#Uploader:UploadFileThread iteration
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:tryConnection #1
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.1:443 #1.0
Authorizer:Solved PQ in 109 ms
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1002:Creating context...
ActorDispatcher:Dispatching action: schedule for scheduller
TransportRate:tryConnection #1
ActorDispatcher:Dispatching action: pingDelay for internal_actions
ActorDispatcher:Dispatching action: pingDelay for internal_actions
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1001:Salt check timeout
MTProto#1002:Ping delay disconnect for 75 sec
MTProto#1001:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
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: schedule for scheduller
ActorDispatcher:Dispatching action: pingDelay for internal_actions
ActorDispatcher:Dispatching action: check for connector
MTProto#1002:sendMessage #5 account.registerDevice#446c712c
ActorDispatcher:Dispatching action: requestSalts for internal_actions
TransportTcpPool#1003:Creating context...
ActorDispatcher:Dispatching action: requestSalts for internal_actions
TransportRate:tryConnection #1
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1003:Salt check timeout
MTProto#1003:Too few actual salts: 0, requesting news
TelegramApi#1001:#MTProto #1002 created in 2222 ms
TelegramApi#1001:Connection iteration
TelegramApi#1001:Sender iteration
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
TransportTcpPool#1002:Context created.
TransportTcpPool#1003:Context created.
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
MTProto#1002#Scheduller:Forgetting message: #3
MTProto#1003#Scheduller:Forgetting message: #4
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
Scheduller:Prepare package: account.registerDevice#446c712c of size 84
Scheduller:Total size: 84
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
Scheduller:Total size: 100
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 108
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 120
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1002#Scheduller:Adding msg_ack: 0
MTProto#1003#Scheduller:Adding msg_ack: 0
MTProto#1002#Scheduller:Adding package: #5 account.registerDevice#446c712c (6107397397028012036, 1)
MTProto#1003#Scheduller:Adding package: #9 ping#7abe77ec (6107397397028012036, 1)
MTProto#1002#Scheduller:Adding package: #6 ping_delay_disconnect#f3427b8c (6107397397028012040, 3)
MTProto#1003#Scheduller:Adding package: #10 get_future_salts#b921bd04 (6107397397028012044, 3)
MTProto#1002#Scheduller:Adding package: #8 get_future_salts#b921bd04 (6107397397028012048, 5)
MTProto#1002#Scheduller:Adding package: #11 ping#7abe77ec (6107397397028012056, 7)
MTProto#1002#Scheduller:Sending Package (6107397397028012060, 8)
MTProto#1003#Scheduller:Adding package: #12 ping#7abe77ec (6107397397028012052, 5)
MTProto#1003#Scheduller:Sending Package (6107397397028012064, 6)
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003#Transport3:Start reading message: 88
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 88
TransportTcpPool#1002:onSuccess
TransportTcpPool#1003:onSuccess
TransportTcpPool#1003:reset
TransportTcpPool#1002:reset
TransportRate:onConnectionSuccess #1
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: bad_server_salt#edab447b
MTProto#1002:MTProtoMessage: bad_server_salt#edab447b
MTProto#1002:BadMessage: 48 #6107397397028012060
MTProto#1003:BadMessage: 48 #6107397397028012064
MTProto#1002:Reschedule messages because bad_server_salt #6107397397028012060
MTProto#1003:Reschedule messages because bad_server_salt #6107397397028012064
MTProto#1003#Scheduller:Resending as new #9
MTProto#1003#Scheduller:Resending as new #10
MTProto#1003#Scheduller:Resending as new #12
MTProto#1002#Scheduller:Resending as new #5
MTProto#1002#Scheduller:Resending as new #6
MTProto#1002#Scheduller:Resending as new #8
MTProto#1002#Scheduller:Resending as new #11
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
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1003#Scheduller:Adding package: #9 ping#7abe77ec (6107397397028012068, 7)
MTProto#1003#Scheduller:Adding package: #10 get_future_salts#b921bd04 (6107397397028012072, 9)
Scheduller:Prepare package: account.registerDevice#446c712c of size 84
Scheduller:Total size: 84
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
Scheduller:Total size: 100
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 108
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 120
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1003#Scheduller:Adding package: #12 ping#7abe77ec (6107397397028012076, 11)
MTProto#1002#Scheduller:Adding package: #5 account.registerDevice#446c712c (6107397397028012080, 9)
MTProto#1003#Scheduller:Sending Package (6107397397028012084, 12)
MTProto#1002#Scheduller:Adding package: #6 ping_delay_disconnect#f3427b8c (6107397397028012088, 11)
MTProto#1002#Scheduller:Adding package: #8 get_future_salts#b921bd04 (6107397397028012092, 13)
MTProto#1002#Scheduller:Adding package: #11 ping#7abe77ec (6107397397028012096, 15)
MTProto#1002#Scheduller:Sending Package (6107397397028012100, 16)
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: #13 get_future_salts#b921bd04 (6107397397028012104, 17)
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: #14 get_future_salts#b921bd04 (6107397397028012108, 13)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003#Transport3:Start reading message: 152
ActorDispatcher:Dispatching action: new for response
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 184
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003#Transport3:Start reading message: 1112
MTProto#1003:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1003: onSessionCreated
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: pong#347773c5
MTProto#1003:pong: -9163812034172340189
MTProto#1003#Scheduller:Forgetting message: #9
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1002: onSessionCreated
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003:MTProtoMessage: future_salts#ae500895
MTProto#1003#Scheduller:Forgetting message: #10
MTProto#1003#Transport3:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1002:pong: 2614958016563426611
MTProto#1002#Scheduller:Forgetting message: #6
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: msgs_ack#62d6b459
MTProto#1002:msgs_ack: 6107397397028012080
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: pong#347773c5
MTProto#1003:pong: -9041944040346766858
MTProto#1003#Scheduller:Forgetting message: #12
MTProto#1003#Transport3:Start reading message: pre
MTProto#1003#Transport3:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: future_salts#ae500895
MTProto#1003:MTProtoMessage: future_salts#ae500895
MTProto#1003#Scheduller:Forgetting message: #14
MTProto#1002#Scheduller:Forgetting message: #8
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002#Transport2:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1002#Transport2:Start reading message: pre
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1002:pong: 8255254634638895934
MTProto#1002#Scheduller:Forgetting message: #11
MTProto#1002#Transport2:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: future_salts#ae500895
MTProto#1002#Scheduller:Forgetting message: #13
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: 6107397397028012080
MTProto#1002:Auth key invalidated
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: checkDestroy for connector
TransportTcpPool#1001:Destroying contexts
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: checkDestroy for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
TelegramApi#1001:Timeout Iteration
Exception in thread "main" TelegramApi#1001:RPC #0: Timeout (500010 ms)
TelegramApi#1001:Timeout Iteration
org.telegram.api.engine.TimeoutException
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:369)
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:309)
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:400)
at com.wonderbiz.wtchat.Application.login(Application.java:397)
at com.wonderbiz.wtchat.Application.main(Application.java:60)
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller

TelegramApi#1001:Timeout Iteration
Exception in thread "main" TelegramApi#1001:RPC #0: Timeout (500010 ms)
TelegramApi#1001:Timeout Iteration
org.telegram.api.engine.TimeoutException
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:369)
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:309)
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:400)
at com.wonderbiz.wtchat.Application.login(Application.java:397)
at com.wonderbiz.wtchat.Application.main(Application.java:60)
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: schedule for scheduller

Win Support

I'd be happy to hear from you about windows support, most of others only support Linux.. Does this one support Win ?

[ubuntu][windows][org.telegram.api.engine.TimeoutException] doRpcCallNonAuth

in windows and also in ubuntu (vm) after i write server name i'm get timeout exception in process of "Loading fresh DC list.."
am i miss something?!

Loading fresh DC list...Exception in thread "main" org.telegram.api.engine.TimeoutException
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:364)
at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:428)
at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:420)
at org.telegram.bot.Application.login(Application.java:380)
at org.telegram.bot.Application.main(Application.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)

Loading fresh DC list timeout

Do we need to configure something for the telegram-bot or it should work out-of-the-box ?

I've run the bot on the production or test servers and I get a timeout when it tries to do a rpc call in the login() method

...
:app:run
Use test DC? (write test for test servers): Using production servers
Loading fresh DC list...Exception in thread "main" org.telegram.api.engine.TimeoutException
        at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:327)
        at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:391)
        at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:383)
        at org.telegram.bot.Application.login(Application.java:382)
        at org.telegram.bot.Application.main(Application.java:40)

Sending Video File sample

Can you help me. Can you add sample sending video also?
Thanks.

Cannot retrieve DC list (Unknown dispatcherId 'connection')

Execution program log:

Exception in thread "Connection#757108857" java.lang.RuntimeException: Unknown dispatcherId 'connection'
at com.droidkit.actors.ActorSystem.actorOf(ActorSystem.java:102)
at com.droidkit.actors.ActorSystem.actorOf(ActorSystem.java:63)
at org.telegram.mtproto.transport.TransportTcpPool.(TransportTcpPool.java:62)
at org.telegram.mtproto.MTProto.(MTProto.java:116)
at org.telegram.api.engine.TelegramApi$ConnectionThread.waitForDc(TelegramApi.java:895)
at org.telegram.api.engine.TelegramApi$ConnectionThread.run(TelegramApi.java:946)
Exception in thread "main" org.telegram.api.engine.TimeoutException
at org.telegram.api.engine.TelegramApi.doRpcCall(TelegramApi.java:369)
at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:428)
at org.telegram.api.engine.TelegramApi.doRpcCallNonAuth(TelegramApi.java:420)
at org.telegram.bot.Application.login(Application.java:380)
at org.telegram.bot.Application.main(Application.java:40)

UpdateShortMessage on own message ?

With current level api, the bot doesn't seem to receive the messages sent by a user with same phone number registered : if I log in telegram with the same phone number, I cannot talk to my bot (for debug or test). So I need to have 2 phone numbers or ask someone else to write...
If I undestand : https://core.telegram.org/constructor/updateShortMessage
we can only receive messages from other contacts.

What's the best solution to develop and test ? Is there a way to distinguish real person and a bot (even if associated with same phone number for security reasons ?) and change the informations for the bot (avatar, ...). For example, after registering an app/bot with the form https://my.telegram.org/apps, we could have special credentials or a virtual phone number (linked to real phone number) so we can use it to authenticate the bot with the SMS code ? Or we could use the same mechanism as https://my.telegram.org/apps ie. receive the TLSEntCode by secure chat in telegram : so we don't need to have a second phone number.

Thanks

Error in switchDC

Hello,

I'm trying to run this program but i recive a NullPointerException in switchDC phase.

Execution program log:

Use test DC? (write test for test servers):
Using production servers
TelegramApi#1001:Phase 0 in 16 ms
TelegramApi#1001:Phase 1 in 437 ms
TelegramApi#1001:Timeout Iteration
TelegramApi#1001:Connection iteration
TelegramApi#1001:#1: waitForDc
TelegramApi#1001:#1: Creating proto for dc
TelegramApi#1001:#1: Creating key
TelegramApi#1001:Phase 2 in 47 ms
TelegramApi#1001:Sender iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Downloader:DownloadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
api#1001#Uploader:UploadFileThread iteration
TelegramApi#1001:Phase 3 in 94 ms
Loading fresh DC list...TelegramApi#1001:Timeout Iteration
TelegramApi#1001:Sender iteration
TelegramApi#1001:>> #0: help.getConfig#c4f9186b
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:tryConnection #1
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.1:443 #1.0
Authorizer:Solved PQ in 313 ms
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
TransportTcpPool#1002:Creating context...
ActorDispatcher:Dispatching action: pingDelay for internal_actions
TransportTcpPool#1003:Creating context...
ActorDispatcher:Dispatching action: requestSalts for internal_actions
TransportRate:tryConnection #1
TransportRate:tryConnection #1
ActorDispatcher:Dispatching action: pingDelay for internal_actions
MTProto#1002:Ping delay disconnect for 75 sec
ActorDispatcher:Dispatching action: pingDelay for internal_actions
MTProto#1002:sendMessage #5 account.registerDevice#446c712c
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1003:Salt check timeout
MTProto#1001:Salt check timeout
MTProto#1003:Too few actual salts: 0, requesting news
MTProto#1001:Too few actual salts: 0, requesting news
ActorDispatcher:Dispatching action: schedule for scheduller
TelegramApi#1001:#MTProto #1002 created in 2719 ms
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: requestSalts for internal_actions
MTProto#1002:Salt check timeout
MTProto#1002:Too few actual salts: 0, requesting news
TelegramApi#1001:Connection iteration
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
TelegramApi#1001:Connection iteration
ActorDispatcher:Dispatching action: schedule for scheduller
TelegramApi#1001:Sender iteration
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
MTProto#1001:sendMessage #11 help.getConfig#c4f9186b
TransportTcpPool#1001:Creating context...
TelegramApi#1001:#> #0 sent to MTProto #1001 with id #11
TelegramApi#1001:Sender iteration
TransportRate:tryConnection #1
TransportTcpPool#1003:Context created.
TransportTcpPool#1001:Context created.
ActorDispatcher:Dispatching action: schedule for scheduller
TransportTcpPool#1002:Context created.
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: check for connector
MTProto#1003#Scheduller:Forgetting message: #4
MTProto#1001#Scheduller:Forgetting message: #2
MTProto#1002#Scheduller:Forgetting message: #3
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
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 8
Scheduller:Prepare package: account.registerDevice#446c712c of size 96
Scheduller:Prepare package: help.getConfig#c4f9186b of size 40
Scheduller:Total size: 96
Scheduller:Total size: 48
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
Scheduller:Total size: 112
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 120
Scheduller:Total size: 60
Scheduller:Prepare package: ping#7abe77ec of size 12
MTProto#1001#Scheduller:Iteration: count: 3, confirm:0
MTProto#1001#Scheduller:Building package
Scheduller:Total size: 132
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1002#Scheduller:Adding msg_ack: 0
MTProto#1003#Scheduller:Adding msg_ack: 0
MTProto#1001#Scheduller:Adding msg_ack: 0
MTProto#1003#Scheduller:Adding package: #6 ping#7abe77ec (6000607884231049220, 1)
MTProto#1001#Scheduller:Adding package: #9 get_future_salts#b921bd04 (6000607884231049224, 1)
MTProto#1002#Scheduller:Adding package: #5 account.registerDevice#446c712c (6000607884231049220, 1)
MTProto#1003#Scheduller:Adding package: #8 get_future_salts#b921bd04 (6000607884231049228, 3)
MTProto#1002#Scheduller:Adding package: #7 ping_delay_disconnect#f3427b8c (6000607884231049232, 3)
MTProto#1001#Scheduller:Adding package: #11 help.getConfig#c4f9186b (6000607884231049228, 3)
MTProto#1003#Scheduller:Adding package: #12 ping#7abe77ec (6000607884231049236, 5)
MTProto#1001#Scheduller:Adding package: #13 ping#7abe77ec (6000607884231049244, 5)
MTProto#1002#Scheduller:Adding package: #10 get_future_salts#b921bd04 (6000607884231049240, 5)
MTProto#1001#Scheduller:Sending Package (6000607884231049252, 6)
MTProto#1003#Scheduller:Sending Package (6000607884231049248, 6)
MTProto#1002#Scheduller:Adding package: #14 ping#7abe77ec (6000607884231049256, 7)
MTProto#1002#Scheduller:Sending Package (6000607884231049260, 8)
TransportTcpPool#1001:Creating context...
TransportRate:tryConnection #1
TransportTcpPool#1001:Context created.
ActorDispatcher:Dispatching action: check for connector
ActorDispatcher:Dispatching action: schedule for scheduller
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
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Single package: #15 ping#7abe77ec (6000607884231049264, 7)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 88
MTProto#1002#Transport3:Start reading message: pre
MTProto#1003#Transport2:Start reading message: pre
MTProto#1002#Transport3:Start reading message: 88
MTProto#1003#Transport2:Start reading message: 88
TransportTcpPool#1003:onSuccess
TransportTcpPool#1002:onSuccess
TransportTcpPool#1002:reset
TransportTcpPool#1001:onSuccess
TransportTcpPool#1001:reset
TransportTcpPool#1003:reset
TransportRate:onConnectionSuccess #1
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:onConnectionSuccess #1
TransportRate:Transport: #1 173.240.5.1:443 #1.0
TransportRate:Transport: #1 173.240.5.1:443 #1.0
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:MTProtoMessage: bad_server_salt#edab447b
MTProto#1003:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:BadMessage: 48 #6000607884231049252
MTProto#1002:BadMessage: 48 #6000607884231049260
MTProto#1003:BadMessage: 48 #6000607884231049248
MTProto#1001:Reschedule messages because bad_server_salt #6000607884231049252
MTProto#1003:Reschedule messages because bad_server_salt #6000607884231049248
MTProto#1002:Reschedule messages because bad_server_salt #6000607884231049260
MTProto#1003#Scheduller:Resending as new #6
MTProto#1001#Scheduller:Resending as new #9
MTProto#1003#Scheduller:Resending as new #8
MTProto#1002#Scheduller:Resending as new #5
MTProto#1003#Scheduller:Resending as new #12
MTProto#1001#Scheduller:Resending as new #11
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1002#Scheduller:Resending as new #7
MTProto#1001#Scheduller:Resending as new #13
Scheduller:Prepare package: ping#7abe77ec of size 12
MTProto#1002#Scheduller:Resending as new #10
Scheduller:Total size: 12
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 20
Scheduller:Prepare package: ping#7abe77ec of size 12
MTProto#1002#Scheduller:Resending as new #14
Scheduller:Total size: 32
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
MTProto#1003#Scheduller:Iteration: count: 3, confirm:0
MTProto#1003#Scheduller:Building package
Scheduller:Prepare package: account.registerDevice#446c712c of size 96
MTProto#1003#Scheduller:Adding package: #6 ping#7abe77ec (6000607888526016512, 7)
Scheduller:Total size: 8
Scheduller:Total size: 96
MTProto#1003#Scheduller:Adding package: #8 get_future_salts#b921bd04 (6000607888526016516, 9)
Scheduller:Prepare package: help.getConfig#c4f9186b of size 40
MTProto#1003#Scheduller:Adding package: #12 ping#7abe77ec (6000607888526016520, 11)
Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16
MTProto#1003#Scheduller:Sending Package (6000607888526016524, 12)
Scheduller:Total size: 48
Scheduller:Total size: 112
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Prepare package: get_future_salts#b921bd04 of size 8
Scheduller:Total size: 60
Scheduller:Total size: 120
MTProto#1001#Scheduller:Iteration: count: 3, confirm:0
MTProto#1001#Scheduller:Building package
Scheduller:Prepare package: ping#7abe77ec of size 12
Scheduller:Total size: 132
MTProto#1001#Scheduller:Adding package: #9 get_future_salts#b921bd04 (6000607888526016528, 9)
MTProto#1002#Scheduller:Iteration: count: 4, confirm:0
MTProto#1002#Scheduller:Building package
MTProto#1001#Scheduller:Adding package: #11 help.getConfig#c4f9186b (6000607888526016532, 11)
MTProto#1002#Scheduller:Adding package: #5 account.registerDevice#446c712c (6000607888526016536, 9)
MTProto#1001#Scheduller:Adding package: #13 ping#7abe77ec (6000607888526016540, 13)
MTProto#1002#Scheduller:Adding package: #7 ping_delay_disconnect#f3427b8c (6000607888526016544, 11)
MTProto#1001#Scheduller:Sending Package (6000607888526016548, 14)
MTProto#1002#Scheduller:Adding package: #10 get_future_salts#b921bd04 (6000607888526016552, 13)
MTProto#1002#Scheduller:Adding package: #14 ping#7abe77ec (6000607888526016556, 15)
MTProto#1002#Scheduller:Sending Package (6000607888526016560, 16)
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: #16 get_future_salts#b921bd04 (6000607888526016564, 13)
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 (6000607888526016568, 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: #18 get_future_salts#b921bd04 (6000607888526016572, 15)
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.1:443 #1.0
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:BadMessage: 48 #6000607884231049264
MTProto#1001:Reschedule messages because bad_server_salt #6000607884231049264
MTProto#1001#Scheduller:Resending as new #15
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 (6000607888526016576, 17)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
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 (6000607888526016580, 19)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1003#Transport2:Start reading message: pre
MTProto#1003#Transport2:Start reading message: 152
MTProto#1002#Transport3:Start reading message: pre
ActorDispatcher:Dispatching action: new for response
MTProto#1003#Transport2:Start reading message: pre
MTProto#1002#Transport3:Start reading message: 184
MTProto#1003#Transport2:Start reading message: 1112
MTProto#1003:MTProtoMessage: new_session_created#9ec20908
TelegramApi#1001:mtproto#1003: onSessionCreated
ActorDispatcher:Dispatching action: new for response
MTProto#1001#Transport4:Start reading message: pre
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: pong#347773c5
MTProto#1003:pong: 8266015509962921824
MTProto#1002:MTProtoMessage: new_session_created#9ec20908
MTProto#1003#Scheduller:Forgetting message: #6
TelegramApi#1001:mtproto#1002: onSessionCreated
ActorDispatcher:Dispatching action: new for response
MTProto#1001#Transport4:Start reading message: 152
MTProto#1002#Transport3:Start reading message: pre
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1002:pong: -1004136667723179958
MTProto#1002#Scheduller:Forgetting message: #7
MTProto#1002#Transport3:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: msgs_ack#62d6b459
MTProto#1001#Transport4:Start reading message: pre
MTProto#1002:msgs_ack: 6000607888526016536
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1001#Transport4:Start reading message: 1112
MTProto#1003#Transport2:Start reading message: pre
MTProto#1003#Transport2:Start reading message: 88
MTProto#1003:MTProtoMessage: future_salts#ae500895
MTProto#1003#Scheduller:Forgetting message: #8
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 3187 ms
MTProto#1001:msgs_ack: 6000607888526016532
MTProto#1003#Transport2:Start reading message: pre
MTProto#1003#Transport2:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1002#Transport3:Start reading message: pre
MTProto#1003:MTProtoMessage: pong#347773c5
MTProto#1003:pong: 4478047087429321965
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: future_salts#ae500895
MTProto#1002#Scheduller:Forgetting message: #10
MTProto#1003#Scheduller:Forgetting message: #12
ActorDispatcher:Dispatching action: new for response
MTProto#1002#Transport3:Start reading message: 88
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 328
ActorDispatcher:Dispatching action: new for response
ActorDispatcher:Dispatching action: new for response
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 1112
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 88
MTProto#1002#Transport3:Start reading message: pre
MTProto#1002#Transport3:Start reading message: 104
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #9
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: pong#347773c5
MTProto#1001:Ignoring messages #6000607889761017857
ActorDispatcher:Dispatching action: new for response
MTProto#1003:MTProtoMessage: future_salts#ae500895
MTProto#1003#Scheduller:Forgetting message: #16
MTProto#1001#Transport5:Start reading message: pre
MTProto#1001#Transport5:Start reading message: 88
MTProto#1002:pong: -3207722024628328379
MTProto#1002#Scheduller:Forgetting message: #14
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001:MTProtoMessage: rpc_result#f35c6d01
MTProto#1001:rpc_result: 6000607888526016532
MTProto#1001:rpc_result: 6000607888526016532 #2e54dd74
MTProto#1001#Transport4:Start reading message: 264
MTProto#1002#Transport3:Start reading message: pre
MTProto#1002#Transport3:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1002:MTProtoMessage: rpc_result#f35c6d01
MTProto#1002:rpc_result: 6000607888526016536
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 1112
TelegramApi#1001:<< #0 deserialized config#2e54dd74 in 0 ms
TelegramApi#1001:<< #0 config#2e54dd74 in 3203 ms
MTProto#1001#Scheduller:Forgetting message: #11
ActorDispatcher:Dispatching action: new for response
completed.
Phone number for bot:MTProto#1002:Auth key invalidated
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #18
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: pong#347773c5
MTProto#1001:pong: 1010305957934124337
MTProto#1001#Scheduller:Forgetting message: #13
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: pong#347773c5
MTProto#1001:pong: -7927455670892566000
MTProto#1001#Scheduller:Forgetting message: #15
ActorDispatcher:Dispatching action: new for response
MTProto#1001:Ignoring messages #6000607889772435457
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #19
+34XXXXXXXXX
Sending sms to phone +34XXXXXXXXX...TelegramApi#1001:Timeout Iteration
TelegramApi#1001:Sender iteration
TelegramApi#1001:>> #1: auth.sendCode#768d5f4d
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001:sendMessage #20 auth.sendCode#768d5f4d
TelegramApi#1001:#> #1 sent to MTProto #1001 with id #20
TelegramApi#1001:Sender iteration
Scheduller:Prepare package: auth.sendCode#768d5f4d of size 72
Scheduller:Total size: 72
MTProto#1001#Scheduller:Iteration: count: 1, confirm:2
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Adding msg_ack: 2
MTProto#1001#Scheduller:Adding package: #20 auth.sendCode#768d5f4d (6000607888526016588, 21)
MTProto#1001#Scheduller:Sending Package (6000607888526016592, 22)
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: bad_server_salt#edab447b
MTProto#1001:BadMessage: 48 #6000607888526016592
MTProto#1001:Reschedule messages because bad_server_salt #6000607888526016592
MTProto#1001#Scheduller:Resending as new #20
ActorDispatcher:Dispatching action: schedule for scheduller
Scheduller:Prepare package: auth.sendCode#768d5f4d of size 72
Scheduller:Total size: 72
MTProto#1001#Scheduller:Iteration: count: 1, confirm:0
MTProto#1001#Scheduller:Building package
MTProto#1001#Scheduller:Single package: #20 auth.sendCode#768d5f4d (6000607914295820288, 23)
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: #21 get_future_salts#b921bd04 (6000607914295820292, 25)
ActorDispatcher:Dispatching action: requestSalts for internal_actions
ActorDispatcher:Dispatching action: schedule for scheduller
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 88
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: msgs_ack#62d6b459
TelegramApi#1001:<< #1 confirmed in 344 ms
MTProto#1001:msgs_ack: 6000607914295820288
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 1112
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: future_salts#ae500895
MTProto#1001#Scheduller:Forgetting message: #21
MTProto#1001#Transport4:Start reading message: pre
MTProto#1001#Transport4:Start reading message: 104
ActorDispatcher:Dispatching action: new for response
MTProto#1001:MTProtoMessage: rpc_result#f35c6d01
MTProto#1001:rpc_result: 6000607914295820288
TelegramApi#1001:<< #1 error #303 PHONE_MIGRATE_2 in 344 ms
MTProto#1001#Scheduller:Forgetting message: #20
Exception in thread "main" java.lang.NullPointerException
at org.telegram.actors.ActorSystem.close(ActorSystem.java:97)
at org.telegram.mtproto.MTProto.close(MTProto.java:219)
at org.telegram.api.engine.TelegramApi.switchToDc(TelegramApi.java:161)
at org.telegram.bot.Application.login(Application.java:401)
at org.telegram.bot.Application.main(Application.java:40)

The connection occurs but when you receive the error '303 'and trying to make switchDC, the error is displayed.

I use Java 1.7 and telegram-api-1.1.127-shadow.jar

I also try with all api source code and tl-api-v12.jar

Our goal is to make an application server for automatic sending of notifications to our workers

Thanks in advance.