-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
Property specifiers expected type of array but got null #198
Comments
I just started seeing this as well and I'm wondering what changed 🤔 |
Me too. Could anyone help me fix this? |
I see this after upgrading from safe-area-context is a dependency of react-navigation, here are my version numbers:
When I switch back to my branch on v0.61.5, I no longer have this issue. |
@CHNB128 @jbolter @khattab93 Can each of you share information about your |
@taylorkline "react-native": "0.63.4" and I am using react native navigation |
And we don't use |
I have red some resources about similar errors: |
Note I upgraded to React Native Current dependencies:
|
I also thought about it, but same. |
|
I created discussion about this in https://github.com/babel/babel, may be some one will help us. |
Babel maintainer here. Does anyone have a complete stack trace or a repository I can clone and run a build command to reproduce the error? |
@nicolo-ribaudo |
The error is thrown at line 158 of https://unpkg.com/browse/@babel/types@7.14.5/lib/definitions/utils.js (it might be a slightly different line if you have a different Could you try editing it like this? Maybe function assertValueType(type) {
function validate(node, key, val) {
const valid = getType(val) === type;
if (!valid) {
+ Error.stackTraceLimit = 100;
+ console.trace("ERROR HERE!");
throw new TypeError(`Property ${key} expected type of ${type} but got ${getType(val)}`);
}
}
validate.type = type;
return validate;
} |
@nicolo-ribaudo
|
Bit more about it.
|
Thanks, I'm trying to reproduce the bug using that stack trace 👍 This seems to be a Babel bug, not caused by this project. |
Can you check the version of |
The highest version I have in
|
Can you check what |
Yes, it's |
Can you also try logging |
I solved it by removing |
So, as I understood problem was that |
We have a workaround, not a solution. I disagree with closing this issue. Something is wrong with some dependencies somewhere. @nicolo-ribaudo My babel types version is actually And here are the arguments to the validate call:
|
As a less heavy-handed workaround, I specifically removed the |
I had two entries for |
This is for v3 of the library, and we're on v4. Please re-open a new issue if you're still facing issues |
I launch application one day and got this error while bundling:
I can't determinate what went wrong. May be I change something in usage of
SafeAreaView
so it got null where should be array or something else.The text was updated successfully, but these errors were encountered: