document.querySelectorAll('button.load-diff-button').forEach(button => button.click());

via

UIImage.Orientation case labels and integer values:

case up = 0
case down = 1
case left = 2
case right = 3

case upMirrored = 4
case downMirrored = 5
case leftMirrored = 6
case rightMirrored = 7

You don’t need access to the fork. Just fetch it from the main repo using the PR ref. If the PR ref (number) is #3, then fetch pull/3/head like this:

git fetch origin pull/3/head:my_new_branch
git checkout my_new_branch

(via)

This OpenAI API error message:

Error: {
   "param": "messages.[1].content.[1].type",
    "message": "Invalid content type. image_url is only supported by certain models.",
    "code": null,
    "type": "invalid_request_error"
}

… is a (mistaken) catchall that’s likely covering up something else. The API returns this whenever there’s a problem in the image_url field, regardless of your model choice. (Try sending it garbage image data as base64 to test it.)

In Xcode 15.3, gaussian blurs in SVGs are no longer supported and cause a failure at compile time. If you’re getting this error when building, check for SVG files in your asset catalog that include a gaussian blur. Some apps (Sketch) use gaussian blurs for their inner / outer shadows. Discussion

Forking a repository with GitHub doesn’t bring its tags (or releases) along. Here’s how to update your fork with the upstream’s tags. Releases will still be missing. (Adapted from Update git fork with tags.sh)

# Clone your fork of the upstream repo
git clone https://github.com/my_team/my_fork.git
cd my_fork
# Add your fork's upstream as a remote
git remote add upstream https://github.com/upstream_team/upstream_repo.git

# Fetch from upstream
git fetch upstream
# Rebase onto upstream
git rebase upstream/main

# Push to your fork's remote
git push
git push --tags

Logging all available accessibility traits (as of iOS 17):

let accessibilityTraits: [String: Bool] = [
    "a11y_isAssistiveTouchRunning":  UIAccessibility.isAssistiveTouchRunning,
    "a11y_isBoldTextEnabled":  UIAccessibility.isBoldTextEnabled,
    "a11y_isClosedCaptioningEnabled": UIAccessibility.isClosedCaptioningEnabled,
    "a11y_isDarkerSystemColorsEnabled": UIAccessibility.isDarkerSystemColorsEnabled,
    "a11y_isGrayscaleEnabled": UIAccessibility.isGrayscaleEnabled,
    "a11y_isGuidedAccessEnabled": UIAccessibility.isGuidedAccessEnabled,
    "a11y_isInvertColorsEnabled": UIAccessibility.isInvertColorsEnabled,
    "a11y_isMonoAudioEnabled": UIAccessibility.isMonoAudioEnabled,
    "a11y_isOnOffSwitchLabelsEnabled": UIAccessibility.isOnOffSwitchLabelsEnabled,
    "a11y_isReduceMotionEnabled": UIAccessibility.isReduceMotionEnabled,
    "a11y_isReduceTransparencyEnabled": UIAccessibility.isReduceTransparencyEnabled,
    "a11y_isShakeToUndoEnabled": UIAccessibility.isShakeToUndoEnabled,
    "a11y_isSpeakScreenEnabled": UIAccessibility.isSpeakScreenEnabled,
    "a11y_isSpeakSelectionEnabled": UIAccessibility.isSpeakSelectionEnabled,
    "a11y_isSwitchControlRunning": UIAccessibility.isSwitchControlRunning,
    "a11y_isVideoAutoplayEnabled": UIAccessibility.isVideoAutoplayEnabled,
    "a11y_isVoiceOverRunning": UIAccessibility.isVoiceOverRunning,
    "a11y_shouldDifferentiateWithoutColor": UIAccessibility.shouldDifferentiateWithoutColor,
    "a11y_buttonShapesEnabled": UIAccessibility.buttonShapesEnabled,
    "a11y_prefersCrossFadeTransitions": UIAccessibility.prefersCrossFadeTransitions
]

I’d like to add /.well-known/apple-app-site-association to my website, but I can’t, because Webflow doesn’t support it, and I went all-in on Webflow during a Lottie-fueled scrollspy bender a few years ago.

Here’s how to host your AASA file for universal links while using Webflow - by using a worldwide distributed highly javascript available cloud edge application to replace a 355 byte static plaintext file that is requested about once a week by Apple’s CDN.

Use Cloudflare

1. Use Cloudflare for DNS
2. Disable SSL in your Webflow site’s settings - Cloudflare will handle SSL for you now.
3. Enable Cloudflare’s proxying for the apex A record and www CNAME pointing to your Webflow site

Create a route

Allowing Cloudflare to proxy your website means you can intercept and work on requests at specific paths. They call these “routes”.

1. Click your domain
2. Click “Workers Routes”
3. Click “Add route”
4. Enter your route - probably mycoolapp.com/.well-known/*.
5. Leave Worker set to “None” and press “Save”

Create a worker

Still in the Workers Routes screen:

1. Click “Manage Workers”
2. Click “Create Application”
3. Pick one of the templates - doesn’t matter, we’re going to empty it
4. Give it a useful name (“well-known”)
5. Click “Deploy”

Give your worker a script

1. Copy and paste this worker script I made into the Cloudflare editor
2. Edit the appleAppSiteAssociationJSON object - you need to replace the appIDs and add/replace the components
3. Click “Save and deploy”

Assign the worker

1. Tap the Cloudflare logo
2. Tap your domain
3. Tap “Workers Routes”
4. Tap “Edit” next to the route you crated earlier
5. In the “Worker” dropdown, select the “well-known” worker you just created

Testing the route

1. Tap “well-known” in the Worker column
2. Tap “Quick Edit”
3. In the right half of the screen, enter the URL your apple-app-site-association file should live - it’s probably https://mycoolapp.com/.well-known/apple-app-site-association/
4. If you get a 200 OK response, and you can see your AASA JSON content in the response payload, you’re probably good!

Your apple-app-site-association file needs to include a list of appIDs. These app IDs take the form of app-id-prefix.app-bundle-id. You can get the App ID prefix in your Apple Developer account, in “Certificates, Identifiers, & Profiles”. Tap your app’s identifier and you’ll see “App ID Prefix” at the top of the screen.

If you’re setting up Universal Links, you can make debugging easier:

TN3155: Debugging universal links | Apple Developer Documentation

1. Turn on Developer Mode in Settings.
2. In Settings > Developer, scroll to the section labeled Universal Links and turn on Associated Domains Development.
3. Open Diagnostics and type in your full URL. You will receive feedback on whether this link is valid for an installed app.

You can force your app to re-request your apple-app-site-association file every run (or install?), so you don’t have to wait for Apple’s CDN to re-cache it. In your Associated Domains capability, replace your domain definition applinks:mycoolapp.com with applinks:mycoolapp.com/?mode=developer. Documentation: Associated Domains Entitlement

While troubleshooting CloudKit bugs, I came across the excellent post General Findings about NSPersistentCloudKitContainer. I followed their lead and added an observer to NSPersistentCloudKitContainer, and was able to log a lot (a LOT) of CKErrors, but somehow only caught the raw Int values and not the case names.