React-native-paper: Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.

[isthaison]

Current behaviour

Expected behaviour

Code sample

Screenshots (if applicable)

What have you tried

Your Environment

| software | version
| --------------------- | -------
| ios or android |
| react-native |
| react-native-paper |
| node |
| npm or yarn |

[Trancever]

Please provide more informations.

[isthaison]

when i upgrade sdk 31 then facing problem

[satya164]

You can ignore the warnings. They won't affect the functionality.

[RajenderDandyal]

getting the same warning .. multiple times when app starts ...
any clue ..How to remove this warning
using Native-base custom theme + RNv0.57 +RNNv2

[satya164]

@RajenderDandyal It's not a bug. You can ignore it: https://github.com/facebook/metro/issues/287

Metro team has to fix it. We cannot do anything about it in Paper.

[ethanke]

3 times warning each startup of my app. Even if it's not a functional problem, would be great to find a way to fix this warning

[Trancever]

@ethanke This will hide warnings console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper'];. We do not prioritize fixing this, because it's not really an issue.

[firofame]

Still getting this issue.

[sajaddp]

Ignoring warnings is not the right thing to do |:

[azuxx]

Still having the issue with RN 0.62.2

[Trancever]

We are not planning to fix this anytime soon. You should silence this particular warning with: console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper'];

[catalincic]

HI @Trancever, funny you just replied to this, was looking for a solution myself too to hide the warnings!

Do you mind letting me know where exactly to add console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper']; ?

I've also tried adding YellowBox.ignoreWarnings(...) to the top of my root index.js file, but it's not working.

Thanks, much appreciated!

[HunteRoi]

HI @Trancever, funny you just replied to this, was looking for a solution myself too to hide the warnings!

Do you mind letting me know where exactly to add console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper']; ?

I've also tried adding YellowBox.ignoreWarnings(...) to the top of my root index.js file, but it's not working.

Thanks, much appreciated!

@catalincic Same here! Mention me whenever you get an answer please :eyes:

[kulikalov]

@ethanke This will hide warnings console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper'];. We do not prioritize fixing this, because it's not really an issue.

what do you mean it's not an issue? Quite a few people on the internet are spending their time on this. Fix the import, is it such a big deal to not fix it for 2 years??

[pke]

This is not an issue to be ignored. It renders the app in the simulator totally unresponsive! One can't even remove the in app warnings with "dismiss all".

[patheticGeek]

This is not an issue to be ignored. It renders the app in the simulator totally unresponsive! One can't even remove the in app warnings with "dismiss all".

Put
console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper'];
in the entry file eg. index.js It removes these warnings from popping up in the yellow blox

[pke]

LOL. No way! That is an ugly hack.
The source cause needs to be fixed.

-----Original Message-----
From: "Pathetic Geek" [e-mail]
Sent: ‎11/‎06/‎2020 16:25
To: "callstack/react-native-paper" [e-mail]
Cc: "Philipp Kursawe" [e-mail]; "Comment" [e-mail]
Subject: Re: [callstack/react-native-paper] Require cycles are allowed, butcan result in uninitialized values. Consider refactoring to remove the needfor a cycle. (#639)

This is not an issue to be ignored. It renders the app in the simulator totally unresponsive! One can't even remove the in app warnings with "dismiss all".
Put
console.ignoredYellowBox = ['Require cycle: node_modules/react-native-paper'];
in the entry file eg. index.js It removes these warnings from popping up in the yellow blox
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[raajnadar]

@pke I fixed the issue in this PR https://github.com/callstack/react-native-paper/pull/1851 but it is not yet merged because the PR breaks the docs if you can help me we can get that PR merged.

[pke]

I'll take a look.

-----Original Message-----
From: "Rajendran Nadar" [e-mail]
Sent: ‎11/‎06/‎2020 17:03
To: "callstack/react-native-paper" [e-mail]
Cc: "Philipp Kursawe" [e-mail]; "Mention" [e-mail]
Subject: Re: [callstack/react-native-paper] Require cycles are allowed, butcan result in uninitialized values. Consider refactoring to remove the needfor a cycle. (#639)

@pke I fixed the issue in this PR #1851 but it is not yet merged because the PR breaks the docs if you can help me we can get that PR merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[cjduncana]

Que hubo @Entx 👋 Quizás estás buscando agregar multiDexEnabled true en tu build.gradle como descrito en este artículo. Justo ayer me encontré con el mismo problema.

[amerllica]

This issue still exists 😢

[tondevelop]

I started to use RN 0.63.0. Still same warning exists. Maybe this warning comes from 'react-native-paper' I think.
Any solution will be appreciate. Thank you.

[GanongLS]

using react native 0.63.0 still has the issue...

[aavhanchatse]

Same issue. Please help.

[satsuya0114]

same issue. both in RN 0.61.5 & 0.63.0

[hkaracaoglu]

Same issue in RN 0.62.2

[GuilhermeCdrs]

Está aparecendo pra mim também, porem estou usando "react-native-maps".. Ainda não descobri a origem do erro/aviso.

[cjduncana]

@GuilhermeCdrs Ninguém sabe.

[muhammadwafa]

Same issue in react-native 0.63.2

[CarlosNeto2804]

@GuilhermeCdrs tive esse mesmo problema com a versão 0.63.2
Tente definir o estilo do MapView para uma posição absoluta com os valores superior, esquerdo, direito e inferior definidos.
Verifique se você ativou a API do Google Maps no console do desenvolvedor do Google;
`const styles = StyleSheet.create({
map: {
...StyleSheet.absoluteFillObject,
},
});

style={styles.map}
/>`

[CarlosNeto2804]

Same issue in react-native 0.63.2

@muhammadwafa Try setting the style of the MapView to an absolute position with top, left, right and bottom values set.
Make sure you have enabled Google Maps API in Google developer console
const styles = StyleSheet.create({
map: {
...StyleSheet.absoluteFillObject,
},
});
style={styles.map}
// other props
/>

[muhammadwafa]

I solved like this https://stackoverflow.com/a/63186739/11566074

[varnguyen]

I think it is an issue print warning!!!

You are probably importing something from "file A" into "file B", then importing something again from "file B" into "file A". Examine all the imports from both the files and see if there's any such cycle.

[jsockchain]

@varnguyen Everybody knows that.
But this error is coming from react-native-paper and the PR is not merged yet.

[raulicious]

Since it's not fixed yet, is there a way to ignore these warnings in RN 0.63 that uses logBox instead of yellowBox?

LogBox.ignoreLogs([
    'Require cycle:'
]);

doesn't work for me

[ixez]

What the heck! It has been two years and this problem has not been solved yet!

[amerllica]

@ixez, And this is an Open-Source world.

[anonewb]

LogBox.ignoreLogs(["Require cycle:"]);

[ixez]

LogBox.ignoreLogs(["Require cycle:"]);

It doesn't work for me. I found even I put LogBox.ignoreAllLogs();, the warning still comes out.

[ribeirogab]

The community is already two years old with this error and you do not solve it, regrettable...

[jaaywags]

I believe this has been fixed in this pull request, #2378 and released in v4.5.0.

Referencing this comment.

NVM. It was supposed to be fixed in that PR but looks like the issue is still occurring.

[simonedavico]

@jaaywags it has not, 4.5.0 still produces the same warnings.

[jaaywags]

As far as I can tell, this was actually fixed in Release v4.7.0. I installed v4.7.1 and no more require cycle messages!

Though, I did run into a weird issue. I got this error after upgrading

unable to resolve module checkboxelements

I fixed it by clearing cache using this command
npx react-native start --reset-cache

Shoutout to this post.