I've got an idea for an app, but I'd need the ability to deploy a cert and pin that I can secure in mobile applications. Is there a way to do this at installation time without user intervention beyond access permissions? The idea is to protect, not just obfuscate these resources from determined parties who'd want to extract the cert and pin then use them to simulate valid clients accessing my service.

For example, say I have this switch statement: let foo = bar() switch foo { case foo0: print(foo.description) case foo1: print(foo.name) ... Could it be abbreviated so that I don't have to declare the "let"? switch bar() { case foo0: print($0.description) case foo1: print($0.name) ...

When using the date format "MMMM" our Polish users are seeing incorrect month names. I'm not a native speaker, but was informed iOS is using the wrong possessive tense. The month names should be as below (Jan-Dec): Styczeń Luty Marzec Kwiecień Maj Czerwiec Lipiec Sierpień Wrzesień Październik Listopad Grudzień Can anyone confirm and correct if necessary?

We'd like to generate reports on the number of users who either turn on or off location when prompted by either the OS or our app. Is this possible via Apple Analytics, or is there a programmatic way to accomplish the same thing with a long-lived CLLocationManager?

Context Objective-C code for the most part iOS 14.8 iPhone X Xcode 14.0.1 I have an app that does the following: User visits portrait orientation page Rotating the phone transitions the page to landscape mode. We then hide the first row in a collection view. Tapping a collection view row presents a special landscape VC Tapping a navigation button dismisses the special landscape VC The expected behavior is to reveal the parent landscape VC underneath the special VC. When performing these actions while running the app in Xcode, the application performs as expected and probably has for years. However, when performing the same actions when NOT attached to Xcode, viewWillTransitionToSize() is called with a portrait orientation size which causes the VC to animate and render the parent view incorrectly. I did discover that if I started the app unattached, then "Attach to Process" in Xcode, I can get the same incorrect viewWillTransitionToSize() call to happen.