KickAsync Leads to HTTPException

Hello,

I send this function KickUser the user I want kicked, the user doing the kicking, and the reason, if any.

[RequireBotPermission(GuildPermission.KickMembers)]
private async Task KickUser(IGuildUser user, SocketGuildUser personKicking, string reason = null)
{
    // user is the person being kicked.
    var textChannel = this._client.GetChannel(this._channelId) as SocketTextChannel;
    if (user == null) await textChannel.SendMessageAsync($"User doesn't exist. " +
        $"Cannot kick this user.");
    var role = user.Guild.Roles.FirstOrDefault(x => x.Name == "Admin");

    await textChannel.SendMessageAsync($"Attempting to kick {user.Mention}. " +
        $"Reason: {reason ?? "Admin has his reasons."}");

    if (!(user as SocketGuildUser).Roles.Contains(role))
    {
        if (personKicking.GuildPermissions.KickMembers)
        {
            await user.KickAsync(reason); // ERROR
        }
        else
        {
            await textChannel.SendMessageAsync($"You don't have permissions" +
                $" to kick {user.Mention}");
        }
    }
    else
    {
        await textChannel.SendMessageAsync($"{user.Mention} is an Admin." +
            $" They cannot be kicked.");
    }
}

Everytime it hits the “KickAsync” line, it throws an the following exception: Exception thrown: 'Discord.Net.HttpException' in System.Private.CoreLib.dll

Why is this happening? How can I resolve it?

[Tzadiko]

Aaahhh that’s how roles work! Haha, okay, I’m new to Discord and I skipped over the caption on the Role Linear Hierachy picture here: https://support.discordapp.com/hc/en-us/articles/214836687-Role-Management-101

The blurple arrow is your highest role; roles now follow a linear hierarchy. In simpler terms, the “metaphorical totem pole” is now a bit more literal in practice.

Thank you all for your prompt responses and help. You have a very intuitive and easy to use API.

[FiniteReality]

Make sure the position of the role is higher - kicking/banning works on role position in the role list rather than permissions.