|
We just open-sourced some cool poo poo. Check 'em out: https://github.com/facebook/FBRetainCycleDetector https://github.com/facebook/FBAllocationTracker https://github.com/facebook/FBMemoryProfiler
|
#
?
Apr 18, 2016 20:57
|
|
|
|
| # ? May 16, 2024 14:35 |
|
|
 WWDC email is out !
|
|
#
?
Apr 19, 2016 00:43
|
|
|
TheReverend posted:
Who else tried typing into the prompt...
|
|
#
?
Apr 19, 2016 14:54
|
|
|
Mac dev question: is there a way to implement multi-monitor fullscreen for an app? Like the way a flight simulator could span multiple screens?
|
|
#
?
Apr 20, 2016 00:14
|
|
|
Docs for CGLSetFullScreenOnDisplay saysquote:If your application creates a window that completely covers the screen, the system implicitly creates a full-screen instance, for the same potential performance benefit. CGDirectDisplay might be useful: http://cocoadevcentral.com/articles/000028.php Check docs for CGCaptureAllDisplays -[NSView enterFullScreenMode:withOptions:]
|
|
#
?
Apr 20, 2016 00:27
|
|
|
If I write a file to Library/Blah/ on iOS, is this backed up by iCloud? The File System Guide says everything in Library/ except Caches is backed up to iTunes, but it's not clear whether it's also backed up to iCloud.
|
|
#
?
Apr 23, 2016 19:36
|
|
|
I'm not 100% sure of this answer I'm giving, but: yes, it's included.
|
|
#
?
Apr 23, 2016 22:04
|
|
|
A question I'm having a surprisingly difficult time finding an answer to online: We have an online multiplayer game in development (though this question applies just as much to any kind of online service). Our producer is worried about app updates and app reviews: Apple requires applications under review to connect to production servers, but most updates to the game also require significant server-side changes that are incompatible with the current "live" version. So, is it okay if our server detects an "under review" app and redirects to a server instance running a newer server version, which is fully functional but empty of actual users? Then, once the new version is released, we update the actual live game server and upgrade its user database to use the new features. Is this something that can potentially get an app rejected?
|
|
#
?
Apr 26, 2016 08:35
|
|
|
It is not unprecedented to have server behaviour for in-review apps that differs from that of the live version. It would be quite surprising to me if they noticed, likewise if they cared.
|
|
#
?
Apr 26, 2016 08:57
|
|
|
orenronen posted:Is this something that can potentially get an app rejected? As with many things involving the app store, yes, but that doesn't stop tons of people from doing it and getting away with it anyways. As long as it's not egregious and you're pragmatic about it (instead of deceptive or seen as gaming the system), you should be fine.
|
|
#
?
Apr 26, 2016 09:34
|
|
|
Just one question: what happens when not all your users upgrade immediately? Probably better to version the API instead.
|
|
#
?
Apr 26, 2016 15:32
|
|
|
Probably like puzzle and dragons where you're completely blocked until you're current
|
|
#
?
Apr 26, 2016 15:37
|
|
|
Doc Block posted:Just one question: what happens when not all your users upgrade immediately? Or they get directed to the new or old server, since it was keyed on version if I understand OP correctly. It's implicit API versioning really.
|
|
#
?
Apr 26, 2016 17:37
|
|
|
Speaking of, what are people's solutions for versioning APIs? Do you have some URL path component to indicate the version of the API you're trying to use? Do you deploy separate application instances at different roots? Do you wind up changing the old API method in maintenance and produce its output with different means when your backend has changed?
|
|
#
?
Apr 26, 2016 17:45
|
|
|
fleshweasel posted:Speaking of, what are people's solutions for versioning APIs? Do you have some URL path component to indicate the version of the API you're trying to use? This is usually what you do. /api/v1, /api/v2, etc.
|
|
#
?
Apr 26, 2016 19:07
|
|
|
Regular Nintendo posted:Probably like puzzle and dragons where you're completely blocked until you're current Yes - this is a Japanese mobile game, and every other one that I've ever tried blocks you from playing until you upgrade once a new version is out.
|
|
#
?
Apr 26, 2016 22:42
|
|
|
That's pretty standard for games, mobile or otherwise. It's generally considered much less acceptable for anything else. The proper REST way to do API versioning is with a HTTP header because the path should just identify the resource and things like what format you want the resource in go in headers, but in practice that works horribly so no one does it.
|
|
#
?
Apr 26, 2016 22:55
|
|
|
Plorkyeran posted:The proper REST way to do API versioning is with a HTTP header because the path should just identify the resource and things like what format you want the resource in go in headers, but in practice that works horribly so no one does it. People tried to argue with me to change our existing routes to this way a while back and they couldn't provide a single reason why it would actually be better. I'm all for best practices, but it just seemed like work for the sake of work.
|
|
#
?
Apr 26, 2016 23:16
|
|
|
Reminder that any software out of Japan not written for a game console (and much of that which is) is objectively terrible and would be unacceptable as an undergrad homework assignment
|
|
#
?
Apr 27, 2016 00:05
|
|
|
The vast majority of my apps have started crashing on launch. I just counted 57 of them. Clearly this is not due to the apps themselves, unless everyone happened to release apps with the same exact bug in them. Neat. Console logs show me AppleFairplayTextCrypterSession::fairplayOpen() failed, error -42028 followed by a SIGKILL. Googling gives me news articles from 2012 about App Store sending out corrupt binaries, but nothing more recent than that. What the gently caress? These aren't no-name shithouse apps either. Here's some of the apps I'm getting this error on: code:edit: Full console log in case anyone is interested. Fairplay shits itself and sends a SIGKILL. The rest is just the OS bitching it can't attach to the PID or something? code:dc3k fucked around with this message at 20:51 on Apr 27, 2016 |
|
#
?
Apr 27, 2016 20:48
|
|
|
I worked on one of those
|
|
#
?
Apr 27, 2016 20:59
|
|
|
Regular Nintendo posted:I worked on one of those Me too! Also every new app I download crashes on launch in the same fashion. This is stupid.
|
|
#
?
Apr 27, 2016 21:01
|
|
|
Anyone else going to WWDC? I'm going to be a first-timer.
|
|
#
?
Apr 28, 2016 05:01
|
|
|
Plorkyeran posted:That's pretty standard for games, mobile or otherwise. It's generally considered much less acceptable for anything else. I prefer to use Host as the HTTP header for this.
|
|
#
?
Apr 28, 2016 05:08
|
|
|
status posted:The vast majority of my apps have started crashing on launch. Some steps to try fixing it: a) reboot your phone (hold power, slide to shutdown, or just hold power+home) b) sign out and in to the iTunes store, and download a free app or something, to kick Fairplay into redownloading the app decryption key database.
|
|
#
?
Apr 28, 2016 06:21
|
|
|
chimz posted:Some steps to try fixing it: Yeah, rebooting always fixes it (It's happened multiple times before, but not at this level) I'll try signing out and in again next time to see if that does anything.
|
|
#
?
Apr 28, 2016 08:40
|
|
|
dazjw posted:Anyone else going to WWDC? I'm going to be a first-timer. There's usually a group that goes. I missed last year but will be forced back this one. Unfortunately my direct manager is out of San Francisco so there's no chance I get to miss it.
|
|
#
?
Apr 28, 2016 14:40
|
|
|
Re: apps crashing I've been seeing some weird poo poo today too. Cancelled some app store updates after I saw how big they were, my phone blacked out, then showed the no battery screen (it was at 45%), came back to life at 30%. Lots of apps freezing for 5-10sec at a time too. I did a reset/restore last night. Wtf?
|
|
#
?
Apr 28, 2016 23:37
|
|
|
I live here but no luck in the lottery this year. Also put my resume in at Apple a week or two ago and havent gotten a call or thanks for trying. I don't think they like me very much.
|
|
#
?
Apr 28, 2016 23:49
|
|
|
Ender.uNF posted:I live here but no luck in the lottery this year. Also put my resume in at Apple a week or two ago and havent gotten a call or thanks for trying. I don't think they like me very much. The most interesting iOS work is being done at Facebook, not just Apple, in my (highly biased) opinion, so you could try applying here as well?
|
|
#
?
Apr 28, 2016 23:52
|
|
|
Ender.uNF posted:Also put my resume in at Apple a week or two ago and havent gotten a call or thanks for trying. I don't think they like me very much. Well I heard there's a recent position that needs to be filled 
|
|
#
?
Apr 29, 2016 00:34
|
|
|
Doctor w-rw-rw- posted:The most interesting iOS work is being done at Facebook, not just Apple, in my (highly biased) opinion, so you could try applying here as well? I'm looking into it as well. Last time I talked to FB it was "go do code golf and practice writing red-black trees from scratch because we're going to spring a lot of CS101 trivia on you". I may just be projecting though, I never actually did the interview last time because another opportunity came along.
|
|
#
?
Apr 29, 2016 00:46
|
|
|
Ender.uNF posted:I'm looking into it as well. Last time I talked to FB it was "go do code golf and practice writing red-black trees from scratch because we're going to spring a lot of CS101 trivia on you". I may just be projecting though, I never actually did the interview last time because another opportunity came along. The iOS interview track is/was very different and more iOS-heavy.
|
|
#
?
Apr 29, 2016 01:27
|
|
|
Ran into this today:Objective-C code:Compiles and runs fine! It's not super tricky or anything, but it baffled me for a moment.
|
|
#
?
Apr 29, 2016 02:42
|
|
|
pokeyman posted:Ran into this today: I accidentally did the same thing once and scratched my head for a few seconds before I realized what was going on. self.image works by capitalizing the "i" and prepending "set", so it calls [self setImage:nil]. So self.Image does the same thing, just that the "I" was already capitalized. That being said, you'd think the compiler would at least issue a warning if the name used at the call-site doesn't exactly match the name in the @property declaration.
|
|
#
?
Apr 29, 2016 02:51
|
|
|
Flobbster posted:I accidentally did the same thing once and scratched my head for a few seconds before I realized what was going on. self.image works by capitalizing the "i" and prepending "set", so it calls [self setImage:nil]. So self.Image does the same thing, just that the "I" was already capitalized. This code wouldn't work if Obj-C had been designed in Turkey.
|
|
#
?
Apr 29, 2016 02:52
|
|
|
Subjunctive posted:This code wouldn't work if Obj-C had been designed in Turkey. Or it would work in a disastrous way: http://gizmodo.com/382026/a-cellphones-missing-dot-kills-two-people-puts-three-more-in-jail
|
|
#
?
Apr 29, 2016 02:57
|
|
|
Flobbster posted:That being said, you'd think the compiler would at least issue a warning if the name used at the call-site doesn't exactly match the name in the @property declaration. It does indeed emit a warning (and a fix-it), which is great. It was the lack of a crash at runtime that got me. e: Flobbster posted:Or it would work in a disastrous way: http://gizmodo.com/382026/a-cellphones-missing-dot-kills-two-people-puts-three-more-in-jail Holy poo poo! pokeyman fucked around with this message at 03:07 on Apr 29, 2016 |
|
#
?
Apr 29, 2016 03:05
|
|
|
Subjunctive posted:This code wouldn't work if Obj-C had been designed in Turkey.  Flobbster posted:Or it would work in a disastrous way: http://gizmodo.com/382026/a-cellphones-missing-dot-kills-two-people-puts-three-more-in-jail 
|
|
#
?
Apr 29, 2016 04:45
|
|
|
|
| # ? May 16, 2024 14:35 |
|
|
dazjw posted:Anyone else going to WWDC? I'm going to be a first-timer. As you might expect, I'll be there.
|
|
#
?
Apr 29, 2016 05:47
|
|
