Uncaught (in promise) DOMException: The element has no supported sources.

[PManager1]

Uncaught (in promise) DOMException: The element has no supported sources.

I dk why do i get this, is it linked with React Native ?

There are so many of these,

doing on ios.

Please read the following carefully before opening a new issue.
Your issue may be closed if it does not provide the information required by this template.

We use GitHub Issues exclusively for tracking bugs in React Native.

• If you have a question, ask on Stack Overflow: http://stackoverflow.com/questions/tagged/react-native
• If you have a feature request, post it on Canny: https://react-native.canny.io/feature-requests

Make sure your issue reproduces on master. Your issue may already have been fixed!
If your issue is present in master and in the stable release, try to reproduce your bug on https://snack.expo.io/
If you can't reproduce the bug on Snack, provide a sample project.
At the very least, provide an example of your code.

--- Delete everything above this line ---

Description

Explain what you did, what you expected to happen, and what actually happens.

Reproduction Steps and Sample Code

List all the steps required to reproduce the issue you're reporting. These steps should be clear and concise.

An example of your code is REQUIRED

Solution

What needs to be done to address this issue? Ideally, provide a pull request with a fix.

Additional Information

• React Native version: [FILL THIS OUT: Be specific, filling out "latest" here is not enough.]
• Platform: [FILL THIS OUT: iOS, Android, or both?]
• Development Operating System: [FILL THIS OUT: Are you developing on MacOS, Linux, or Windows?]
• Dev tools: [FILL THIS OUT: Xcode or Android Studio version, iOS or Android SDK version, if applicable]

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.