User Profile

I can't believe that Xcode requires Catalina starting with 11.4. Are you guys at Apple living under a rock? To enumerate the problems Catalina has would take hours. I can't imagine any technical reasons for forcing Catalina on Xcode, this appears to be pure arbitrariness.Just FYI: I'm not a Facebook engineer, I don't have 10 development machines at my disposal, I have exactly 1 iMac where I write my Apps on and where I do all the other daily stuff with. And given the current state of Catalina, it would be very unwise to upgrade that iMac to Catalina. Consequently I'm stuck at iOS 13.2. Maybe someone at Apple can explain why 13.5 requires Xcode running on Catalina.I know what will be next: if anyone from Apple bothers to respond, the response will look like this: file a radr. Why do they do this? So that the problem can be moved out of the public eye and silently swept under the rug. While this might satifiy some managers, it will not solve the underlying problem: Catalina is not ready for production.To cut off regular customers from a stable OS and force them to use a public Catalina beta is one thing, but forcing developers is IMHO a scandal.

we are supposed to set up our own web server, and install some some unknown software that dynamically creates a JWT token? It would be nice if Apple could at least write some documentation how to achieve this. Until then I will of course store the token in-app, what else am I supposed to do, I'm a developer not a web server admin? Plus: Wasn't the original idea of the app store to avoid the requirement for developers to run their own server infrastructure?we are supposed to write tons of boiler plate code wrapping the whole API into either Objective-C or Swift classes, #defining dozens of API keywords, piping requests into data tasks and results through JSON parsers and create class instances of it, doing the same programming mistakes over and over until maybe some kind soul posts a working solution on github in 6 months? This is just sad and disappointing. This API should be wrapped into code like for example GameKit wraps its web API into Objective-C.

For one of my apps the disk capacity of the device it is running on is important to know, for example iPhone 6 (16GB) or iPhone 7 (128GB). The canonical way to query the disk capacity appears to be through `NSFileManager`. A function that returns the device capacity in GB as an `NSNumber` might look like this :NSNumber * totalDiskSpaceInGb(void) { NSNumber *totalsize = [[NSFileManager.defaultManager attributesOfFileSystemForPath:NSHomeDirectory() error:nil] objectForKey:NSFileSystemSize]; return @(exp2(ilogb(totalsize.doubleValue) - 29)); }This funtion served me well in the last couple of years but occasionally the value returned is off, in both directions, so I ended up detecting an 4 GB iPhone 5c, or a 512 GB iPhone 7.The Settings.app displays the device capacity in General > About. Assuming that the algorithm is not the biggest secret at Apple, may I request how the Settings app calculates that value?

I'm downloading 11.2.1 and it says it fixes a crash in UITextView. Why do we need to download 7.8 gig in order to do this???

I'd like to use CloudKit for my app in order to store data in the public database, which would be pre-loaded by me with around10-20k records prior to app launch, with a fluctuation rate of maybe 200/week going in and out, so the total number is expected to be more or less constant.My question is: how does Apple think a device that comes in say 6 month after app launch is supposed to get the current set of data from the public database??As we all know, the relevant methods that fetch records in bulk and return a serverChangeToken only work on custom zones, which cannot be created in the public db.The only solution right now seems to be: Create a CKQuerySubscription for each record type, and run a CKFetchNotificationChangesOperation (whoch is deprecated, btw) at the apps first launch. Given the fluctuations above, that would mean processing around 5000 notification changes after 6 month for a new device to be up to date, i.e. before the user can do anything with the new app.The only hack that I can think of to work around this problem is to periodically create a snapshot of the data and the serverChangeToken and download that snapshot as a starting point.Does anyone know of a better solution? Thanks in advance for any help, and apologies if this topic has been discussed before.

Wouldn't it be easier to sniff the URL than to reverse-engineer the app?