-
Notifications
You must be signed in to change notification settings - Fork 140
Conversation
…gins to handle some of the code in the boilerplate. Almost all dependencies are bumped except for the mobx deps (because of limitations in Android). We need to handle the jest setup, for know I just got it tow work. We probably need to update the jest-preset-ignite config.
There is still work that needs to be done .. It seems the patch doesn't work with ios.
@nirre7 great work on the update. I was attempting the same with RN 0.56 but didn't get to submit a PR yet. However I can help out with a few issues.
Looks like the lib received a typescript/jest update in the meantime: infinitered/jest-preset-ignite@f32890d Like this, I got the boilerplate to work on both, iOS and Android. |
@marcelkalveram thanks for the help! The jest setup now works great! However there are still issues with the IOS + SplashPagePatch... I have a stashed updated of the patch that adds UIAppFonts with Montserrat references and the UIStatusBarStyle styling but I can't get it to work... Any help is appreciated |
@nirre7 how do you run the boilerplate locally? I ran into some errors when ignite silently failed at adding this boilerplate as a plugin. So when installing it from a local folder I had to tweak the following line in
to
and then I run Or otherwise it would skip a bunch of install steps such as |
I run it as: I've ran it a couple of times with --debug or --verbose (forget which one ...) and it seems to run everything locally. |
@nirre7 oh, ok! I do get the following error if I don't apply the little patch/hack I mentioned: If that's not the issue, I'd also have to investigate further. |
Oh thats weird. Everything builds and works on Android without any hacks for me. Ignite doctor React Native Ignite Android iOS |
@nirre7 My assumption is that it's something xCode 10-related. For me it works fine on xCode 9.4 and I can't reproduce the issue you have. It looks like the RN team is aware of xCode 10 problems and working on fixing them for the 0.58 release: facebook/react-native#19573 |
Could definitely have something todo with xcode 😞 .... Given that Android works etc. I'm going to try to downgrade to xcode 9.x and then I'll update / create a new PR when 0.58 is out 👍 |
@ryanlntn was able to get one of our projects to build in Xcode 10 after upgrading the project to RN 0.57, so maybe he has some ideas. |
I definitely had some linking issues after upgrading but for the most part I was able to resolve them by updating Cocoapods. I would still recommend against using react-native with XCode 10 right now. It seems incredibly unstable. I've been having pretty consistent issues with the installer failing unless I reboot the simulator. |
Deleted too much in previous commit ...
…rplate-bowser # Conflicts: # boilerplate/package.json.ejs
Finally 🎉 Got it to work after downgrading to XCode 9.4.1. Would be great to get this reviewed and merged 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good apart from the error that @jamonholmgren referenced. I'm going to add some code on your fork that will execute the workaround described here
@mlaco @jamonholmgren Did it work when you ran the bundler in a separate terminal? I might be wrong (since there been so many issues with babel and regressions, it's hard to keep track of everything) but I think that error might be related to xcode 10 rather than the metro bundler, The regression issue I mentioned earlier is regarding the bundler and the RN hmr issue. |
@nirre7 sorry for the delay I was able to get this up and running using a separate terminal. However, I encountered a different problem along the way not mentioned here. If it only affects me, maybe it can be ignored. The error message:
and is fixed by changing the project settings:
I'm still trying to figure out what to make of this for now. I'll update again. |
I updated my macOS and now I am getting the RN hmr issue. Finally I was able to reproduce it! |
Seems they're prepping 0.57.3 now. Hopefully it will fix "everything" 🤞. react-native-community/releases#46 |
I hear that RN 0.57.3 is coming very soon, so I'll revisit this once it drops! |
Created and ran ignite app on both IOS and Android and it works. None of the earlier issues. Did not have to do any workarounds. |
@nirre7 great! I'll test it myself now. I'll get back to you asap |
Apparently I had some environment issues to sort out; sorry for the delay. I've tested it, and it looks good to go, so I'll approve! |
Does this work on Xcode 10? I'm not sure I'll have time to test today. Note that React Native 0.57.3 still has the |
@mlaco reports that it works! I'm good to go. 👍 |
@ugurozturk How are you running ignite? Is it on an existing RN / Ignite project? Run: FYI It won't work with ignite new SomeApp => choose Bowser and supply latest RN version, since the Bowser version on npm (atm) is based on 0.55 and it will not work with the latest RN since there has been changes in Info.plist between version 0.55 and latest. I.e the old patch won't work. If you really want to use the latest bowser ask someone at ignite to publish the latest to npm OR clone the repo and run it locally: |
Hmm.. Weird. Only difference is node version and that you run windows + another git client. When git is trying to apply the patch/hunks it fails. You could try to comment out the rnpm config in package.json in the boilerplate folder in the bowser clone. It might be that the info.plist file gets updated in the wrong order. |
@ugurozturk sorry about this. I'm trying to recruit help on this, because I'm not that great with the internals of Ignite yet. |
Those lines has been the same since the patch file was created it seems. |
So it looks like we need to modify that path, and others like it, to match the app name. I'll see if I can manage that! |
Oh, it looks like this code is meant to do exactly that. I guess the question would be why it didn't work in this case? |
@ugurozturk where is that diff file in your screenshot from? The boilerplate itself, or inside the app you generated? After looking into it, I see how it works now. Ignite copies the patch to your app directory (at which point it will still have the path |
@nirre7 Ofc without local boilerplate and bower test : @mlaco it was location on new project
Still idk why i having this error |
@mlaco We may need something like this for Xcode 10: https://github.com/infinitered/ir-boilerplate-barebones/blob/master/boilerplate.js#L35-L36 |
@ugurozturk I tried to reproduce this using your steps, but it worked for me. I did however, receive the message about the patch being corrupted, after I modified the patch. I assume you didn't modify yours though? |
@mlaco Well idk why, yet i tried this boilerplate on my Debian Server. And everything looks good in the Debian Server. |
@jamonholmgren I found this script in this issue about XCode build fails that we might be able to use. I'm trying it out now. There are a few other proposed fixes in the issue too, if that doesn't work. (btw, I'm not working solely on this issue. I just came across that script and realized it could be useful here) |
Hi.
I've updated Ignite Bowser to RN 0.57.1 and bumped multiple dependencies.
Babel 7 has been the major thing as you will se in the commits.
Android seems to be working.
IOS is almost there just a couple outstanding issues.
Outstanding issues (that I need help with before you can merge this)
The SplashPagePatch. Currently the IOS build breaks "SplashScreen.h' file not found" which I think is caused by the splashPagePatch file needs to be updated to patch the files from RN 0.57, i.e it needs to be updated with the correct "hunks".✅The jest setup in package.json is temporary. I got it to work with babel and ts but we probably want to "package" it a bit better alt update "jest-preset-ignite"@skellock && @marcelkalveram thanks! ✅Trailing comma or not, in text-field.tsx? TS Lint gets angry or compiler gets angry … Allow trailing commas after non-rest elements in destructuring microsoft/TypeScript#24672✅Would be great to get this merged with Bowser since I've got a big project coming up ;)
Thanks in advance
Niclas