missing package product

Hi,I feel that I must be missing something obvious. Decomposing a list into the head and tail and then recursing over the tail is a standard functional programming technique, yet I'm struggling to do this for Sliceble types in Swift.To start with a simple case using an Array, I have a recursive function that follows this pattern:func recurseArray(arr: [Int]) -> [Int] { guard let first = arr.first else { return [] } let rest = recurseArray(Array(dropFirst(arr))) let next = rest.first ?? 0 return [first + next] + rest }(Obviously the real code does a lot more than add each number to the next).Note the call to `Array(dropFirst(seq))`. Converting to an Array is required since dropFirst actually returns an `ArraySlice`, and an `ArraySlice` isn't `Sliceable`, so I can't pass it to my function.I'm not sure what sort of optimisation the compiler is capable of here, but it seems to me that creating a new array from a slice unnecessarily won't be optimal. Is there a solution to this?Furthermore, what I'd *r

Am I the only one missing tv iOS betas on the new dev center?

I have a consumable IAP, I mark it as finished after my POST request returns success with[[SKPaymentQueue defaultQueue] finishTransaction:transaction];but if there is an error and then user closes the app and open it next time, even though I have no calls to StoreKit or etc. the app asks for password (I am assuming because its getting ready to notify the app about unfinished transaction). Is this desired behaviour? Am I missing something?

Hi!Does anybody know, where I can get good examples/explanation on how to use Swift(pref. 2.0) and Cocoa(OSX)?I'm familiar with programming languages (C/C++), but not very much with GUI programming, although understanding the basic concepts.So, want to understand how to code in Cocoa using MVC and in this context the use of delegates and protocols, which is recommended by Apple.All the examples I found so far, are either rather code fragments or don't go to much into the details of the basics (delegates, MVC) that I need to understand.But just reading the Cocoa API I'm not getting the insight to be able to put this in code.I would like to explore this on my own, but I'm missing some kind of a sound starting point to progress from there.Thanks for any kind of support...

I have a photo app with an action extension (not photo editing) that works well in Photos. I'm in the process of converting that app to freemium (different bundleID but same display names for the extension and app) and at one point I installed the new app with the original app still there during testing on a real phone. Then I saw two identical actions when a photo is selected and the action button is tapped.So, I looked and I may (or may not) have mixed bundleIDs for the various parts (or something), so I changed the display name for the newest app (over and over).Long story short, after deinstalling the original app, resetting the iPhone, cleaning the project, quitting/restarting Xcode, deleting both apps from the phone, reinstalling the new app alone, etc. when I try to use the free app on my phone bizarre things happen (and BTW, everything works fine in the simulator).What happens is that when I select a photo, tap the action button, my action icon is not there. But when I look under More… the single acti

I've searched all over, but I cannot find any specifications for the image sizes used in the complications that have images for both the 38 and 42mm watches. Creating a new project with complications creates an asset library with a complicaitons group, but I have not found any specs anywhere.Specifically:1) ModularSmallStackImage2) ModularSmallRingImage3) ModularSmallSimpleImage4) ModularLargeStandardBody (header image)5) ModularLargeTable (header image)6) ModularLargeColumns (row images)7) UtilitarianSmallFlat8) UtilitarianSmallSquare9) UtilitarianSmallRingImage10) UtilitarianLargeFlat11) CircularSmallSimpleImage12) CircularSmallRingImage13) CircularSmallStackImage (line 1)Can anybody please help?

We have created 8 box objects that contain tiles. We have attached the boxes at their outer edges to create an eight sided drum. Six of the eight tiles allow us to expand textures to fill each tile. For the other two tiles, the textures won't expand properly. Any ideas on what we may have missed?? There doesn't seem to be any discernable differences between those two and the other six.