search

telegram-s / telegram-api-old

Telegram Api library for java
MIT License
138 stars 64 forks source link

TelegramApI What can you do to help me when you're using it all of a sudden?friends #60

Open fengyaojieTTT opened 6 years ago

fengyaojieTTT commented 6 years ago

I was successful when I called the auth.SendCode! but after it was successful and then the other excuse was failed and I don't know what I should do?

Exceptions are as follows: ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1005#Transport32511:Start reading message: pre MTProto#1005#Transport32511:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32511:Message processing error MTProto#1005#Transport32511:Breaking context TransportTcpPool#1004:Context created. TransportTcpPool#1005:onChannelBroken (#32511) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 ActorDispatcher:Dispatching action: check for connector TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Scheduller:Connection dies 32511 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32614 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32614 ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 MTProto#1005#Transport32511:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32615 ping#7abe77ec (6557995111974699024, 32395) MTProto#1004#Scheduller:Sending Package (6557995111974699028, 32396) ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1005:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 MTProto#1004#Transport32512:Start reading message: pre MTProto#1004#Transport32512:Start reading message: 4 MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32616 ping#7abe77ec (6557995111974699036, 32273) MTProto#1005#Scheduller:Sending Package (6557995111974699040, 32274) ActorDispatcher:Dispatching action: schedule for scheduller java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32512:Message processing error MTProto#1004#Transport32512:Breaking context TransportTcpPool#1004:onChannelBroken (#32512) TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32512 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32615 ping#7abe77ec MTProto#1004#Scheduller:Forgetting message: #32615 MTProto#1004#Transport32512:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 MTProto#1005#Transport32513:Start reading message: pre MTProto#1005#Transport32513:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32513:Message processing error MTProto#1005#Transport32513:Breaking context TransportTcpPool#1004:Context created. TransportTcpPool#1005:onChannelBroken (#32513) ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Scheduller:Connection dies 32513 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32616 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32616 MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32617 ping#7abe77ec (6557995111974699048, 32397) MTProto#1004#Scheduller:Sending Package (6557995111974699052, 32398) ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: check for connector MTProto#1005#Transport32513:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 MTProto#1004#Transport32514:Start reading message: pre MTProto#1004#Transport32514:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32514:Message processing error MTProto#1004#Transport32514:Breaking context TransportTcpPool#1005:Context created. ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:onChannelBroken (#32514) TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32514 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32617 ping#7abe77ec MTProto#1004#Transport32514:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 MTProto#1004#Scheduller:Forgetting message: #32617 ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32618 ping#7abe77ec (6557995111974699060, 32275) MTProto#1005#Scheduller:Sending Package (6557995111974699064, 32276) ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1004:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32619 ping#7abe77ec (6557995111974699072, 32399) MTProto#1004#Scheduller:Sending Package (6557995111974699076, 32400) ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1005#Transport32515:Start reading message: pre MTProto#1005#Transport32515:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32515:Message processing error MTProto#1005#Transport32515:Breaking context TransportTcpPool#1005:onChannelBroken (#32515) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Scheduller:Connection dies 32515 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Transport32515:DieThread exit ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32618 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32618 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1004#Transport32516:Start reading message: pre MTProto#1004#Transport32516:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32516:Message processing error MTProto#1004#Transport32516:Breaking context TransportTcpPool#1004:onChannelBroken (#32516) TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32516 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32619 ping#7abe77ec MTProto#1004#Scheduller:Forgetting message: #32619 ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 MTProto#1004#Transport32516:DieThread exit TransportTcpPool#1005:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32620 ping#7abe77ec (6557995111974699084, 32277) MTProto#1005#Scheduller:Sending Package (6557995111974699088, 32278) ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1004:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32621 ping#7abe77ec (6557995111974699096, 32401) MTProto#1004#Scheduller:Sending Package (6557995111974699100, 32402) ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1005#Transport32517:Start reading message: pre MTProto#1005#Transport32517:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32517:Message processing error MTProto#1005#Transport32517:Breaking context TransportTcpPool#1005:onChannelBroken (#32517) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Scheduller:Connection dies 32517 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32620 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32620 ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 MTProto#1005#Transport32517:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1004#Transport32518:Start reading message: pre MTProto#1004#Transport32518:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32518:Message processing error MTProto#1004#Transport32518:Breaking context TransportTcpPool#1004:onChannelBroken (#32518) TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32518 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32621 ping#7abe77ec MTProto#1004#Scheduller:Forgetting message: #32621 ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1004#Transport32518:DieThread exit TransportTcpPool#1005:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32622 ping#7abe77ec (6557995116269666308, 32279) MTProto#1005#Scheduller:Sending Package (6557995116269666312, 32280) ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1004:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32623 ping#7abe77ec (6557995116269666320, 32403) MTProto#1004#Scheduller:Sending Package (6557995116269666324, 32404) ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1005#Transport32519:Start reading message: pre MTProto#1005#Transport32519:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32519:Message processing error MTProto#1005#Transport32519:Breaking context TransportTcpPool#1005:onChannelBroken (#32519) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Transport32519:DieThread exit ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 MTProto#1005#Scheduller:Connection dies 32519 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32622 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32622 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1004#Transport32520:Start reading message: pre MTProto#1004#Transport32520:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32520:Message processing error MTProto#1004#Transport32520:Breaking context TransportTcpPool#1004:onChannelBroken (#32520) TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32520 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32623 ping#7abe77ec MTProto#1004#Scheduller:Forgetting message: #32623 MTProto#1004#Transport32520:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1005:Context created. ActorDispatcher:Dispatching action: check for connector ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32624 ping#7abe77ec (6557995116269666332, 32281) MTProto#1005#Scheduller:Sending Package (6557995116269666336, 32282) ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1004:Context created. MTProto#1005#Transport32521:Start reading message: pre MTProto#1005#Transport32521:Start reading message: 4 ActorDispatcher:Dispatching action: schedule for scheduller Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 Scheduller:Total size: 8 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 24 Scheduller:Prepare package: ping_delay_disconnect#f3427b8c of size 16 Scheduller:Total size: 40 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 52 MTProto#1004#Scheduller:Iteration: count: 4, confirm:0 MTProto#1004#Scheduller:Building package MTProto#1004#Scheduller:Adding msg_ack: 0 MTProto#1004#Scheduller:Adding package: #22 get_future_salts#b921bd04 (6557978353012310024, 3) MTProto#1004#Scheduller:Adding package: #32093 ping_delay_disconnect#f3427b8c (6557994841391759424, 31871) MTProto#1004#Scheduller:Adding package: #32593 ping_delay_disconnect#f3427b8c (6557995099089797180, 32373) MTProto#1004#Scheduller:Adding package: #32625 ping#7abe77ec (6557995116269666344, 32405) MTProto#1004#Scheduller:Sending Package (6557995116269666348, 32406) ActorDispatcher:Dispatching action: schedule for scheduller ActorDispatcher:Dispatching action: check for connector java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1005#Transport32521:Message processing error MTProto#1005#Transport32521:Breaking context TransportTcpPool#1005:onChannelBroken (#32521) TransportTcpPool#1005:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1005#Scheduller:Connection dies 32521 MTProto#1005#Scheduller:Re-schedule: #28 get_future_salts#b921bd04 MTProto#1005#Scheduller:Re-schedule: #27087 ping#7abe77ec MTProto#1005#Scheduller:Re-schedule: #31591 ping#7abe77ec MTProto#1005#Scheduller:Removing: #32624 ping#7abe77ec MTProto#1005#Scheduller:Forgetting message: #32624 MTProto#1005#Transport32521:DieThread exit ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1005:Creating context... TransportRate:tryConnection #0 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1004#Transport32522:Start reading message: pre MTProto#1004#Transport32522:Start reading message: 4 java.lang.SecurityException at org.telegram.mtproto.transport.TransportPool.decrypt(TransportPool.java:148) at org.telegram.mtproto.transport.TransportTcpPool$TcpListener.onRawMessage(TransportTcpPool.java:322) at org.telegram.mtproto.transport.TcpContext.onMessage(TcpContext.java:167) at org.telegram.mtproto.transport.TcpContext.access$1600(TcpContext.java:21) at org.telegram.mtproto.transport.TcpContext$ReaderThread.run(TcpContext.java:320) MTProto#1004#Transport32522:Message processing error MTProto#1004#Transport32522:Breaking context TransportTcpPool#1005:Context created. TransportTcpPool#1004:onChannelBroken (#32522) ActorDispatcher:Dispatching action: check for connector MTProto#1004#Transport32522:DieThread exit ActorDispatcher:Dispatching action: schedule for scheduller TransportTcpPool#1004:onFailureNoWait TransportRate:onConnectionFailure #0 TransportRate:Transport: #0 149.154.175.50:443 #1.0 MTProto#1004#Scheduller:Connection dies 32522 MTProto#1004#Scheduller:Re-schedule: #22 get_future_salts#b921bd04 MTProto#1004#Scheduller:Re-schedule: #32093 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Re-schedule: #32593 ping_delay_disconnect#f3427b8c MTProto#1004#Scheduller:Removing: #32625 ping#7abe77ec Scheduller:Prepare package: get_future_salts#b921bd04 of size 8 ActorDispatcher:Dispatching action: check for connector TransportTcpPool#1004:Creating context... TransportRate:tryConnection #0 MTProto#1004#Scheduller:Forgetting message: #32625 Scheduller:Total size: 8 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 20 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 32 Scheduller:Prepare package: ping#7abe77ec of size 12 Scheduller:Total size: 44 MTProto#1005#Scheduller:Iteration: count: 4, confirm:0 MTProto#1005#Scheduller:Building package MTProto#1005#Scheduller:Adding msg_ack: 0 ActorDispatcher:Dispatching action: schedule for scheduller MTProto#1005#Scheduller:Adding package: #28 get_future_salts#b921bd04 (6557978353012310048, 3) MTProto#1005#Scheduller:Adding package: #27087 ping#7abe77ec (6557992264411381812, 26755) MTProto#1005#Scheduller:Adding package: #31591 ping#7abe77ec (6557994583693721648, 31251) MTProto#1005#Scheduller:Adding package: #32626 ping#7abe77ec (6557995116269666356, 32283) MTProto#1005#Scheduller:Sending Package (6557995116269666360, 32284) ActorDispatcher:Dispatching action: schedule for scheduller

eugenemallim commented 3 years ago

https://github.com/ex3ndr/telegram-api/issues/60#issue-324884623

eugenemallim commented 3 years ago

https://github.com/ex3ndr/telegram-api/issues/60#issue-324884623