-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
[Getting Started] Error: ignoring return value of function declared with warn_unused_result attribute #8584
Comments
I had similar experience today. But it was on macOS beta. Build failed on both XCode 7.3.1 (7D1014) and 8.0 beta 2 (8S162m). I did try $ react-native run-ios but got error:
macOS: 10.12 Beta (16A239j) Same two errors on both versions of XCode under Semantic Issue, when I tried build with XCode:
Edit: Sorry, I forgot to mention that I was not able to install watchman. |
+1 on this, getting almost exactly the same output as OP 😭 Could be related to #8108? |
I'm also facing this error :( |
same :( |
I'm running into this issue as well. I'm on Xcode Version 8.0 beta 2. And OS X 10.11.5. I've got almost the same log too |
Same issue here :( |
Same issue here:( |
1 similar comment
Same issue here:( |
Same issue here on Xcode version 8.0 beta 3 |
I uninstalled Xcode version 8.0 beta 3 and installed 7.3 and now everything works fine. |
@TimBroddin Thank you!! |
Having the same issue, but on XCode 7.2.1 I think the fact that upgrading XCode fixes this for some people has more to do with temporary files being retained somewhere and the installer deletes them. What is the -proper- way to clear a working directory and rerun a build with react-native? I'm having problems with rebuilding and having components that have been deleted or renamed still causing errors, which means that some part of the build is not removing intermediate results between builds. |
Thanks for this!! |
Fixed by 2f78852 |
How to upgrade to this version o this code in a "old" project @javache? |
We don't release patches for old releases, but you can apply these changes yourself. |
Oh thanks. I'll try |
Thanks @TimBroddin - it worked for me too! |
@TimBroddin your the man! |
@edin-m's solution of (void) in front of line temporarily worked for us on Sierra .. TY |
@noprom it looks like you're searching in your main project. If you click RCTWebSocket in the sidebar, and then search in Build Settings, you should see it. |
1. ignoring return value of function declared with warn_unused_result attribute facebook/react-native#8584 2. Environment Variables -> Add -> Name: "OS_ACTIVITY_MODE", Value:"disable"
@TimBroddin i love u |
@TimBroddin you are the MVP here. |
@TimBroddin, Bless your children, give them names... |
@TimBroddin You rock |
@dwilt I do take a while to figure it out,hahaha |
@TimBroddin God bless you children... |
Hi there, I'm snagged after a fresh install today:
$ react-native init AwesomeProject
$ react-native run-ios
Full log:
https://gist.github.com/andresn/1f35d718da9fc57542bb399460f2efd0#file-gistfile1-txt-L109
react-native@0.28.0
react-native-cli@1.0.0
XCode Beta 8.0
Mac OS X El Capitan v.10.11.5
I think this is specific to having Xcode-beta 8.0 installed, because running the app through beta-7.3 does work.
The text was updated successfully, but these errors were encountered: