org.jivesoftware.smack.SmackException$NoResponseException

No response received within reply timeout. Timeout was 5000ms (~5s). Used filter: IQReplyFilter: iqAndIdFilter (AndFilter: (OrFilter: (IQTypeFilter: type=error, IQTypeFilter: type=result), StanzaIdFilter: id=V3Zqn-8)), : fromFilter (OrFilter: (FromMatchesFilter (full): null, FromMatchesFilter (bare): 234377203703@gcm.googleapis.com, FromMatchesFilter (full): gcm.googleapis.com)).

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web24

  • via GitHub by puel
    ,
  • via Unknown by Paul Sterl,
  • via Unknown by Paul Sterl,
  • Stack trace

    • org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). Used filter: IQReplyFilter: iqAndIdFilter (AndFilter: (OrFilter: (IQTypeFilter: type=error, IQTypeFilter: type=result), StanzaIdFilter: id=V3Zqn-8)), : fromFilter (OrFilter: (FromMatchesFilter (full): null, FromMatchesFilter (bare): 234377203703@gcm.googleapis.com, FromMatchesFilter (full): gcm.googleapis.com)). at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:106)[smack-core-4.1.6.jar:4.1.6] at org.jivesoftware.smack.AbstractXMPPConnection$6.run(AbstractXMPPConnection.java:1447)[smack-core-4.1.6.jar:4.1.6] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[na:1.8.0_51] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[na:1.8.0_51] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[na:1.8.0_51] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_51] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_51]

    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 visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitor3 times, last one
    Unknown visitor
    Unknown visitorOnce,
    1 more bugmates