iOS App Testing on Multiple Devices: A Guide

Testing your iOS app on multiple devices is essential for catching layout issues, performance problems, and hardware-specific bugs before release. This guide walks you through the process, from using simulators to physical devices and cloud services, so you can ensure your app works well across the iPhone and iPad lineup.

What You’ll Need

A Mac with the latest version of Xcode installed
An Apple Developer account (free or paid) for physical device testing
One or more physical iOS devices (iPhone, iPad) for real-world testing
A lightning or USB-C cable to connect your devices to the Mac
An active internet connection for cloud testing services (optional)

Step-by-Step

Start with simulators. Open your project in Xcode. In the toolbar, click the scheme dropdown (next to the run button) and select “Edit Scheme…”. Under “Run” > “Info”, set the “Executable” to your app. Then, from the same dropdown, choose “Add Additional Simulators” to open the Devices window. Click the “+” button to add simulators for different iPhone and iPad models. Select a simulator from the dropdown and press Run (⌘R) to build and launch your app.
Test multiple simulator configurations. Run your app on each simulator you added. Pay special attention to different screen sizes (e.g., iPhone SE, iPhone 15 Pro Max, iPad) and orientations. Use the “Device” > “Rotate” menu to test landscape and portrait. Also, simulate different hardware conditions: “Device” > “Shake” for shake gestures, and “Features” > “Touch Pressure” to test 3D Touch (on older models) or Haptic Touch.
Test on physical devices. Connect your iPhone or iPad to your Mac via cable. If prompted, tap “Trust” on the device. In Xcode, open “Window” > “Devices and Simulators”. Your device should appear under “Connected”. If not, click the “+” button at the bottom left and select your device. Then, in the scheme dropdown, select your device name and press Run. You may need to enable Developer Mode on the device (Settings > Privacy & Security > Developer Mode).
Use device-specific features. Physical devices give you access to features simulators can’t emulate: camera, GPS, accelerometer, gyroscope, and push notifications. Test these thoroughly. For example, if your app uses the camera, take photos and videos. For GPS, use the “Features” > “Location” menu in the simulator to simulate locations, but on a real device, walk around or use Xcode’s “Simulate Location” feature (Product > Debug > Simulate Location).
Check performance and memory. Use Xcode’s Instruments (Product > Profile) to monitor CPU, memory, and energy usage. Run the app on both simulators and physical devices. Compare results—simulators use your Mac’s resources, so physical devices may show different performance. Look for memory leaks and high CPU usage that could cause battery drain.
Test on different iOS versions. In the scheme dropdown, select “Edit Scheme…” > “Run” > “Info”. Under “iOS Version”, choose an older version (e.g., iOS 16) to test backward compatibility. For physical devices, you can only test the iOS version they have installed. To test multiple versions, use simulators with different iOS runtimes (download them via Xcode > Settings > Components).
Use cloud testing services. If you don’t have many physical devices, services like Firebase Test Lab or BrowserStack (paid) let you run your app on a wide range of real devices hosted in the cloud. Upload your .ipa file (or build archive) and select the devices you want to test on. These services often provide screenshots and logs, which are great for catching issues you might miss.
Automate UI tests. Write UI tests using XCUITest. In Xcode, create a new UI Test target (File > New > Target > UI Testing Bundle). Write test cases that interact with your app’s interface. Run these tests on multiple simulators using the “Test” button (⌘U). You can also run them on physical devices by selecting a device in the scheme.
Use TestFlight for beta testing. To get real-world feedback, distribute your app via TestFlight. In Xcode, go to Product > Archive, then upload the archive to App Store Connect. From there, you can add testers (up to 100 per build) and invite them to install your app on their devices. This gives you diverse device coverage without needing the hardware yourself.
Monitor crash reports. After testing, check Xcode’s Organizer (Window > Organizer) for crash logs from your devices. Also, use the “Device” > “View Device Logs” option in the Devices window. Address any crashes or exceptions that appear, as they often indicate device-specific issues.

