-
Notifications
You must be signed in to change notification settings - Fork 46
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
Error after fresh install #3
Comments
Hi @bryantAXS, I've updated ViroARSampleApp to use the latest version of viro react which is 2.4. Can you do a fresh checkout of ViroARSample and do a fresh install of the node modules: "rm -rf node_modules && npm install". That should hopefully fix the issue you are seeing. If there are still issues, let us know. Thanks! |
JASWANTs-MacBook-Pro:ViroARSampleApp jaswantsinghjatav$ ./setup-ide.sh --ios
==== Running iOS Setup Script === File Doesn't Exist, Will Create: true/Info.plist File Doesn't Exist, Will Create: true/Info.plist File Doesn't Exist, Will Create: true/Info.plist Set: Entry, ":NSCameraUsageDescription", Does Not Exist cp: true/AppDelegate.m: No such file or directory grep: true/AppDelegate.m: No such file or directory sed: true/AppDelegate.m: No such file or directory Please help me to sort this out. Thanks in advance. |
Hi @jaswantjatav, something very strange is happening here. The script should not be looking for true.xcodeproj. What shell are you using? Perhaps the shell is executing script incorrectly. Can you try using the normal bash shell that ships with mac? |
I am running into the same exact issue. What happens is when I run './setup-ide.sh ios', it changes my Podfile target to 'true', instead of my project name. Even when I change it back to my target name, it keeps changing the file, and this error keeps displaying. |
Nevermind, solved the issue...at least for me, I did not have a project name set up in package.json. |
After install both Viro and the ViroARSampleApp today I'm getting this error (plug a handfull of others) on the initial load.
The text was updated successfully, but these errors were encountered: