java.util.concurrent.ExecutionException

org.telegram.api.engine.RpcException: PEER_ID_INVALID

Solutions on the web1

  • via GitHub by abangkis
    , 9 months ago
    org.telegram.api.engine.RpcException: PEER_ID_INVALID
  • Stack trace

    • java.util.concurrent.ExecutionException: org.telegram.api.engine.RpcException: PEER_ID_INVALID at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.telegram.bot.kernel.KernelComm.doRpcCallSync(KernelComm.java:184) at org.telegram.bot.kernel.KernelComm.performMarkAsReadInternal(KernelComm.java:654) at org.telegram.bot.kernel.KernelComm.performMarkAsRead(KernelComm.java:632) at org.telegram.plugins.echo.handlers.MessageHandler.handleMessageInternal(MessageHandler.java:56) at org.telegram.plugins.echo.handlers.MessageHandler.handleMessage(MessageHandler.java:46) at org.telegram.plugins.echo.handlers.CustomUpdatesHandler.onTLUpdateShortMessageCustom(CustomUpdatesHandler.java:61) at org.telegram.bot.handlers.UpdatesHandlerBase.onTLUpdateShortMessage(UpdatesHandlerBase.java:264) at org.telegram.bot.handlers.UpdatesHandlerBase.processUpdate(UpdatesHandlerBase.java:107) at org.telegram.bot.kernel.MainHandler$UpdateHandlerThread.run(MainHandler.java:301)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 6 months ago
    6 times, 10 months ago
    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 11 months ago
    66 more bugmates