Common Mistakes

Only testing on simulators. Simulators don’t replicate hardware performance, sensor behavior, or memory constraints. Always test on at least one physical device.
Ignoring older devices. Your app may run fine on the latest iPhone but struggle on older models with less RAM or slower processors. Test on the oldest device you can.
Forgetting about iPad multitasking. If your app supports iPad, test Split View and Slide Over. These modes can cause layout issues if your app doesn’t adapt properly.
Not testing in low-power mode. Low Power Mode can throttle CPU and disable background tasks. Enable it on a physical device to see how your app behaves.
Skipping network variations. Test on Wi-Fi, cellular (3G/4G/5G), and offline. Use the Network Link Conditioner (available from Apple’s developer tools) to simulate poor connections.

Tips

Keep a small collection of physical devices that represent different screen sizes and iOS versions—an older iPhone, a newer iPhone, and an iPad cover most bases.
Use the “View” > “Debug Area” > “Simulate Location” in Xcode to test location-based features without moving.
Automate as much as possible with UI tests, but remember that automated tests can’t catch visual glitches—always do a manual pass.
Use the “Accessibility Inspector” in Xcode to check that your app is usable with VoiceOver and other assistive technologies, which can behave differently across devices.
Create a test plan that lists each device and the key features to test. This ensures you don’t miss anything.

Troubleshooting

App won’t install on physical device. Check that your device is connected and trusted. Ensure you have a valid development certificate in Xcode > Preferences > Accounts. Also, verify that the device’s iOS version is supported by your deployment target.
Simulator is slow. Close other apps on your Mac, and try using a simulator with a smaller screen (e.g., iPhone SE) which uses fewer resources. You can also increase the simulator’s allocated memory via “File” > “Simulator Settings” (on newer versions).
UI elements are cut off on a specific device. This is likely an Auto Layout issue. Open the storyboard or SwiftUI preview and check for constraints. Use the “View” > “Debug Area” > “View Debugging” to inspect the view hierarchy.
Performance is poor on a device but fine on simulator. This is common because simulators use your Mac’s CPU. Use Instruments to profile on the physical device and look for inefficient code, such as excessive image processing or network calls on the main thread.
Cloud testing service fails to launch your app. Make sure your app is built as a release build (not debug) and that the .ipa is signed with a distribution certificate. Also, check that your app doesn’t require hardware features that the cloud device lacks (e.g., a specific sensor).

Frequently Asked Questions

Do I need a paid Apple Developer account to test on physical devices?

No. A free personal team account allows you to run your app on your own devices for development. However, to use TestFlight or distribute to other testers, you need a paid account ($99/year).

Can I test on Android devices?

No. This guide is specifically for iOS apps. For Android, you’d use Android Studio and its emulator or physical devices.

How many devices should I test on?

There’s no fixed number, but aim to cover the most common screen sizes and iOS versions. A good starting point is 3-5 devices: one small iPhone (e.g., SE), one standard (e.g., 15), one large (e.g., Pro Max), and one iPad.

What’s the difference between a simulator and an emulator?

In iOS development, a simulator runs your app in a window on your Mac, using your Mac’s hardware. It doesn’t emulate the exact CPU or memory of an iPhone. An emulator (like Android’s) mimics the hardware, but Apple doesn’t provide an emulator for iOS.

How do I test push notifications?

On a physical device, you can send a push notification from your server or use Xcode’s “Simulate Push Notification” feature (Device > Simulate Push Notification) for development. On a simulator, push notifications are supported in newer Xcode versions (Xcode 11.4+), but you need to drag a .apns file onto the simulator.

Can I test on a device with a beta iOS version?

Yes, but it’s risky. Beta versions can have bugs that affect your app, and you might see false failures. It’s best to test on stable iOS versions, and only use beta for compatibility checks if you’re preparing for a new iOS release.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →