com.pokegoapi.exceptions.RemoteServerException

com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web63

  • com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null
  • via GitHub by Padrino02
    , 11 months ago
    com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null
  • com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null
  • Stack trace

    • com.pokegoapi.exceptions.RemoteServerException: com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null at com.pokegoapi.api.map.Map.getMapObjects(Map.java:307) at com.pokegoapi.api.map.Map.getMapObjects(Map.java:270) at com.pokegoapi.api.map.Map.getMapObjects(Map.java:205) at com.pokegoapi.api.map.Map.getMapObjects(Map.java:195) at com.pokegoapi.api.map.Map.getCatchablePokemon(Map.java:103) at ink.abb.pogo.scraper.tasks.WalkToUnusedPokestop.run(WalkToUnusedPokestop.kt:24) at ink.abb.pogo.scraper.Bot.task(Bot.kt:163) at ink.abb.pogo.scraper.tasks.ProcessPokestops.run(ProcessPokestops.kt:44) at ink.abb.pogo.scraper.Bot.task(Bot.kt:163) at ink.abb.pogo.scraper.Bot$start$4.invoke(Bot.kt:115) at ink.abb.pogo.scraper.Bot$start$4.invoke(Bot.kt:30) at ink.abb.pogo.scraper.Bot$runLoop$1.invoke(Bot.kt:128) at ink.abb.pogo.scraper.Bot$runLoop$1.invoke(Bot.kt:30) at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:18) Caused by: com.google.protobuf.InvalidProtocolBufferException: Contents of buffer are null at com.pokegoapi.main.ServerRequest.getData(ServerRequest.java:66) at com.pokegoapi.api.map.Map.getMapObjects(Map.java:305) ... 13 more

    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

    You’re the first here who have seen this exception.