[BUG] Cannot read properties of undefined (reading 'getFile')

[MathiasWP]

Describe the bug
To be honest, i am not quite sure how this has happened. Sentry captured this, and we're left wondering how this is possible. Any help would be much appreciated.

Expected behavior
This should not throw.

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows >= 10
• Browser: Edge
• Version: 131.0.0

Additional context
Let me know if there's anything i can do to help investigate this further.

[jonkoops]

This seems like it would be fixed by #114

[MathiasWP]

This seems like it would be fixed by #114

Looks like it! Looking at the API is seems like the entry.kind === "file" would help here.

[rolandjitsu]

@jonkoops the same fix is in #107, though, it would reject there. Alternatively, as suggested in some of the comments there, in case the handle is undefined, we can continue to the getAsFile. I can rebase it and make it ready for master.

Following up on that conversation, the type is file at that point, so I'm also wondering why it is undefined.

[jonkoops]

Following up on that conversation, the type is file at that point, so I'm also wondering why it is undefined.

Indeed, it is hard to imagine a circumstance where it would be.

[MathiasWP]

Following up on that conversation, the type is file at that point, so I'm also wondering why it is undefined.

Indeed, it is hard to imagine a circumstance where it would be.

I would imagine maybe a browser bug, since the API is still marked as experimental. I give a +1 on fallbacking to getAsFile just in case. Also not sure if e.g. browser plugins that can tinker with items in drag & drop? And therefore cause weird edge cases.

[github-actions]

🎉 This issue has been resolved in version 2.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 3.0.0-beta.5 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 2.1.2 🎉

The release is available on:

• npm package (@release-2.1.x dist-tag)
• GitHub release

Your semantic-release bot 📦🚀