Robert A Barclay

I recently ran into this myself. I store information that must be accessed promptly upon the loading of the application from background during a VOIP pushkit event, so i cannot...

I ran into this problem too, except with the the scenario of using "onFirstUnlock", which by the way if you are storing login credentials is the safest and most secure....

getting something similar. This seems to have to do with `event-target-shim`, and it appears to be with the 111.0.6 update as best as i can tell, since its a new...

Given the Hermes is becoming the default on RN, would it be a good idea then to support Hermes if .prototype is infact not supported?

we are currently using RN 0.72.5. Per https://reactnative.dev/docs/hermes, it has become dafault as of RN 0.70 and RN 0.72.5 has `event-target-shim` at '^5.0.1', which is why we have not moved...

Will see what we can do. We have some tight cycles as well.

I might have found more information to help with this issue: basically RN 0.72.x is still using `event-target-shim: "^5.0.1"`. We are using yarn in a learna mono repo, so under...

By removing all imports of `Event` and implementing the `type` prop on each Event subclass class (in a hacky way) i was able to get these errors to disappear given...

i'm seeing if there are adjustments that can/need to be made with webpack and our bunlding proccess, becuase it would be a serious issue of flattening out two differing versions...

As an update here, we found that we has some bable preset configurations that was flattening our modules out as an optimization, and due to that the `event-target-shim` that was...