Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
Doctor w-rw-rw-
Jun 24, 2008

Subjunctive posted:

I thought the good doctor would beat me to it, but: the Paper team's AsyncDisplayKit is released at last. http://asyncdisplaykit.org/
Oops. Clearly, I'm not doing a good enough job shilling for Facebook iOS.

The next release of my employer's app is going to include it, probably also along with a engineering blog post. Huuuuuuuuuge performance win, especially on the iPhone 4.

Adbot
ADBOT LOVES YOU

ultramiraculous
Nov 12, 2003

"No..."
Grimey Drawer

Subjunctive posted:

I thought the good doctor would beat me to it, but: the Paper team's AsyncDisplayKit is released at last. http://asyncdisplaykit.org/

It caused Gruber say a nice thing about Facebook.

Doh004
Apr 22, 2007

Mmmmm Donuts...
Holy poo poo the "Debug View Hierarchy" in iOS8 is fan loving tastic.

lord funk
Feb 16, 2004

Doh004 posted:

Holy poo poo the "Debug View Hierarchy" in iOS8 is fan loving tastic.

Really? I think it's hugely under-featured compared to Reveal.

Simulated
Sep 28, 2001
Lowtax giveth, and Lowtax taketh away.
College Slice

lord funk posted:

Really? I think it's hugely under-featured compared to Reveal.

Don't forget SparkInspector which is similar to Reveal.

Doh004
Apr 22, 2007

Mmmmm Donuts...
Oh it is, but I was debugging something and accidently hit the button (not knowing what it was) and was surprised to see it. I remember trying out Reveal a while back and really liking it, just never got around to buying.

PleasureKevin
Jan 2, 2011

What good beginner or intermediate Apple development in Swift books are there on iBooks Store?

Doc Block
Apr 15, 2003
Fun Shoe
Apple has an official one. But trying to learn Swift hasn't given me much pleasure, Kevin.

PleasureKevin
Jan 2, 2011

Since yesterday I can't select any scheme in Xcode except My Mac. Probably something to do with the update of Xcode Command Line Tools and maybe some other stuff. I was on RC 3 before, but not beta Xcode.

EDIT: Actually, only appears in one project, so maybe unrelated to any update.

EDIT 2: Clicked [App Name] > Manage Schemes > Autocreate Schemes, then App Name > [Autocreated Scheme Name]

PleasureKevin fucked around with this message at 21:16 on Oct 17, 2014

Doc Block
Apr 15, 2003
Fun Shoe
Any ideas when XCode 6.1 will be available? Trying to download it from developer.apple.com just links to the Mac App Store, which only has XCode 6.0.1. v:shobon:v

edit: I'm guessing Monday, since it has the iOS 8.1 SDK.

Doc Block fucked around with this message at 21:23 on Oct 17, 2014

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

PleasureKevin posted:

Since yesterday I can't select any scheme in Xcode except My Mac. Probably something to do with the update of Xcode Command Line Tools and maybe some other stuff. I was on RC 3 before, but not beta Xcode.

EDIT: Actually, only appears in one project, so maybe unrelated to any update.

EDIT 2: Clicked [App Name] > Manage Schemes > Autocreate Schemes, then App Name > [Autocreated Scheme Name]

Yeah that's usually indicated a scheme issue or a build settings issue for me in the past.

Doc Block posted:

Any ideas when XCode 6.1 will be available? Trying to download it from developer.apple.com just links to the Mac App Store, which only has XCode 6.0.1. v:shobon:v

edit: I'm guessing Monday, since it has the iOS 8.1 SDK.

That's my guess too. The copy here changed recently to "Available Shortly".

brap
Aug 23, 2004

Grimey Drawer
Swift has rough edges still and I think they're noting where the gaps are in the standard library. But it's a good language innately and getting better. I am definitely looking forward to some quality of life features like refactoring and smarter error messages.

edit: How can I view the state of local variables more effectively when I hit a breakpoint? Most of the poo poo I see in the watch window at the bottom just doesn't help-- it doesn't display values meaningfully. I can add print statements to get more sometimes, but goddamn if that's not primitive. Is there a correct way to do this that I'm missing?

brap fucked around with this message at 01:22 on Oct 18, 2014

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.
I think I was in here awhile back asking about the status bar in the iOS Simulator and such. SimulatorStatusMagic is the repo with the answers, for all y'all who were at the edge of your seats.

fleshweasel posted:

