Assign has an enumerable key on the prototype chain #3
Comments
|
I just started getting this same error and I am trying to are what has
changed.... Currently investigating
On Tue, Aug 1, 2017 at 7:54 AM Laszlo Schürg ***@***.***> wrote:
Im getting this error when Im calling Firebase put() to upload the image.
Running on ***@***.*** and ***@***.*** (before 3.9.0 same error)
One of the sources for assign has an enumerable key on the prototype chain. Are you trying to assign a prototype property? We don't allow it, as this is an edge case that we do not support. This error is a performance optimization and not spec compliant.
handleException @ ExceptionsManager.js:63
handleError @ InitializeCore.js:125
reportFatalError @ error-guard.js:44
__guard @ MessageQueue.js:230
callFunctionReturnFlushedQueue @ MessageQueue.js:100
(anonymous) @ debuggerWorker.js:71
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgCmbRLM7FxZcUBQK93YxoClEh1m3E-ks5sTxHfgaJpZM4Opnlx>
.
--
…--
Aaron K. Saunders
CEO Clearly Innovative Inc - Luma Lab - In3
aaron@clearlyinnovative.com
www.clearlyinnovative.com
www.In3DC.com
This email message and any attachment(s) are for the sole use of the
intended recipient(s) and may contain proprietary and/or confidential
information which may be privileged or otherwise protected from disclosure.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient(s), please contact the sender by reply
email and destroy the original message and any copies of the message as
well as any attachment(s) to the original message.
|
|
seems the issue exists when you are running the react-native debugger... as soon as I closed the debugger and reloaded the code, everything works fine on this side |
|
OMG I started to get crazy as it suddenly stopped working for me too. Thank you you for the hint Aaron! It is working again after stopping the debugger. Do you think I would make sense to talk to the Expo guys about it? |
|
I rebuilt the project completely without expo and saw the same issue, was
unable to isolate the source, is it react or is it something with the
debugger?
On Wed, Aug 2, 2017 at 8:06 AM Laszlo Schürg ***@***.***> wrote:
OMG I started to get crazy as it suddenly stopped working for me too.
Thank you you for the hint Aaron!
It is working again after stopping the debugger. Do you think I would make
sense to talk to the Expo guys about it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgCmQQHFYXDqne9YZ44JvHykA37qHA2ks5sUGZAgaJpZM4Opnlx>
.
--
…--
Aaron K. Saunders
CEO Clearly Innovative Inc - Luma Lab - In3
aaron@clearlyinnovative.com
www.clearlyinnovative.com
www.In3DC.com
This email message and any attachment(s) are for the sole use of the
intended recipient(s) and may contain proprietary and/or confidential
information which may be privileged or otherwise protected from disclosure.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient(s), please contact the sender by reply
email and destroy the original message and any copies of the message as
well as any attachment(s) to the original message.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Im getting this error when Im calling Firebase
put()to upload the image. Running on Expo@19.0.0 and Firebase@4.2.0 (before 3.9.0 same error)The text was updated successfully, but these errors were encountered: