Introduction

To paste text into the iOS Simulator, copy it on your Mac and press Cmd+V while a text field inside the simulator has focus. If that does not work, the problem is almost always one of three things: the simulator window does not have focus, the hardware keyboard setting is misconfigured, or the target control in your app is not accepting input. This guide walks through each layer of the paste pipeline and gives you concrete steps to isolate the issue.

How Clipboard Paste Reaches Your Simulator App

The paste path involves three layers:

1. macOS pasteboard stores the copied content.
2. Simulator process bridges the macOS pasteboard to the simulated UIPasteboard.
3. UIResponder chain inside your app determines which control receives the paste action.

A failure at any layer produces the same symptom: nothing happens when you press Cmd+V. Understanding which layer broke determines what to fix.

Baseline Verification Steps

Before investigating your app code, confirm that the simulator itself can paste. This takes about 30 seconds:

1. Copy plain text from any macOS application (TextEdit, Notes, Terminal).
2. Click the simulator window to bring it to the foreground.
3. Open the built-in Notes app or Settings > General > About > Name field.
4. Tap the text field until the cursor appears.
5. Press Cmd+V.

If paste works in a system app, the simulator clipboard bridge is healthy and the issue is in your app. If paste fails even in system apps, the problem is at the simulator level.

Hardware Keyboard Toggle

The most common cause of paste failure is the hardware keyboard setting. When this toggle is in the wrong state, key events from your Mac keyboard may not reach the simulator correctly.

Menu path: I/O > Keyboard > Connect Hardware Keyboard (or press Cmd+Shift+K to toggle).

Try toggling this setting and retesting. Some Xcode versions default to different states, and updating Xcode can change the behavior. If you use a non-US keyboard layout, also check I/O > Keyboard > Use Same Keyboard Layout As macOS to ensure key mappings match.

Menu Paste vs. Shortcut Paste

If Cmd+V does not work but Edit > Paste from the simulator menu bar does work, the issue is keyboard routing, not clipboard content. This distinction matters because:

• Menu paste goes through the simulator's menu responder chain, bypassing keyboard event dispatch.
• Cmd+V goes through the keyboard event pipeline, which can be intercepted by other apps or accessibility features.

Check whether another application (screen recorders, keyboard managers, clipboard managers) is capturing Cmd+V globally.

Debugging Your App's Responder Chain

When paste works in system apps but not in your screen, the issue is inside your UIKit code. Common causes:

The control is not first responder. A UITextField must be the first responder to receive paste actions. If a gesture recognizer, a parent view, or a custom input accessory view is stealing focus, paste silently fails.

The text field delegate is blocking edits. If textField(_:shouldChangeCharactersIn:replacementString:) returns false, the paste action is swallowed.

A custom canPerformAction override disables paste. Some developers override this method to hide the paste menu item, which also blocks Cmd+V.

Build a minimal test screen to confirm baseline behavior:

1import UIKit
2
3final class PasteTestViewController: UIViewController {
4    private let field = UITextField()
5
6    override func viewDidLoad() {
7        super.viewDidLoad()
8        view.backgroundColor = .systemBackground
9
10        field.translatesAutoresizingMaskIntoConstraints = false
11        field.borderStyle = .roundedRect
12        field.placeholder = "Paste here"
13
14        view.addSubview(field)
15        NSLayoutConstraint.activate([
16            field.centerXAnchor.constraint(equalTo: view.centerXAnchor),
17            field.centerYAnchor.constraint(equalTo: view.centerYAnchor),
18            field.widthAnchor.constraint(equalToConstant: 260)
19        ])
20    }
21
22    override func viewDidAppear(_ animated: Bool) {
23        super.viewDidAppear(animated)
24        field.becomeFirstResponder()
25    }
26}

If paste works in this controller but fails in your production screen, the difference is in your custom view hierarchy, gesture recognizers, or delegate logic.

Programmatic Clipboard Verification

You can verify the clipboard bridge programmatically by reading and writing UIPasteboard directly:

1import UIKit
2
3func verifyClipboardBridge() {
4    // Write to pasteboard from simulator
5    UIPasteboard.general.string = "bridge-test-value"
6
7    // Read back
8    if let value = UIPasteboard.general.string {
9        print("Pasteboard read: \(value)")
10    } else {
11        print("Pasteboard read returned nil")
12    }
13}

If reading back returns nil, the simulator-to-host clipboard bridge is broken. If it works but UI paste fails, the problem is in the responder chain.

Pasting into SwiftUI Text Fields

SwiftUI TextField and TextEditor support paste through the same UIPasteboard bridge. If paste fails specifically in SwiftUI, check that you are not applying a .disabled(true) modifier or intercepting the paste with a custom onPasteCommand handler that swallows the input.

1import SwiftUI
2
3struct PasteTestView: View {
4    @State private var text = ""
5
6    var body: some View {
7        TextField("Paste here", text: $text)
8            .textFieldStyle(.roundedBorder)
9            .padding()
10    }
11}

Reset Strategy for Persistent Failures

When clipboard issues persist across all apps in the simulator:

1. Quit Simulator completely (Cmd+Q, not just closing the window).
2. Reopen Simulator and test again.
3. If still broken, use Device > Erase All Content and Settings to reset the simulator.
4. Restart Xcode if the run destination state is stale.

Use the full reset only after simpler checks, because it removes all installed apps and data from that simulator instance.

Clipboard in UI Automation Tests

In XCUITest, the host clipboard is not reliably synced across CI agents. Tests that depend on Cmd+V are inherently flaky in CI environments. Prefer deterministic text entry:

let field = app.textFields["email"]
field.tap()
field.typeText("[email protected]")

If you must test paste behavior specifically, set the pasteboard programmatically within the test process rather than relying on the host OS clipboard:

UIPasteboard.general.string = "test-paste-value"
app.textFields["email"].press(forDuration: 1.0)
app.menuItems["Paste"].tap()

Common Pitfalls

• Assuming paste failure is a code bug when the simulator window does not have focus. Click the simulator window first before pressing Cmd+V.
• Debugging custom view code before verifying that paste works in a system app like Notes. Always validate the baseline first.
• Forgetting that the Hardware Keyboard toggle affects shortcut delivery. This setting can change after Xcode updates.
• Writing UI tests that rely on host clipboard state. These tests pass locally but fail in CI.
• Overlooking canPerformAction(_:withSender:) overrides that disable the paste action on custom text controls.
• Not checking whether a clipboard manager app on macOS is intercepting Cmd+V before it reaches the simulator.

Summary

• Simulator paste depends on three layers: macOS pasteboard, simulator clipboard bridge, and the app responder chain.
• Verify paste in a system app first to determine which layer is broken.
• Toggle the hardware keyboard setting under I/O > Keyboard as a first troubleshooting step.
• Use menu-based paste (Edit > Paste) to distinguish keyboard routing issues from clipboard problems.
• Inspect responder chain, text field delegates, and canPerformAction overrides when only your app fails.
• In UI automation, prefer typeText() over clipboard-dependent paste to avoid CI flakiness.