“build disappears”

Those two architectures are used when building for the iOS simulator (64 and 32 bit). Not sure how to convince a third party framework to not include those slices. Most of the third party code I've used is in source form and is built as part of my app target.

Glad to hear someone else is having this problem too. I thought I was going insane when my iCloud storage was basically empty and I kept having backup problems. Most recently all my backups disappeared like they don't exist but are still taking up my storage.

You must be experiencing JavaScript's garbage collection here. When the immediately invoked closure is cleaned up, the variables created inside are cleaned up as well (and your window goes away, because it has no variable referencing it anymore). To keep the window around, you will need a persistent variable in the global scope (which is why the non-closure version worked for you). You can accomplish this by either having a window variable outside of the closure that you set to an NSWindow inside the closure or declaring the window variable without the var keyword inside the closure (which will declare the window variable in the global scope). Here is code demonstrating these two approaches:var globalWindow = null; (function() { ObjC.import('Cocoa'); // Helper function for window creation function windowWithTitle(title) { var window = $.NSWindow.alloc.initWithContentRectStyleMaskBackingDefer( $.NSMakeRect(0, 0, 800, 400), $.NSTitledWindowMask | $.NSClosableWindowMask | $.NSResizableWindowMask | $.NSMiniaturiz

I would try the Automator app (don't know if you've used it before, but it comes with OS X). You can build up a sequence of automated actions by using the record button. You may have to learn a couple of Applescript basics too. They're both about as accessible to beginners as these things get, but you'll still have to put in some study to get to automate properly - to be honest, even if your list is 200 passwords or more, you'd probably be quicker doing it manually - but learning new skills is a reward in itself, so I don't want to discourage you.Good Luck!

Generally you wouldn't get any beta builds via iTunes.If you already had the beta installed, you would get the subsequent builds Over The Air (Settings > General > Software Update)If not you can laway download the full IPSWhttps://developer.apple.com/ios/download/

I have 2.0 (13S5255d) installed also. they must have tried to put out a repaired build or something.

Short answer is yes, the watch app should disappear when they update the companion iOS app, since it wont support the old watchOS 1.0Long answer, the target or executable for you watch app lives on your phone and is included with the application bundle. So when the companion app is updated the watch app will essentially need to be reinstalled. Since the watch app doesn't include a target for watchOS 1.0 it wont be installed and to the user it will look as if it has been removed from the phone.Personally, I think you should add some type of exception in your watch app that can notifiy that they need to update to watchOS 2.0 to use new features.