-
Notifications
You must be signed in to change notification settings - Fork 650
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 to build iOS app on fresh clone #77
Comments
I actually had the app running in the iOS simulator briefly, but after wiping and trying again I can't seem to get it running - just getting that same error: |
Yes, I can replicate this. Investigating. This appears to be reported in facebook/react-native#7308 and facebook/react-native#7806 as well. |
I had this problem and solved with the |
@ljmsouza After |
It's not entirely a react-native issue, Pepperoni should build out of the box. For some reason the PRODUCT_NAME variable binding we use to populate the CFBundleIdentifier field no longer works after the latest upgrade. I have fixed the issue locally by running react-native upgrade and reapplying our customisation son top of it. I have working version of Pepperoni, but made some unnecessary .pbxproject changes in the process and need to clean up before pushing this up. I'll reopen until this is fixed in master, so others experiencing the same problem don't get tripped up or resubmit a new one. |
Understood. Thank you. |
Any update on this? |
@clauderic this has just been fixed by #94. See the PR for tests to verify that change worked. If you have trouble with getting the new version working with a fresh clone, let me know. |
Still getting this error on a fresh clone |
@jhabdas I also just tried running the ios version and did complete that step and am having the same issues. Edit: The only thing I did differently was clone as mirror and update my remote as well renaming the app. I blew everything away and started over without renaming and just did a normal clone and it worked. |
@jevakallio seems this should be reopened |
I have faced that today |
Same, hit the exact same error off a fresh copy (or rather taken yesterday morning) clone of the template. |
RN moves fast. My best suggestion is to slim down your boilerplates, start from an RN init and practice "code for today" XP philosophies while building leveraging the best of the current kits available. Good luck to all. And I hope to see a new simple starter kit emerge for RN without immutable. |
Seems like I was able to fix the issue somehow... not quite sure what I did, attempted a manual linking, and then actually ran Here is what the commit ended up looking like. |
Same issue today for a fresh clone, any update on this? |
Hey @KrzysztofP, thanks for your interest in pepperoni 🍕 🚀 What steps are you using for a fresh clone? Just checked it out myself and the following steps are working for me. Let me know if you have any issues with these:
|
Hi @KrzysztofP, we removed now cocoa pods as dependency so you shouldn't get this error anymore when cloning a fresh copy of the repo again. Just run
to get started. Let me know if it solves you issue. |
closing this now since issue doesn't seem to be active anymore |
I'm still having this issue (running react-native run-android in a linux box). Not sure if it's a problem that I'm using Linux. |
@fredbt perhaps time to open a new ticket? |
use |
Might related to #25
Error:
Steps to reproduce the error:
git clone https://github.com/futurice/pepperoni-app-kit
cd pepperoni-app-kit && npm install
cp env.example.js env.js
cd ios && pod repo update && pod install && cd -
react-native run-ios
Versions:
The text was updated successfully, but these errors were encountered: