Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught TypeError: Cannot set property 'volume' of null #23664

Closed
haddow777 opened this issue Feb 27, 2019 · 3 comments
Closed

Uncaught TypeError: Cannot set property 'volume' of null #23664

haddow777 opened this issue Feb 27, 2019 · 3 comments
Labels
Bug Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@haddow777
Copy link

The debugger-ui crashes and then doesn't output the proper output, such as console.log statements put into code.
Screenshot of error

To Reproduce

It appears that the code is trying to get a reference to an audio component that is supposed to be loaded on the page. The problems is that the element is obviously not loaded at the time the code is trying to get the reference. This can be seen in the fact that once the code is allows to execute past the exception, the element is loaded and can be referenced.
Screenshot of element being references after error
So, clearly the issue is that the code is trying to access the element too soon as not all elements are loaded yet. This seems to be closely linked with the chrome extensions that are running. Here are mine.
Screenshot of chrome extensions
You will notice I only have one loaded in the picture. I usually have more loaded, but I was trying to see which one was conflicting with the code. The problem I found was that it is any of them, potentially. For some reason, they can slow down the loading of the audio element the code is trying to reference.
The confusing thing is, different extensions will have different effects. Some will always cause the error. Others won't. Still others will cause the error some of the time while not others. With the extension shown, the code would break half the time after each refresh.
Not sure how you can fix this, but as the issue has been brought up many times before, I think we can say it hasn't been fixed. At least, put a check into the code to make sure it has go the reference it wants to the audio element. Maybe a setTimeout can be used if it fails to get it, or at least it can safely skips that portion as it doesn't seem to be vital to the program.

Expected Behavior

That the debugger would load and run properly despite how many chrome extensions are loaded. Seems silly to have to shut down all ones extensions because the debugger can't safely get a reference to an audio element.

Code Example

System Setup

React Native Environment Info:
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz
Memory: 2.43 GB / 7.91 GB
Binaries:
Yarn: 1.13.0 - C:\Users\SURFACE\AppData\Roaming\npm\yarn.CMD
npm: 6.7.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338

@kaelxeth
Copy link

Duplicate #19022

@stale
Copy link

stale bot commented Aug 2, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Aug 2, 2019
@stale
Copy link

stale bot commented Aug 9, 2019

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Aug 9, 2019
@facebook facebook locked as resolved and limited conversation to collaborators Aug 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

5 participants