@shazron
So I looked more closely at your commit, and you mention a build exception in
mobile spec? I’ve tried to replicate a build exception, but I can’t get one —
can you share the error logs you were getting?
I agree; I’ll push out a PR early next week and re-open the issue to land it in
4
Hi Kerri, which changes? Is it related to my fix for the code in
prepare.js?
I think we should push this fix for 4.3.1, which I will launch a.s.a.p once
there is a PR for it :)
On Sat, Oct 22, 2016 at 9:28 PM, Kerri Shotts wrote:
> So, while testing for the VOTE thread, I discovered that a coupl
So, while testing for the VOTE thread, I discovered that a couple recent
changes have broken launch image storyboard support. As it stands now, the
broken code does NOT break existing functionality — it just means that should a
user utilize the launch storyboard image feature, it will render as
The problem is that iOS requires an updated tools. Chicken and egg! Maybe
we release everything at once?
On Thu, Oct 20, 2016 at 3:37 PM, julio cesar sanchez wrote:
> +1
>
> As there is a tools release planed and android release too, shouldn't we
> release ios and android first and then tools wi
+1
As there is a tools release planed and android release too, shouldn't we
release ios and android first and then tools with this platforms?
2016-10-20 22:38 GMT+02:00 Shazron :
> Chock full of new features:
> - CocoaPods (static libs only) support as
> - Xcode 8 / iOS 10 support
> - buildFlag
Chock full of new features:
- CocoaPods (static libs only) support as
- Xcode 8 / iOS 10 support
- buildFlag support on the command line
- iPad storyboard support
- others that I may have forgot
All the outstanding PRs and (according to me) issues that can get fixed
are in.
Let me know if there
