From cb4f1d8dc7718e2f55436a980f82842207642b9e Mon Sep 17 00:00:00 2001 From: Joshua Higgins Date: Fri, 6 Nov 2026 17:39:28 -0500 Subject: [PATCH] docs: remove Handoff README addition --- apps/mobile/README.md | 31 ------------------------------- 1 file changed, 31 deletions(-) diff --git a/apps/mobile/README.md b/apps/mobile/README.md index 8e33bc2..7fb65bd 100644 --- a/apps/mobile/README.md +++ b/apps/mobile/README.md @@ -42,34 +42,3 @@ Native sharing supplies media titles and artwork through iOS link metadata and A thumbnail, while sharing the original HTTPS URL. Receiving apps control whether they display previews. If artwork cannot load, the URL is still shared. Existing builds without the native sharing module fall back to URL-only sharing. - -### Apple Handoff - -The native app advertises the current album, artist, or playlist screen using -`NSUserActivity`, with the custom activity type `.media`. -Leaving these screens or signing out invalidates the activity. Only the media -route and source server address travel with it, with no playback, queue, tokens, -or web URL. Receiving compares the source with the configured server and uses -the existing navigation and sign-in flow. A missing or different configured -server shows "This activity belongs to a different oTunes server." Setup is -never prefilled or switched by Handoff. - -This repository has one UIKit-based Expo app, not a separate AppKit or Mac -Catalyst target. On macOS this implementation covers the iPhone/iPad app running -on Apple silicon, if the signed app is made available there. The same native -subscriber publishes and receives on that runtime. Intel Macs and a standalone -AppKit app are not supported by this app architecture. - -Install a new native build on each device. Apps must be signed with the same -Apple developer Team ID and declare the same activity type. Variants deliberately -use different activity types so development, preview, and production do not -continue each other's activities. Self-hosters need no associated domains, AASA -files, per-server signing configuration, or web Handoff. Server addresses are -used only for comparison on receipt. - -Apple also requires nearby devices signed into the same Apple Account, Handoff -enabled, and Wi-Fi and Bluetooth enabled. See Apple's -[Handoff implementation requirements](https://developer.apple.com/documentation/foundation/implementing-handoff-in-your-app). -Verify on physical devices in both directions, including a cold launch, signed-out -receipt, a different configured server, and leaving a media screen. A simulator -or a TypeScript check cannot establish that cross-device Handoff works.