edit: How can I view the state of local variables more effectively when I hit a breakpoint? Most of the poo poo I see in the watch window at the bottom just doesn't help-- it doesn't display values meaningfully. I can add print statements to get more sometimes, but goddamn if that's not primitive. Is there a correct way to do this that I'm missing?

I haven't figured it out. I've also noticed that let is often a synonym for "never show me in the debugger".

lord funk
Feb 16, 2004

pokeyman posted:

I haven't figured it out. I've also noticed that let is often a synonym for "never show me in the debugger".
This sounds like a Text from Xcode. "YOU SHOULD KNOW ALREADY jeez."

brap
Aug 23, 2004

Grimey Drawer
Which event should I be handling if I want to perform an action when the user is switching away from my app? Or do I need to find an earlier opportunity to do that? I just want to put off updating NSUserDefaults until the user is switching away from my app.

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.
Why do you want to delay that?

Anyway, assuming iOS you want one of the UIApplication notifications like UIApplicationDidEnterBackgroundNotification.

brap
Aug 23, 2004

Grimey Drawer
Well, I clearly need to figure out the correct method of persistence here. I am keeping a list of the user's favorite bus stops. So during use I want to just keep a static list of strongly typed objects.

When the app goes to the background or gets killed I want the unique IDs of the bus stops to get saved so I can look them up again.

I also have an app extension I'm working on where I want to obtain this list of IDs and look up the arrival times to show in the Today view.

Doc Block
Apr 15, 2003
Fun Shoe
Well, you could do it by listening to the appropriate UIApplication notification as mentioned above, but I'm not sure if the user prefs are the right place to store them, and only saving when the user switches away could mean data loss if your app crashed.

Better would be to have a database that was saved every time the user added a new bus stop.

Also, by "strongly typed" do you mean strong reference?

brap
Aug 23, 2004

Grimey Drawer
I mean a type I've defined as opposed to a NSDictionary or something. I can't seem to figure out how to store Swift objects in NSUserDefaults.

I would like to find out how to properly keep this data, keeping in mind that my Today extension needs to access it as well. That's why I've been using the App Groups functionality. Also keep in mind that all I'm keeping track of at this point is a list of 20 or fewer integers.

I'm going to go ahead and have NSUserDefaults synchronize every time the favorites list is changed.

brap fucked around with this message at 20:15 on Oct 18, 2014

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.
User defaults might be easier than file coordination, but yeah it's not really appropriate for this. You probably want to dump a plist to the app container (NSArray's writeToURL: methods) and use NSFileCoordinator to avoid races.

Whether you stick to user defaults or move elsewhere, the basic idea is the same and you have some options. Saving when the app resigns active would be fine. You could save every few seconds if there's been any changes. You could save in a background queue so the main thread doesn't block.

I might start with just saving after every change, then scale up my tests and see how far that takes me with acceptable performance.

edit:

fleshweasel posted:

I mean a type I've defined as opposed to a NSDictionary or something. I can't seem to figure out how to store Swift objects in NSUserDefaults.

User defaults only works with objects that work in property lists. Convert your Swift types to plist types.

quote:

I'm going to go ahead and have NSUserDefaults synchronize every time the favorites list is changed.

I don't think synchronize is needed or helpful as of iOS 8.

pokeyman fucked around with this message at 20:22 on Oct 18, 2014

Hughlander
May 11, 2005

Really long shot but anyone see this before? We've occasionally had a crash in our test infrastructure in the process 'python' of all things. Did some refactoring and managed to catch it:

code:
Removing named pipe at `/var/folders/69/_9s_j8ns097dmrjqgnsvy7h40000gn/T//ios-sim-stderr-pipe-1413596471'
Removing named pipe at `/var/folders/69/_9s_j8ns097dmrjqgnsvy7h40000gn/T//ios-sim-stdout-pipe-1413596471'
osascript -e 'tell app "iPhone Simulator" to quit'
osascript -e 'tell app "iOS Simulator" to quit'

////////////////////////////////////////////////////////////////////////////////
/Users/macmini/Library/Logs/DiagnosticReports/python_2014-10-17-184149_supersecretmachine.crash
////////////////////////////////////////////////////////////////////////////////
Process:         python [68080]
Path:            /usr/bin/python
Identifier:      python
Version:         ???
Code Type:       X86-64 (Native)
Parent Process:  sh [68079]
Responsible:     [b]launchd_sim[/b] [68038]
User ID:         501

Date/Time:       2014-10-17 18:41:49.554 -0700
OS Version:      Mac OS X 10.9.2 (13C1021)
Report Version:  11
Anonymous UUID:  C090D86F-EBE3-76E4-D0E3-8B6B23E3DE99


Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Symbol not found: _objc_isAuto
  Referenced from: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
  Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libobjc.A.dylib
 in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

Binary Images:
       0x1089f1000 -        0x1089f2ff7  libSystem.B.dylib (1197.1.1) <5292BF21-9406-32D5-8BB3-7DD02C672FA0> /usr/lib/libSystem.B.dylib
       0x1089ff000 -        0x108a41ff7  libauto.dylib (185.5) <F45C36E8-B606-3886-B5B1-B6745E757CA8> /usr/lib/libauto.dylib
       0x108a5a000 -        0x108a5bff7  libDiagnosticMessagesClient.dylib (100) <4CDB0F7B-C0AF-3424-BC39-495696F0DB1E> /usr/lib/libDiagnosticMessagesClient.dylib
       0x108a64000 -        0x108c67ff7 +libicucore.A.dylib (511.23.6) <5F1FFC56-6EA1-3365-80D8-A46AAAFA71A5> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libicucore.A.dylib
       0x108d0d000 -        0x108eb9d57 +libobjc.A.dylib (627.6) <A9EBDDF6-50B7-3B04-8C6F-73818347F23F> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libobjc.A.dylib
       0x108edc000 -        0x108eeeff7 +libz.1.dylib (53) <F8673CFA-B03D-3412-905A-066EF1DEC3AB> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libz.1.dylib
       0x108ef6000 -        0x108f60fff +libc++.1.dylib (230) <7F78297D-FC6D-3DE5-A1E0-A01C349C8DD8> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libc++.1.dylib
       0x108fb9000 -        0x108fe3fff +libc++abi.dylib (114) <1B93F9EE-48F6-3F56-93A1-AF5CBDFB1830> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libc++abi.dylib
       0x108ff3000 -        0x10902ffff +libSystem.dylib (111.10.5) <E906B701-0FFD-3D5F-AC0E-157F0B6C5F5E> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libSystem.dylib
       0x10904e000 -        0x109053ff7 +libsystem_override.dylib (111.10.5) <5BE36121-E168-3158-9B2F-9ADE3D446488> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_override.dylib
       0x10905e000 -        0x109063ff7 +libcache_sim.dylib (65) <7FC19C5D-480C-38BC-B65B-EA09C3959328> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libcache_sim.dylib
       0x10906e000 -        0x10907bfff +libcommonCrypto_sim.dylib (60049) <4392AA37-3CFF-311F-B0CA-168DAE830F24> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libcommonCrypto_sim.dylib
       0x10908c000 -        0x1090e1fff +libcorecrypto_sim.dylib (170.2) <939061E1-618D-3E75-AC02-71AE48A3057E> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libcorecrypto_sim.dylib
       0x1090f4000 -        0x1090fbfff +libcompiler_rt_sim.dylib (57) <8F05E0B2-F932-3311-B051-56D1F6E27043> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libcompiler_rt_sim.dylib
       0x109105000 -        0x10910cfff +libcopyfile_sim.dylib (103) <D3629AF6-8B6A-3962-9C84-DB8101F12D37> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libcopyfile_sim.dylib
       0x109118000 -        0x109135fff +libdispatch.dylib (354.10.5) <64987B7A-CBC8-3843-98AC-10898CD6CFB6> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libdispatch.dylib
       0x109155000 -        0x109155ff7 +libdyld_sim.dylib (324.1) <EA7A7D89-DD38-3D92-A0BF-04430617604E> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libdyld_sim.dylib
       0x10915e000 -        0x109164fff +libmacho_sim.dylib (846.2.4) <2A7E82E7-84CD-3F3E-AE3A-4242C15E3B3A> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libmacho_sim.dylib
       0x10916f000 -        0x10917afff +libnotify_sim.dylib (121) <618D4C3F-6963-3E40-93CE-5CD4A039A6B4> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libnotify_sim.dylib
       0x109183000 -        0x109185ff7 +libremovefile_sim.dylib (33) <7FD13C3C-9CCA-35AE-8813-CA6305C46B95> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libremovefile_sim.dylib
       0x10918f000 -        0x109190fff +libsystem_sim_blocks.dylib (64) <C236C86F-5DDA-3AC8-A0D2-3E32CBA24E73> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_blocks.dylib
       0x109198000 -        0x10922bfef +libsystem_sim_c.dylib (1002.10.1) <5A5BF007-3A1D-3B61-9F38-73FAB4DF9264> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_c.dylib
       0x109255000 -        0x10925dfff +libsystem_sim_dnssd.dylib (539.10.1) <DE54BBEA-0371-3DB3-89B6-9F6CAB569735> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_dnssd.dylib
       0x109269000 -        0x109293fff +libsystem_sim_info.dylib (452) <F44DC64A-C2B0-3857-935D-BCADBB20BFAC> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_info.dylib
       0x1092ab000 -        0x1092dafef +libsystem_sim_m.dylib (3061) <7E5FAA2C-A7F5-3ADD-B125-A397941BCE2B> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_m.dylib
       0x1092e6000 -        0x109311fff +libsystem_network.dylib (268.3) <8D7640B7-D62D-313F-81A4-0F0C2EBC3329> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_network.dylib
       0x10932b000 -        0x109331ff7 +libunwind_sim.dylib (59.3) <D4DB76C7-DD7D-3642-9788-04D75E3B9334> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libunwind_sim.dylib
       0x10933d000 -        0x109365fff +libxpc.dylib (330.10.5) <CD688251-B63D-3119-A295-6257D0626A03> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libxpc.dylib
       0x109385000 -        0x109387fff +libsystem_sim_configuration.dylib (615.1) <F75F8F3A-631B-31C1-9F91-1783FB4A1529> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_configuration.dylib
       0x109391000 -        0x1093a4ff7 +libsystem_sim_asl.dylib (224.10.2) <BEAB7FA7-38BA-3F30-B8FF-F7FD4AB03484> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/libsystem_sim_asl.dylib
       0x1093b0000 -        0x1093b3ff7 +libdyld.dylib (239.4) <CF03004F-58E4-3BB6-B3FD-BE4E05F128A0> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/system/host/libdyld.dylib
       0x1093bc000 -        0x1093c2ff7  libsystem_platform.dylib (24.90.1) <3C3D3DA8-32B9-3243-98EC-D89B9A1670B3> /usr/lib/system/libsystem_platform.dylib
       0x1093d9000 -        0x1093f4ff7  libsystem_malloc.dylib (23.10.1) <A695B4E4-38E9-332E-A772-29D31E3F1385> /usr/lib/system/libsystem_malloc.dylib
       0x1093ff000 -        0x109488ff7  libsystem_c.dylib (997.90.3) <6FD3A400-4BB2-3B95-B90C-BE6E9D0D78FA> /usr/lib/system/libsystem_c.dylib
       0x1094b8000 -        0x1094bfff7  libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
       0x1094d2000 -        0x1094d9ff8  liblaunch.dylib (842.90.1) <38D1AB2C-A476-385F-8EA8-7AB604CA1F89> /usr/lib/system/liblaunch.dylib
       0x1094e3000 -        0x1094e4ff7  libsystem_blocks.dylib (63) <FB856CD1-2AEA-3907-8E9B-1E54B6827F82> /usr/lib/system/libsystem_blocks.dylib
       0x1094f0000 -        0x10950cff7  libsystem_kernel.dylib (2422.92.1) <3F649963-7FA1-3201-8FF6-8438A52B9973> /usr/lib/system/libsystem_kernel.dylib
       0x109531000 -        0x109538fff  libcompiler_rt.dylib (35) <4CD916B2-1B17-362A-B403-EF24A1DAC141> /usr/lib/system/libcompiler_rt.dylib
       0x10954a000 -        0x10954fff7  libunwind.dylib (35.3) <78DCC358-2FC1-302E-B395-0155B47CB547> /usr/lib/system/libunwind.dylib
       0x10955b000 -        0x10958afd2  libsystem_m.dylib (3047.16) <B7F0E2E4-2777-33FC-A787-D6430B630D54> /usr/lib/system/libsystem_m.dylib
       0x109599000 -        0x109599ff7  libkeymgr.dylib (28) <3AA8D85D-CF00-3BD3-A5A0-E28E1A32A6D8> /usr/lib/system/libkeymgr.dylib
       0x1095a3000 -        0x1095a8fff  libmacho.dylib (845) <1D2910DF-C036-3A82-A3FD-44FF73B5FF9B> /usr/lib/system/libmacho.dylib
       0x1095b0000 -        0x1095c1ff7  libsystem_asl.dylib (217.1.4) <655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib
       0x1095cb000 -        0x1095f2ffb  libsystem_info.dylib (449.1.3) <7D41A156-D285-3849-A2C3-C04ADE797D98> /usr/lib/system/libsystem_info.dylib
       0x10960d000 -        0x109616ff3  libsystem_notify.dylib (121) <52571EC3-6894-37E4-946E-064B021ED44E> /usr/lib/system/libsystem_notify.dylib
       0x109621000 -        0x109623ff7  libquarantine.dylib (71) <7A1A2BCB-C03D-3A25-BFA4-3E569B2D2C38> /usr/lib/system/libquarantine.dylib
       0x10962f000 -        0x10967dfff  libcorecrypto.dylib (161.1) <F3973C28-14B6-3006-BB2B-00DD7F09ABC7> /usr/lib/system/libcorecrypto.dylib
       0x109694000 -        0x109698ff7  libcache.dylib (62) <BDC1E65B-72A1-3DA3-A57C-B23159CAAD0B> /usr/lib/system/libcache.dylib
       0x1096a3000 -        0x1096adfff  libcommonCrypto.dylib (60049) <8C4F0CA0-389C-3EDC-B155-E62DD2187E1D> /usr/lib/system/libcommonCrypto.dylib
       0x1096c2000 -        0x1096c9ff3  libcopyfile.dylib (103) <5A881779-D0D6-3029-B371-E3021C2DDA5E> /usr/lib/system/libcopyfile.dylib
       0x1096d5000 -        0x1096d6ffb  libremovefile.dylib (33) <3543F917-928E-3DB2-A2F4-7AB73B4970EF> /usr/lib/system/libremovefile.dylib
       0x1096e3000 -        0x1096e5ff3  libsystem_configuration.dylib (596.13) <B51C8C22-C455-36AC-952D-A319B6545884> /usr/lib/system/libsystem_configuration.dylib
       0x1096eb000 -        0x1096f3fff  libsystem_dnssd.dylib (522.90.2) <A0B7CF19-D9F2-33D4-8107-A62184C9066E> /usr/lib/system/libsystem_dnssd.dylib
       0x1096fc000 -        0x1096fdff7  libsystem_sandbox.dylib (278.11) <5E5A6E09-33A9-391A-AB34-E57D93BB1551> /usr/lib/system/libsystem_sandbox.dylib
       0x109706000 -        0x10970aff7  libsystem_stats.dylib (93.90.3) <1A55AF8A-B6C4-3163-B557-3AD25DA643A8> /usr/lib/system/libsystem_stats.dylib
       0x109717000 -        0x109718fff  libunc.dylib (28) <62682455-1862-36FE-8A04-7A6B91256438> /usr/lib/system/libunc.dylib
    0x7fff6be5b000 -     0x7fff6be8e817  dyld (239.4) <2B17750C-ED1B-3060-B64E-21897D08B28B> /usr/lib/dyld

The best part of that of course being that libauto.dylib is pretty much the first lib listed...

Dessert Rose
May 17, 2004

awoken in control of a lucid deep dream...

lord funk posted:

This sounds like a Text from Xcode. "YOU SHOULD KNOW ALREADY jeez."

Thank you for reminding me that I haven't looked at that site in a couple of years. So much queued up hilarity.

It was very cathartic after dealing with Xcode suddenly deciding that my app identifier having capital letters in it meant I needed to either recreate my app ID on the portal or manually migrate all user data to the lowercased version, despite it having been totally fine since February.

Dessert Rose fucked around with this message at 06:13 on Oct 19, 2014

Slamma Jamma!
May 20, 2010

Is this a decent spot to ask some applescript questions?

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

Factory posted:

Is this a decent spot to ask some applescript questions?

Probably your best bet. Fire away!

Slamma Jamma!
May 20, 2010

A year or so back I found a script on the apple forums that would let you input your webmail server info, username, pop vs. imap, etc and skip the setup wizard and just implement this into mail.app.
I recently needed this again, as I tend to setup email accounts for a large amount of my older relatives and their businesses and when updating this to yosemite I ended up breaking the script.
Here is the initial code

code:
 

-- Script to install a new POP (or IMAP) account on Mail
-- This script has only been tested for POP on Leopard
-- Old Mail folders will be renamed if no account is detected
-- Setting delete mail to false is the safest way to start
-- It is more secure to insert passwords when Mail is first used
-- Password for test account is: dumpty
 
-- Mail plist file location:
set plistFile to "~/Library/Preferences/com.apple.mail.plist"
-- For Mountain Lion change the above to:
-- ~/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.Mail.pli st
 
-- Account details:
set accountName to "lavabit"
set accountUser to "humpty"
set accountServer to "lavabit.com"
set accountPort to 995 -- do not quote
set accountSSL to true -- do not quote
set accountType to "pop"
set fullName to "Humpty Dumpty"
set emailAddress to "humpty@lavabit.com"
set deleteMail to false -- do not quote
 
-- Optional SMTP account details - not always easy to add later:
set smtpUser to "humpty"
set smtpServer to "lavabit.com"
set smtpPort to 465 -- do not quote
set smtpSSL to "YES"
set useAuthentication to "YES"
set smtpAuth to "PASSWORD" -- do not change this to your password
 
tell application "Mail"
  if not (first account exists) then
  try
                              do shell script "killall Mail; p=" & plistFile & ";
                              f(){ mv $1 $1-`date +%Y%m%d%H%M%S` || :; }; f ~/Library/Mail; f $p; printf \"
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE plist PUBLIC '-//Apple//DTD PLIST 1.0//EN' 'http://www.apple.com/DTDs/PropertyList-1.0.dtd'>
<plist version='1.0'>
<dict>
<key>MailAccounts</key>
<array>
<dict>
<key>AccountName</key>
<string>delete me</string>
<key>AccountType</key>
<string>POPAccount</string>
</dict>
</array>
</dict>
</plist>
\" >> $p"
  end try
  end if
  set stopScript to false
  if account accountName exists then
                    display dialog "Account '" & accountName & "' already exists. Either backup its emails and delete it or change one of the names." buttons {"Stop script"} with icon stop
  set stopScript to true
  else
  repeat with accountNumber from 1 to count of accounts
  if (user name of account accountNumber = accountUser and server name of account accountNumber = accountServer) then
                                        display dialog "Your existing '" & name of account accountNumber & "' account already has user name '" & accountUser & "' and server name '" & accountServer & "'. Either backup this account's emails and delete it or change one of the above names." buttons {"Stop script"} with icon stop
  set stopScript to true
  return
  end if
  end repeat
  if stopScript is false then
  if accountType = "pop" then
  set alpha to make new pop account with properties {name:accountName, user name:accountUser, server name:accountServer, port:accountPort, uses ssl:accountSSL, full name:fullName, email addresses:emailAddress, delete mail on server:deleteMail}
                              else if accountType = "imap" then
  set alpha to make new imap account with properties {name:accountName, user name:accountUser, server name:accountServer, port:accountPort, uses ssl:accountSSL, full name:fullName, email addresses:emailAddress}
  else
  set stopScript to true
                                        display dialog accountType & " Ensure that 'accountType' is set to \"pop\" or \"imap\"." buttons {"Stop script"} with icon stop
  end if
  if stopScript is false then
                                        if account "delete me" exists then delete account "delete me"
                                        try
                                                  do shell script "killall Mail"
  end try
  end if
  end if
  end if
end tell
if stopScript is false then
  set smtpDetails to {|AccountName|:accountName, |AccountType|:"SMTPAccount", |Hostname|:smtpServer, |SSLEnabled|:smtpSSL, |ShouldUseAuthentication|:useAuthentication, |Username|:smtpUser, |AuthenticationScheme|:smtpAuth, |PortNumber|:smtpPort}
          tell application "System Events"
  tell property list file plistFile
                              tell property list item "DeliveryAccounts"
  make new property list item at beginning with properties {kind:record, value:smtpDetails}
  end tell
  end tell
  end tell
  tell application "Mail"
  set smtp server of alpha to smtp server accountName
  end tell
end if
to my understanding of the script I should only have to update the location of the .plist at the initial part of the code.I went ahead and updated this to the new location of


set plistFile to "~/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.mail.plist”

And now I receive an error when running the script of this:
code:
 error "System Events got an error: Can’t get property list item \"DeliveryAccounts\" of property list file \"~/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.mail.plist\"." number -1728 from property list item "DeliveryAccounts" of property list file "~/Library/Containers/com.apple.mail/Data/Library/Preferences/com.apple.mail.plist”
Any ideas?

Slamma Jamma! fucked around with this message at 19:43 on Oct 19, 2014

Dessert Rose
May 17, 2004

awoken in control of a lucid deep dream...
No, Xcode, you're right. Those simulators were just a waste of space.

Also, definitely don't bother actually creating new ones when I ask. I'd rather stare at a beach ball.

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

Factory posted:

Any ideas?
It sounds like the plist structure might have changed. Maybe you can open up the plist and see what it looks like, maybe comparing it to one on a computer that does work with the script?

I don't know how relevant it is, but I literally just read this blurb about preferences in iOS 8 and OS X 10.10:

