Jda: Completed the setup for Guild without matching id in ReadyHandler cache

[MitchTalmadge]

JDA was working great until I initialized it inside of a Spring Boot service (previously I was not using Spring Boot). Now it can login but not connect to my guild.

Log:

[19:07:12] [Info] [JDA]: Login Successful!
[19:07:13] [Info] [JDASocket]: Connected to WebSocket
[19:08:43] [Fatal] [JDASocket]: Completed the setup for Guild: G:My Guild(<Big long number goes here>) without matching id in ReadyHandler cache
[19:08:43] [Fatal] [JDASocket]: Encountered an exception:
[19:08:43] [Fatal] [JDASocket]: java.lang.NullPointerException
    at net.dv8tion.jda.core.handle.ReadyHandler.guildSetupComplete(ReadyHandler.java:193)
    at net.dv8tion.jda.core.handle.GuildCreateHandler.lambda$handleInternally$91(GuildCreateHandler.java:44)
    at net.dv8tion.jda.core.entities.EntityBuilder.createGuildFirstPass(EntityBuilder.java:292)
    at net.dv8tion.jda.core.handle.GuildCreateHandler.handleInternally(GuildCreateHandler.java:38)
    at net.dv8tion.jda.core.handle.SocketHandler.handle(SocketHandler.java:37)
    at net.dv8tion.jda.core.requests.WebSocketClient.handleEvent(WebSocketClient.java:811)
    at net.dv8tion.jda.core.requests.WebSocketClient.onTextMessage(WebSocketClient.java:516)
    at net.dv8tion.jda.core.requests.WebSocketClient.onBinaryMessage(WebSocketClient.java:845)
    at com.neovisionaries.ws.client.ListenerManager.callOnBinaryMessage(ListenerManager.java:368)
    at com.neovisionaries.ws.client.ReadingThread.callOnBinaryMessage(ReadingThread.java:270)
    at com.neovisionaries.ws.client.ReadingThread.handleBinaryFrame(ReadingThread.java:990)
    at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:749)
    at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:108)
    at com.neovisionaries.ws.client.ReadingThread.runMain(ReadingThread.java:64)
    at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)

Really not sure where to go from here. I tried kicking and re-adding the bot.

[Kodehawa]

Are you on latest? I'm kinda sure it was fixed on 240

[MitchTalmadge]

I'm on 3.2.0_241, thanks for the quick reply!

[Kodehawa]

Do you use maven or gradle?
If you're using gradle, add compile group: 'org.json', name: 'json', version: '20160810' to your build.gradle dependencies.

[MitchTalmadge]

I use maven:

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>3.2.0_241</version>
</dependency>

[MinnDevelopment]

You need to specify the org. json version explicitly

[Kodehawa]

Try adding (Well imagine I know how to format it.)

```

org.json
json
20160810

[MitchTalmadge]

That worked, thanks both of you! I guess Spring Boot has a conflicting version?

[Sanduhr32]

The issue happend alot to maven users so we already knew the solution. However Gradle user are having no problems.