Uniform Type Identifiers (UTIs) are a standardized way for macOS and iOS applications to identify data types. UTIs are used to identify a wide range of data types, from images and audio files to text documents. UTIs are hierarchical, allowing applications to recognize and work with related data types. Developers can define their own UTIs in their applications to provide better integration with other applications in the ecosystem.
By default, Xcode Server signs binaries using a development certificate, not a distribution one. Unfortunately there is no built-in option to make it use a Developer ID certificate. What’s the solution?
Continuous testing is paramount to ship serous software. Yet continuously running tests is a pensive productivity plight. Is it possible to automate testing? Yes you can.
“I want a REST API for notarization since it’s impossible to parse text coming from the notarization tool reliably.” What if I say that the command line API is the best method for integration with build pipelines? Read on to find out more.
Notarization may take just a few clicks in Xcode, but this takes time and a security risk. You include notarization as part of your continuous delivery pipeline. Here’s how.
Including passwords into the source tree is a big security breach. Similarly including passwords into build jobs would be insecure. Learn how to securely provide Apple ID credentials into notarization jobs.
The App Store Small Business Program offers lowered commission cost with one big caveat: no app transfer. But apps graduating from a “hobby” into a “small business” would definitely involve transferring ownership. Read how to transfer apps without engaging in the app transfer process and losing out on the program’s benefits.
Compiled code can conclude the instruction set through conditional compilation. But what about processor-independent scripts? Finding out the current native processor architecture and emulation status thereof would be very useful in build systems that doesn’t support cross-compilations. Find out how a shell script can find out whether it is running under Apple’s processor, Intel, or emulated.
Publishing similar apps is considered spamming. Yet there are valid reasons to develop multiple apps from the same code base. Here is what you need to know to avoid being labeled as spammer by app reviewers.
It would be a big blow when Apple rejects your suite of apps, call it “spam” and tell you to move into a container app. If this is happening to you, then this article would be a solution to your predicament.
The long-rumored ARM Mac is on the horizon. With this comes the big work of porting and re-compiling current applications. But many Mac App Store apps are dependent on OpenSSL, which doesn’t yet support ARM on the Mac. Here is how you can continue to test your mac app while waiting for official OpenSSL support for the new hardware.
Being a white-label app vendor in Apple’s store is not easy. App Review could label you as a spammer because of a number of similarly-looking template apps and jeopardize your entire developer account.
Testing network I/O code without accessing the backend is not easy. Here is how you can mock the backend by injecting code into the URL Loading System
When a table view asks for a cell, often images in the cell isn’t yet available and needs to be fetched from a server – thus the cell gets a placeholder image. But static placeholders doesn’t look as good as animated ones. Unfortunately cell views gets scrolled off and re-used which makes managing animations challenging.