stickers | repository contains the iOS and Android sample apps | iOS library

you can use MediaQuery.of(context).size.width and MediaQuery.of(context).size.height

use the slice function

In the StickerView file:

1. Remove the StickerView(Context context) constructor
2. Put the initialization code also in the StickerView(Context context, AttributeSet attributeSet) constructor (creating a dedicated method is a good approach) and
3. Change this(context, attributeSet, 0) to super(context, attributeSet)

There are only a few known image extensions like jpg, png, gif, jpeg. Maybe try and fetch the file with best guess extension, if it throws exception try the next format.

The issue you are having most likely stems from the fact that you are saving the entire Invites Collection object in your guildInvites Map. Remember that in Javascript, when you save a single object in multiple different locations, each location still points to the same object. Basically, when you save the invites object or invite.guild.invites.fetch() to your guildInvites Map, it refers to the exact same object as newInvites will. In other words, cachedInvites and newInvites are both referring to the same object; because of this, they will contain the exact same values. Whenever an invite in newInvites is updated, it will automatically also update the invite in cachedInvites. This may be happening only now due to some changes in discord.js' code for invite management in v13.

I have not, however, looked at the discord.js source code for the new InviteManager, so it is possible that some other, similar issue is at play here. However, the solution in this answer works regardless.

Because the cache and new invite lists were both the same, the uses between the cached and used invite ended up being equal (causing the cachedInvites.get(inv.code).uses < inv.uses condition to not be met). Thus, newInvites.find() could not find the invite you were looking for, and usedInvite ended up being undefined.

There are several ways you could fix this issue. My preference is to not save the entire invites collection to your invite cache. Since you only need to know the cached invite's code and old number of uses, you only need to save that information. No need to save entire Invite objects to your cache when you only need two small pieces of information from each cached invite.

This is my proposed new structure of your cachedInvites. As you can see, it is much simpler and more efficient than before. It also solves the aforementioned possible JS issues with a single object being saved to multiple locations, by not directly saving the invites object in your cache.

Discord uses the APNG format, which is essentially just letting PNG files be animated, for rendering stickers, so it being .png isn't the problem.

As for why it doesn't load, there are a number of reasons why.

1. Your browser might not support the format. This, however, is ruled out as you said in your question that you can load it in a seperate window.
2. It might be the media and cdn servers messing with the APNG data while compressing the file.

As you found out, Discord uses media.discordapp.net as its media proxy for loading images, so that might be at fault. There are known issues about videos loaded from that domain not loading in Discord, so that might be related.

I've tested this myself, and it looks like a) if you load the media link in your browser, it won't animate (at least for me), and b) if you send it in Discord, it also won't animate.

The cdn link, however, is a tiny bit different. I found out that a) it does, actually, animate on my browser (like what happened to yours) but b) does not animate in Discord.

So we know what happens on media is different from cdn. Maybe this is why?

My current theory is that Discord might strip unneeded (in its opinion) data from the PNG file (thinking it's not APNG) to cut down on bandwidth usage, which prevents it from animating.

I'll have to investigate this further, though.

For those of you who are still trying to find solution, I finally found it.

We just use ffmpeg with child_process.exec(). No need to install anything.

With the help of @LukeWoodward, I did find my mistake and that upd.getChatMember() was the one responsible for giving me the null pointer exception.

upd.getChatMember() will be null if the messages are coming from direct DMs in Telegram and not from group chats. For that, you need to use upd.getMessage().getFrom().getId() for getting the user's id who direct messaged your bot.

The voiceStateUpdate is emitted whenever a member changes their voice state. In some cases, e.g. when someone leaves a voice channel, newVoiceState.channel will be null and if you try to read a property of this, it will throw a TypeError.

You'll need to compare the voiceStates before and after the update to figure out what triggered the voiceStateUpdate event. I've just added some code below with a few examples. The following code logs if someone joined/left/switched channels, or if there are other changes like muted/unmuted themselves, started sharing their screen, etc.: