Cross-Version Testing for iOS and Android Apps
Our cross-version mobile app testing service ensures compatibility across all supported OS versions. We detect deprecated APIs and prevent compatibility issues before release. Our mobile app compatibility testing covers both iOS and Android. You updated compileSdkVersion to 35, but kept minSdkVersion at 26. A week later in production on Android 10, a NoSuchMethodError crashes. Silent failure due to missing NotificationChannel on Android 7 — users complain about no notifications. Such bugs occur when code uses APIs newer than the minimum OS version. We've encountered this dozens of times and learned to identify these issues before release. Our service — cross-version mobile app testing — ensures all features work correctly on each supported OS version, without UI artifacts or crashes. Order a compatibility audit and get a version matrix in 2 days. With 7+ years of experience and 40+ successful projects, we guarantee thorough testing. Packages start at $999 for a basic compatibility audit, saving you up to $10,000 in potential production fixes.
How to Choose the Version Matrix for Cross-Version Testing?
Testing every OS version is impractical. We use a priority-based approach, leveraging analytics and project requirements.
| Priority | iOS Versions | Android Versions |
|---|---|---|
| Mandatory | Current − 1 (e.g., iOS 17, 18) | Android 12, 13, 14 (API 31–34) |
| Important | minDeploymentTarget (e.g., iOS 15) |
minSdkVersion (e.g., API 26–28) |
| Based on Analytics | Versions with >5% share in your target audience | Same |
Analytics from Firebase or Mixpanel on the os_version field provides the real picture. If 8% of users are on iOS 15 — test that version. If 0.3% are on iOS 14 — skip it. This approach reduces workload without losing quality. Additionally, it's useful to include versions with major API changes — for example, Android 12 (API 31) with the changed exported in intent-filters.
Why Deprecated APIs Are the Main Compatibility Issue?
The gap between minSdkVersion and compileSdkVersion spans about 8 years of API evolution. Miss one deprecated replacement — and the app crashes on older versions. We systematically catch such issues with static analysis and targeted testing.
Android: Three Common Pitfalls
Common API Issues by Android Version
Notifications (API 26+). On Android 8+, all notifications require a NotificationChannel. Without it, notify() is silently ignored. Code check:
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) { val channel = NotificationChannel(CHANNEL_ID, "General", NotificationManager.IMPORTANCE_DEFAULT) notificationManager.createNotificationChannel(channel) } Permissions (API 33+). READ_EXTERNAL_STORAGE is replaced by granular READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO. Requesting the old permission on Android 13 grants no media access.
Foreground Service (API 34+). Android 14 requires specifying the foreground service type (dataSync, mediaPlayback, etc.) — without it, a SecurityException is thrown.
| API | Android Version | Typical Issue |
|---|---|---|
| NotificationChannel | API 26+ | Without channel, notify() is ignored |
| Granular media permissions | API 33+ | READ_EXTERNAL_STORAGE doesn't work |
| Foreground service type | API 34+ | SecurityException without type |
Tool to check: lint with the NewApi rule. It automatically finds API calls above minSdkVersion without @RequiresApi or Build.VERSION.SDK_INT check. Experience shows lint catches 80% of issues before launch.
iOS: @available and #available
if #available(iOS 16.0, *) { NavigationStack { ... } } else { NavigationView { ... } } The compiler warns about using new API without a check — this can be caught statically. But in large codebases, such warnings get lost. The most common victims: ContentUnavailableView (iOS 17), NavigationStack (iOS 16), Charts (iOS 16) — without a fallback, the app crashes with dyld: Symbol not found. More details in the @available documentation.
Tool for iOS: Xcode Simulator
Download additional runtimes: Xcode → Settings → Platforms → + → iOS 15.x Simulator Runtime. After downloading, create a simulator and test on it.
How to Automate Deprecated API Detection?
Static analysis with lint and Xcode Build & Analyze finds incompatibilities 10x faster than manual search. We run it in CI on every PR. For deeper checks, we use Firebase Test Lab — virtual devices with different API levels. It's fast, cheap, and covers most incompatibilities. For example, on one project we found 12 deprecated APIs before release, saving the client over $10,000 in potential production fixes.
How We Test Without Real Devices?
Emulators cover 90% of cases. Real devices are only needed for specific firmware (Samsung, Xiaomi) or hardware features (camera, NFC). We combine:
- In CI: run lint + build with
-Werrorfor iOS. - Smoke tests on emulators with minimum, mid-range, and current OS versions.
- Firebase Test Lab for integration scenarios.
This provides fast feedback without the cost of physical devices. You save on expensive post-release fixes and optimize the testing budget.
Our Process
- Audit current
minSdkVersion/minDeploymentTargetand version distribution analytics. - Compile a supported version matrix with priorities.
- Static analysis for deprecated APIs (lint/Xcode) with a full list of found issues.
- Testing on priority versions (smoke + targeted).
- Report with compatibility matrix and recommendations for fixes.
- Consultation on contentious points and help with code fixes.
Contact us to discuss your app and get a customized test plan. Packages start at $999 for a basic compatibility audit, $1,999 for full version matrix testing.
What's Included
- Documentation: supported version matrix with priorities, list of discovered incompatibilities, fix recommendations.
- Access to Firebase Test Lab reports and CI logs.
- Consultations on code fixes and adaptation for older OS versions.
- Support for 5 business days after report delivery.
Our certified team has over 7 years in mobile development and 40+ tested apps with audiences from 50,000 users. We guarantee accurate results. We'll assess your project in 2 days. Contact us to get a consultation. Order testing and receive a full report with compatibility matrix.