Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on updating Bot's Icon #94

Closed
LeakingAmps opened this issue Aug 2, 2016 · 3 comments
Closed

Error on updating Bot's Icon #94

LeakingAmps opened this issue Aug 2, 2016 · 3 comments

Comments

@LeakingAmps
Copy link

While using 2.2.0_334, I updated the bot's icon, and found this in console. It doesn't seem major, but it does say to report it!

[22:21:40] [Warning] [JDASocket]: Got an unexpected Json-parse error. Please redirect following message to the devs:
JSONObject["verified"] not found.
USER_UPDATE -> {"bot":true,"id":"[REDACTED]","avatar":"[REDACTED]","username":"[REDACTED]","discriminator":"6748"}

Note, I've removed the bot's id, avatar, and username because I don't know how dangerous each code is.

@DV8FromTheWorld
Copy link
Member

I'll mark this on our todo list.

@Xetanai
Copy link
Contributor

Xetanai commented Aug 15, 2016

Tested myself and didn't get any error in build 345.
My code:

public static void main(String[] args) {
        JDA jda = null;
        try {
            jda = new JDABuilder().setBotToken([REDACTED]).buildBlocking();

            jda.getAccountManager().setAvatar(AvatarUtil.getAvatar(new File("E:/Photos/Other/Assets/Avatars/RubixDev_new.png")))
                .update();
        } catch (LoginException | IllegalArgumentException | InterruptedException | UnsupportedEncodingException ignored) {}
    }

@DV8FromTheWorld
Copy link
Member

Yep. I also just double checked this. It doesn't happen anymore.

Considering this is from 15 days ago, that was around the time that Discord rolled out some changes to OAuth and 2FA systems. Most likely they had a hickup and didn't send us all of the info.

This shouldn't happen anymore, so I'm going to close the issue. Feel free to reopen if you get the error again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants