tracking-used-invites.md

[GregoryGHarding]

this code returns errors for first two member joins, i guess its creating a baseline, but theres no error handling. example:

You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
unhandledRejection: TypeError: Cannot read property 'get' of undefined
You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
unhandledRejection: TypeError: Cannot read property 'invite' of undefined

[acollierr17]

I read this line on that page:

Rember, because of the way the ready event works, you need to wait a bit before running the fetchInvite method[...] During this time, member joins won't correctly register because the cache doesn't exist.

And I believe the reason it may not be getting member joins is because of the way the ready event works.

[GregoryGHarding]

dosent matter how long bot has been online for, the first two invites return the above error

[acollierr17]

It's not about how long the bot has been online for. It's just about how the `guildMemberAdd` event fires in relation to the `ready` event as quoted in my previous response. It's just all about caching. The original response I provided along with the quote from the guide isn't about how long the bot has been online for. But how the code functions in relation with what is and isn't cached.

…

On Sun, Nov 18, 2018 at 4:12 AM Gregory G Harding ***@***.***> wrote: dosent matter how long bot has been online for, the first two invites return the above error — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#53 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AP0M0SfZq7rOsKEOD2eVOiyezXaWUaqeks5uwSRngaJpZM4YYxJR> .

[YorkAARGH]

Closing this due to no activity since November 18th, 2018.

We will investigate the issue though.