missing package product

Two days into my Swift (2) experience...func X( a:Int, b:Int) { print(a,b) } X( 1, 2) // error: missing argument label 'b:' in call X(a:1, 2) // error: incorrect argument labels in call (have 'a:_:', expected '_:b:') X( 1, b:2) // ok X(a:1, b:2) // error: extraneous argument label 'a:' in callHorror!😢😮😠😕😟➖⚠✖ And I *never* use Emoji.Contrast this with:print( [1,2,3].contains(2) )Perfect, I didn't know any of that syntax. But that's what I would expect. That's 'Pythonic'. Writing out my idea in straight pseudocode, and it works! Isn't that the goal of all of this? Getting the most natural effortless straightforward syntax?That named parameter mess reminds me of C++, where everything breaks down into a zillion edge cases.(On a side note, I wasted a lot of effort trying to get named parameters past the C++ committee. So there is some irony in the fact that although Swift has done it, it has in-so-doing created a C++-style awfulness).I am making a bad smell here for a reason. Because I've watched the

On WatchOS, there is a notification that seems to go off about ten minutes until the hour that reminds you to stand up and move around some. I know we can schedule local notifications, but when the notification is triggered how is Apple checking if they actually need to present the notification or not? For example, if I have stood in the past hour and moved around, there's no need to show me the notification at 10 minutes until the hour.My app runs on iOS. Reaching a goal is dependent on a user's last known action and the time elapsed since that last action. Currently, the user can launch my app and logic will be run to let them know their progress in reaching their goal. What I would like is the ability to run this logic in the background while the app is backgrounded (or even if it is killed). The end result for the user would be their iPhone is in their pocket and my app notifies them when the goal has been reached.There is not a server component to my app. I am aware of things like region monitoring, moni

Hi everyone,I'm having a doubt or an issue creating a simple CocoaTouch Framwork and measuring the code coverage.For test only purposes I just created one struct and one unit testing file. Before testing, in the scheme's Test phase I've already checked the Gather Coverage Data checkbox. All tests succeed but the code coverage for the Framework still 0% within the Report Navigator > Coverage tab. I just can get some coverage checking the Show Test Bundles option.Am I missing something? Do I have to include some code that uses the Framework to check the coverage?

I appriciate that apple brings all these new productivity features to the iPad with iOS 9.But folders on iPad is a joke. Half of the screen real estate is wasted. Before iOS 7, folders on iPad could contain 20 apps in a single view.But with iOS 7, multiple views has been introduced and maximum apps you can see in a single view is 9 apps in both ipad and iphone.It has been 2 years and apple should fix it. They should do it by viewing 4*4 = 16 apps in iPad's folders. Also that way it'll look same both portrait and landscape.It may seem like a trivial feature request for some of you. But it's important to me.I want to see more of my productivity folder apps or video folder apps in a single view.

I have a vertical NSStackView with views, which should have the same width as the stack view itself. I havn't foundany property of the stack view to say all subviews should have the same width. Do I missed something,or do I really have to specify additional constraints like subview.width = stackview.width ?

I am having a strange problem with orientation at app startup. This problem shows up on both the iPad simulator and iPad hardware. Lets say I am running in the iPad 2 (8.3) simulator. If the simulator is orented in portrait before I start the app, the views all look fine and when I simulate rotations, all the views rotate and look just fine.Now if I orient the simulator in landscape before I start the app, the views are properly oriented but larger in size. Now when I simulate rotations, all the views rotate but the size is still too large and there is no way to recover other than stopping the app, rotate the hardware, and restart the app again.My main view is a split screen in landscape but not in portrait. If I start the app with the simulator in landscape, the main view comes up split screen like it supposed to but the display view on the right is the one that is too large. The view looks like it goes off the screen to the right and bottom.By split screen I mean a scrollable list view on the left and a nor

i would like to get help to solve my problem