quote:

NSUserDefaults Plist Files

The on-disk property list files used by NSUserDefaults have always been a private implementation detail, but in previous releases of iOS, and significantly older releases of Mac OS X, directly modifying them has mostly worked (though there are some potential data-loss issues for applications that do so, even on previous systems). In iOS 8 and later, the NSUserDefaults daemon process (cfprefsd) will cache information from these files and asynchronously write to them. This means that directly modifying plist files is unlikely to have the expected results (new settings will not necessarily be read, and may even be overwritten). You should use the NSUserDefaults or CFPreferences APIs, or (on Mac OS X) the defaults(1) command, to interact with the preferences system.

In case it's unclear, it's saying that manually messing with the plist files might not work right, and you should use either NSUserDefaults (e.g. from a Python script) or the defaults command. I'm not saying rewrite your script, if it seems to work ok, but I thought I'd mention it.

dizzywhip
Dec 23, 2005

Just spent almost an hour thinking I was crazy because none of my log statements would show up until I realized Xcode has been helpfully closing the right panel in the console for me :saddowns:

Slamma Jamma!
May 20, 2010

pokeyman posted:

It sounds like the plist structure might have changed. Maybe you can open up the plist and see what it looks like, maybe comparing it to one on a computer that does work with the script?

I don't know how relevant it is, but I literally just read this blurb about preferences in iOS 8 and OS X 10.10:


In case it's unclear, it's saying that manually messing with the plist files might not work right, and you should use either NSUserDefaults (e.g. from a Python script) or the defaults command. I'm not saying rewrite your script, if it seems to work ok, but I thought I'd mention it.

Yeah, it's doing its job but then erroring on trying to edit the plist. I think that blurb is exactly what the problem is.

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

dizzywhip posted:

Just spent almost an hour thinking I was crazy because none of my log statements would show up until I realized Xcode has been helpfully closing the right panel in the console for me :saddowns:

Oh man. I was working on a keyboard extension and the iOS Simulator will seemingly randomly decide to hide the on-screen keyboard on launch. So I'd hit command-r in Xcode and wait for the keyboard to pop up, assuming something was building or slowly loading or something. I'm sure I spent at least an hour in small chunks waiting for a keyboard that never came.

Doctor w-rw-rw-
Jun 24, 2008

pokeyman posted:

Oh man. I was working on a keyboard extension and the iOS Simulator will seemingly randomly decide to hide the on-screen keyboard on launch. So I'd hit command-r in Xcode and wait for the keyboard to pop up, assuming something was building or slowly loading or something. I'm sure I spent at least an hour in small chunks waiting for a keyboard that never came.

Can't you just toggle the soft keyboard or disable the hardware keyboard?

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

Doctor w-rw-rw- posted:

Can't you just toggle the soft keyboard or disable the hardware keyboard?

Yep. I just kept forgetting, and somehow the simulator would occasionally flip back.

Simulated
Sep 28, 2001
Lowtax giveth, and Lowtax taketh away.
College Slice

fleshweasel posted:

Swift has rough edges still and I think they're noting where the gaps are in the standard library. But it's a good language innately and getting better. I am definitely looking forward to some quality of life features like refactoring and smarter error messages.

edit: How can I view the state of local variables more effectively when I hit a breakpoint? Most of the poo poo I see in the watch window at the bottom just doesn't help-- it doesn't display values meaningfully. I can add print statements to get more sometimes, but goddamn if that's not primitive. Is there a correct way to do this that I'm missing?

You can't! Xcode's debugging is delightfully primitive; they were so proud of the hover over variable names and basic visualizer support a couple of WWDCs ago. I didn't have the heart to tell them that's been in Visual Studio for about 20 years. When I first started learning Apple development stuff I was shocked that debugging wasn't better. It's basically the same today as it was back then around iOS 4.0. It's hilarious when you expand an NSDictionary and get nothing in the variable window. When even basic stuff like that fails just give up and go back to print statements.

I still have to explain crap to the debugger like it rides the short bus. Oh you hate properties? OK, format it as a message send. Oh you can't tell that's a CGRect return type? Here, let me insert a cast.

The Swift debugger is infuriating because it freaks out about the most minor of errors or slight inconsistencies in Swift code and the Objective-C bridging header. Nothing like trying to print a local variable and getting "Unknown type Foo in BlahBlah.h from MyProject-Bridge.h". Really Swift? I don't give a poo poo, that code compiled and I'm running it right now, just print the value of X you rear end in a top hat.

