Closed gwonsuji closed 1 year ago
Hello @gwonsuji! Thanks for taking the time to report it. This issue has already been reported in #330, so let me close this one as a duplicate.
@BartoszKlonowski I'm not using tvos, and the version and environment are different from the problem you mentioned. Nevertheless, it's disappointing to end like this without properly checking and supporting just because it's the same error phrase. None of the writing on the issue you mentioned was helpful to me. I wasted a week on this issue and nevertheless the issue didn't work out, so I asked here a question. But is it right to close the problem without giving proper help just because the phrase of the error is the same? I want proper help, not a manual response.
Hello @gwonsuji! Sorry for misunderstanding. Thing is, that in the issue I linked is a place for me to keep all those errors in one place so I can easier keep track on all of them. Note that after I linked your issue I also added new label noticing it indeed does affect different environment than the original issue just like you said, so please do not worry. edit: And also please see that other folks also post theirs "+1"s in the original issue even when explicitly saying their "+1"s are also for other platforms, just like your, which be sure I will keep in mind./edit Also, the fact that I closed the issue you created in favor of having it in the first reported for such error doesn't mean your issue will not be worked on, do not worry about it 👍 When having all of them linked in the "original one" I can still see all of them even when they are closed and I will cover all of them when I get to this issue regardless of their state or platform. Let me know if explanation of my approach covered your concerns.
@BartoszKlonowski Oh, I'm sorry I misunderstood. I just thought I was closing my problem and no more support. I'll be waiting.
I battled this for a long time. I fixed it by running...
rm -rf ios/build // this deletes the iOS build cache
npm start --reset-cache // this runs the metro server and rebuilds the iOS app
I reinstalled dependencies several times (delete node_modules, pods, build and install node packages, pods and build in XCode), and you know. there's a status bar in XCode. I think I may've tried to build while it's doing something, which isn't noticiable, and I put a couple hours into it and it works now.
Environment
react-native info output:
are you using the new architecture? No.
which version of react & react-native are you using? react : 18.1.0 react-native : 0.70.8
Description
Upgrading existing react native cli project. I am upgrading the reaction native version to 0.68.6 -> 0.70.8. I was warned to change to @react-native-community/slider because react-native no longer supports sliders after the version up. So I changed it, but I received the same error as above.
I wondered if it was a problem because I called from multiple screens, but the same problem occurs when I just call the slider in the App.js file. The bigger problem is that after you create a new project, the slider works and you don't know what the problem is. If necessary, I will compress and upload my node_modules.
This is my package.json