A native clipboard manager for Mac, iPhone and iPad — privacy notice, support and documentation.
Paste Me for iPhone and iPad ships in the same App Store record as the Mac app (“Paste-Me”, bundle ID com.guy.PasteMe). Using the same bundle ID makes it a Universal Purchase and lets both apps use the same iCloud container and iCloud key-value store, which is what keeps them in sync.
The source is the private Paste_Me_iOS repository (~/git/macosx/Paste_Me_iOS). It has three targets:
| Target | Bundle ID | What it is |
|---|---|---|
| Paste Me | com.guy.PasteMe |
The app |
| PasteMeKeyboard | com.guy.PasteMe.Keyboard |
Paste Me Keyboard (custom keyboard, RequestsOpenAccess) |
| PasteMeShare | com.guy.PasteMe.Share |
Share ▸ Paste Me |
iCloud.com.guy.PasteMe container exists and its CloudKit schema is deployed to Production (submission-guide.md). The iOS app uses exactly the same data model, so no schema change is needed.Xcode’s automatic signing does most of this the first time you build for a device with your team selected. To do it by hand:
group.com.guy.PasteMe.com.guy.PasteMe (shared with the Mac): add App Groups (select group.com.guy.PasteMe). iCloud with CloudKit (iCloud.com.guy.PasteMe) and Push Notifications are already on from the Mac setup.com.guy.PasteMe.Keyboard and com.guy.PasteMe.Share, each with App Groups ▸ group.com.guy.PasteMe.cd ~/git/macosx/Paste_Me_iOS
scripts/build.sh # simulator build, no signing needed
scripts/build.sh test # unit tests on a simulator
Then in Xcode: open PasteMe.xcodeproj, select the Paste Me target ▸ Signing & Capabilities ▸ set your Team (do the same for PasteMeKeyboard and PasteMeShare), choose your iPhone and press ⌘R.
Check on a device:
In App Store Connect ▸ Apps ▸ Paste-Me:
TEAM_ID=ABCDE12345 scripts/build.sh archive
Or in Xcode: destination Any iOS Device (arm64) ▸ Product ▸ Archive ▸ Organizer ▸ Distribute App ▸ App Store Connect ▸ Upload. Automatic signing creates the distribution profiles for the app and both extensions, and switches aps-environment to production.
ITSAppUsesNonExemptEncryption is already false, so export compliance isn’t asked again (export-compliance.md).