HaB
Jan 5, 2001

What are the odds?

Ender.uNF posted:

You can't! Xcode's debugging is delightfully primitive; they were so proud of the hover over variable names and basic visualizer support a couple of WWDCs ago. I didn't have the heart to tell them that's been in Visual Studio for about 20 years. When I first started learning Apple development stuff I was shocked that debugging wasn't better. It's basically the same today as it was back then around iOS 4.0. It's hilarious when you expand an NSDictionary and get nothing in the variable window. When even basic stuff like that fails just give up and go back to print statements.

I still have to explain crap to the debugger like it rides the short bus. Oh you hate properties? OK, format it as a message send. Oh you can't tell that's a CGRect return type? Here, let me insert a cast.

The Swift debugger is infuriating because it freaks out about the most minor of errors or slight inconsistencies in Swift code and the Objective-C bridging header. Nothing like trying to print a local variable and getting "Unknown type Foo in BlahBlah.h from MyProject-Bridge.h". Really Swift? I don't give a poo poo, that code compiled and I'm running it right now, just print the value of X you rear end in a top hat.

This. So Much This.

I made the jump from the .NET side about 3 years ago, and I was a little startled at xcode's debugger not having some of the most basic features of Visual Studio. Having to NSLog all over the place to see what values are being tossed around makes me feel like I'm writing javascript in 1999 and putting alert() everywhere.

eschaton
Mar 7, 2007

Don't you just hate when you wind up in a store with people who are in a socioeconomic class that is pretty obviously about two levels lower than your own?

Hughlander posted:

Really long shot but anyone see this before? We've occasionally had a crash in our test infrastructure in the process 'python' of all things. Did some refactoring and managed to catch it:

code:

Dyld Error Message:
  Symbol not found: _objc_isAuto
  Referenced from: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
  Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libobjc.A.dylib
 in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

The best part of that of course being that libauto.dylib is pretty much the first lib listed...

This looks like you're trying to run a binary built for OS X against the iOS Simulator framework stack.

HiriseSoftware
Dec 3, 2004

Two tips for the wise:
1. Buy an AK-97 assault rifle.
2. If there's someone hanging around your neighborhood you don't know, shoot him.

HaB posted:

This. So Much This.

I made the jump from the .NET side about 3 years ago, and I was a little startled at xcode's debugger not having some of the most basic features of Visual Studio. Having to NSLog all over the place to see what values are being tossed around makes me feel like I'm writing javascript in 1999 and putting alert() everywhere.

poo poo, I thought Xcode debugging issues was just something that was wrong with my setup and didn't know that it was an epidemic. I'm like "eh, I can't see what's in this NSDictionary, but it's probably something I'm doing wrong" but I guess not.

Visual Studio's STL compile error messages are so incredibly cryptic, but the fact that the debugger lets me see everything in the containers is more than enough consolation.

lord funk
Feb 16, 2004

Speaking of basic editor functionality that sucks in Xcode, can we please get a 'dark mode' for Xcode? I can't stand the fact that the UI stays bright when you switch to a dark editing color scheme. How does anyone like that?

Or is this one of Apple's decisions for me, like how everything in iOS should be white?

Doh004
Apr 22, 2007

Mmmmm Donuts...
Did they open up the internal TestFlight beta testing? It seems like it's open in iTunes Connect.

*edit* Still internal only. Would be cool to get a timeframe as to when external users would be allowed, because we're at our limit.

Can you have an enterprise licensed account as well as have it able to submit apps to the App Store? Or would they have to be two separate accounts? Does Apple care if a company has two separate accounts, one enterprise and one normal?

Doh004 fucked around with this message at 21:09 on Oct 20, 2014

Dessert Rose
May 17, 2004

awoken in control of a lucid deep dream...
Cool Xcode UI design feature:

Send Xcode into fullscreen mode. Note the location of the "Build and Run" shortcut (the far upper left)

Now move your mouse into the upper left hand corner. Notice what is now in that location.

If you bounce your mouse off the top of the screen and then click the button, you'll close the window, even if the animation hasn't finished yet.

Adbot
ADBOT LOVES YOU

pokeyman
Nov 26, 2006

That elephant ate my entire platoon.

Doh004 posted:

*edit* Still internal only. Would be cool to get a timeframe as to when external users would be allowed, because we're at our limit.

I'm hoping the email that went out saying

quote:

iTunes Connect will undergo maintenance on Sunday, October 26, 2014 for approximately six hours starting at 6 a.m. (PT).
is related.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply