You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dfa60bf
Browse filesBrowse the repository at this point in the historyBrowse files
docs: iPhone 16 Pro Max and the gpu1 runner type were removed on 9 No… (#161)
* docs: iPhone 16 Pro Max and the gpu1 runner type were removed on 9 November 2026
A usage check found that iPhone 16 Pro Max and the gpu1 runner type each
carry less than 1% of 7-day usage, so under the support policy they were
removed on 9 November 2026. iPhone 16 Pro still carries more than 1%, so
it stays, deprecated, with removal now targeted for 7 December 2026,
subject to change based on usage. iOS 17, Pixel 7 and Maestro 2.2.0 are
not changed here.
- Devices & OS Versions: the iPhone 16 Pro Max row is gone. The
deprecation warning names only iPhone 16 Pro and its new target date,
and a removal sentence says runs that target iPhone 16 Pro Max are
rejected and where to move them: iphone-16 (the default), iphone-17,
iphone-air, iphone-18-pro or iphone-18-pro-max.
- Runner Type: the gpu1 row is gone, and the warning says it was removed
and that Android runs which still pass it, per upload or per flow, run
on cpu1 at the standard Android rate rather than failing (iOS still
rejects it). The limitations no longer mention gpu1. This also drops a
stray "|" after the old warning's closing ":::".
- Concurrency: the gpu1 column is gone, and the warning says its runs
now count towards the cpu1 limit.
- Billing, README, GitHub Actions, EAS Workflows, Bitbucket Pipelines,
Google Play APIs, Per-flow Devices and the MCP tools page no longer
offer gpu1 or iphone-16-pro-max. iphone-16-pro stays, deprecated.
* docs: iOS 17, Pixel 7 and Maestro 2.2.0 removals now targeted for 23 November 2026
iOS 17, Pixel 7 and Maestro 2.2.0 were targeted for 9 November 2026, subject to usage. All three were still over 1% on the 2026-11-06 check, so their removal is now targeted for 23 November 2026.
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ For most projects, yes. The CLI mimics the Maestro Cloud API, so you change `mae
68
68
69
69
### How much does it cost?
70
70
71
-
DeviceCloud bills per test run i.e. a single top-level flow on a single device and are charged at $0.11 for standard iOS and $0.09 for standard Android. iPad, iPhone Duo, Pixel 10 Pro Fold, Google Play, tablet and `m4`, `m1`and `gpu1` (deprecated) runner flows are charged at the advanced rate of $0.15. New accounts get $20 of free credits. The Pro and Max plans include a set amount of usage each month, and usage beyond that is billed as [overage](billing/overage.md), up to a limit you control. See [Test Run Billing](billing/test-run-billing.md).
71
+
DeviceCloud bills per test run i.e. a single top-level flow on a single device and are charged at $0.11 for standard iOS and $0.09 for standard Android. iPad, iPhone Duo, Pixel 10 Pro Fold, Google Play, tablet and `m4`and `m1` runner flows are charged at the advanced rate of $0.15. New accounts get $20 of free credits. The Pro and Max plans include a set amount of usage each month, and usage beyond that is billed as [overage](billing/overage.md), up to a limit you control. See [Test Run Billing](billing/test-run-billing.md).
Copy file name to clipboardExpand all lines: billing/test-run-billing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Details of charges made to your account can be found on the [billing page](https
17
17
| Standard iOS | Any iPhone device (except the iPhone Duo) on our default [runner type](../configuration/runner-type.md)| $0.11 |
18
18
| Advanced iOS | Any runs on our `m4`[runner type](../configuration/runner-type.md), and any iPad or iPhone Duo runs (on either runner). | $0.15 |
19
19
| Standard Android | Any non-Play Pixel phone (except the Pixel 10 Pro Fold) on our cpu1 [runner type](../configuration/runner-type.md)| $0.09 |
20
-
| Advanced Android | Any runs on our `m1`and `gpu1` (deprecated) [runner types](../configuration/runner-type.md), and any Tablet, Pixel 10 Pro Fold or Play device runs | $0.15 |
20
+
| Advanced Android | Any runs on our `m1`[runner type](../configuration/runner-type.md), and any Tablet, Pixel 10 Pro Fold or Play device runs | $0.15 |
21
21
22
22
::: info
23
23
Enterprise customers with volume discounts or grandfathered users with older pricing may have different pricing. You can view your account's test run cost in the [billing page](https://console.devicecloud.dev/billing)
Copy file name to clipboardExpand all lines: ci-cd/bitbucket-pipelines.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Most pipe variables map to the [`dcd cloud`](../cli/dcd-cloud.md) CLI flag of th
74
74
| `ASYNC` | `"true"` to fire-and-forget. |
75
75
| `CANCEL_PREVIOUS` | `"true"` to cancel the previous run's still-queued tests when this one starts (from pipe 1.5.0). See [Cancelling superseded runs](../advanced/cancel-previous.md). |
76
76
| `PRIORITY` | `low`, `normal` (default) or `high` (from pipe 1.6.0). Reorders only your organisation's own queued runs, see [Run Priority](../configuration/run-priority.md). |
77
-
| `RUNNER_TYPE` | `default`, `cpu1`, `gpu1` (deprecated), `m1` or `m4`. `gpu1`, `m1` and `m4` are premium runners, see [Runner Type](../configuration/runner-type.md). |
77
+
| `RUNNER_TYPE` | `default`, `cpu1`, `m1` or `m4`. `m1` and `m4` are premium runners, see [Runner Type](../configuration/runner-type.md). |
78
78
| `RENDER_ENGINE` | Android only: `lavapipe`or `swiftshader`, the software renderer the emulator boots with on the default Android runner. Leave unset to let DeviceCloud choose (`swiftshader` for apps built with Flutter, otherwise `lavapipe`). |
Copy file name to clipboardExpand all lines: configuration/google-play-apis.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,9 +55,9 @@ Google Play APIs are available on these devices:
55
55
|`pixel-10`|`36`, `37`|
56
56
|`pixel-7` (deprecated) |`34`|
57
57
58
-
Pixel 7 is targeted for removal on 9 November 2026, subject to change based on usage, so move Google Play runs to `pixel-8` (to stay on API 34) or `pixel-10`.
58
+
Pixel 7 is targeted for removal on 23 November 2026, subject to change based on usage, so move Google Play runs to `pixel-8` (to stay on API 34) or `pixel-10`.
59
59
60
-
On the `m1`[runner type](runner-type.md), Google Play is available on `pixel-8` (API `34`) and `pixel-10` (API `36`, `37`). It isn't available on `gpu1`.
60
+
On the `m1`[runner type](runner-type.md), Google Play is available on `pixel-8` (API `34`) and `pixel-10` (API `36`, `37`).
61
61
62
62
Pass the device and API level together on Google Play runs:
63
63
@@ -95,7 +95,7 @@ env:
95
95
### What to check
96
96
97
97
***arm64-v8a native code.** The `m1` emulators run arm64-v8a code only. If your APK ships native libraries, it must include arm64-v8a ones. A build cut down to `x86_64` for emulators won't install, so DeviceCloud rejects `m1` runs for it with an error saying so. Builds with no native code run as they are.
98
-
***Devices.** Google Play on `m1` runs on `pixel-8` (API `34`) and `pixel-10` (API `36`, `37`). Pixel 7 isn't offered on `m1`, because it is removed on 9 November 2026.
98
+
***Devices.** Google Play on `m1` runs on `pixel-8` (API `34`) and `pixel-10` (API `36`, `37`). Pixel 7 isn't offered on `m1`, because its removal is targeted for 23 November 2026.
99
99
***Concurrency.** Google Play runs on `m1` count towards your `m1` limit, not your `cpu1` limit. [Concurrency Protection](../getting-started/concurrency-and-parallel-runs.md) doesn't cover `m1`.
100
100
101
101
Google Play images work the same way on both runner types: they come with Google Play Services and the Play Store, the price is the same, and they can't be rooted, so the [device date and time override](device-datetime.md) isn't applied.
Copy file name to clipboardExpand all lines: configuration/maestro-versions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ We currently support the following versions of Maestro:
21
21
* 2.12.1
22
22
23
23
::: warning
24
-
Maestro 2.2.0 is deprecated and we're targeting removal on 9 November 2026. This date is subject to change based on usage. If you pin `--maestro-version` to 2.2.0, move it to 2.6.1 or newer (the default is 2.10.0). See the [Maestro Support Policy](maestro-versions.md#maestro-support-policy) for more information.
24
+
Maestro 2.2.0 is deprecated and we're targeting removal on 23 November 2026. This date is subject to change based on usage. If you pin `--maestro-version` to 2.2.0, move it to 2.6.1 or newer (the default is 2.10.0). See the [Maestro Support Policy](maestro-versions.md#maestro-support-policy) for more information.
25
25
:::
26
26
27
27
Maestro 2.0.4, 2.0.9, 2.1.0, 2.5.0, 2.5.1 and 2.6.0 were removed on 19 October 2026. Runs pinned to these versions are rejected.
Copy file name to clipboardExpand all lines: configuration/per-flow-devices.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ iPhone upload charges that one flow at the advanced rate, and the rest at the st
60
60
61
61
- You cannot target across platforms in the same upload.
62
62
63
-
- On the `m1`and `gpu1`[runner types](runner-type.md), a flow's device must be on API level 34 or above (up to 37 on `m1`). Google Play is available on `m1`only, on `pixel-8` (API 34) and `pixel-10` (API 36, 37). Generic Tablet isn't available on them.
63
+
- On the `m1`[runner type](runner-type.md), a flow's device must be on API level 34 to 37. Google Play is available only on `pixel-8` (API 34) and `pixel-10` (API 36, 37), and Generic Tablet isn't available.
`gpu1`is deprecated and **will be removed on 9 November 2026**. From that date, runs that pass `--runner-type gpu1` will run on `cpu1` instead, at the standard Android rate, rather than failing. To move now, stop passing `--runner-type gpu1` (Android runs use `cpu1` by default) or pass `--runner-type cpu1`. See the [Runner Type Support Policy](#runner-type-support-policy) for more information.
35
-
:::|
33
+
The `gpu1`runner type was removed on 9 November 2026. Android runs that still pass `--runner-type gpu1`, or set it with `DEVICECLOUD_OVERRIDE_RUNNER_TYPE`, run on `cpu1` instead, billed at the standard Android rate. They don't fail. On iOS, `gpu1` is still rejected. Stop passing `gpu1`: Android runs use `cpu1` by default, or you can pass `--runner-type cpu1`. See the [Runner Type Support Policy](#runner-type-support-policy) for more information.
34
+
:::
36
35
37
36
::: info
38
37
**Google Play runs move to `m1` on 14 December 2026.** From that date every Google Play run uses `m1` rather than `cpu1`, at the same price. To test your app on `m1` now, add `--runner-type m1` to your Google Play runs. See [Moving to Apple Silicon](google-play-apis.md#moving-to-apple-silicon-m1).
@@ -41,11 +40,11 @@ If your app or test is struggling with the default runner types, you can try the
41
40
### Limitations
42
41
43
42
*`m4` is iOS only. Choosing it for an Android app is rejected.
44
-
*`cpu1`, `m1`and `gpu1` are Android only. On iOS, `m1` is treated as `default` (with a warning), and `cpu1`and `gpu1` are rejected.
45
-
* On `m1` and `gpu1`, every flow must run on API level 34 or above (up to 37 on `m1`). This includes devices chosen per flow or in a [device matrix](device-matrix.md).
46
-
* Google Play is available on `m1` on `pixel-8` (API 34) and `pixel-10` (API 36, 37), and not on `gpu1`. See [Google Play APIs](google-play-apis.md#device-availability).
43
+
*`cpu1`and `m1` are Android only. On iOS, `m1` is treated as `default` (with a warning), and `cpu1`is rejected.
44
+
* On `m1`, every flow must run on API level 34 to 37. This includes devices chosen per flow or in a [device matrix](device-matrix.md).
45
+
* Google Play is available on `m1` on `pixel-8` (API 34) and `pixel-10` (API 36, 37). See [Google Play APIs](google-play-apis.md#device-availability).
47
46
*`m1` runs arm64-v8a code only. An APK with native libraries must include arm64-v8a ones, otherwise the run is rejected.
48
-
* Generic Tablet isn't available on `m1` or `gpu1`, so don't select it with those runner types.
47
+
* Generic Tablet isn't available on `m1`, so don't select it with that runner type.
| Max | up to 20, with 1 protected | up to 5 | up to 20, with 1 protected | up to 20 |
13
13
14
14
::: warning
15
-
The `gpu1` runner type is deprecated and will be removed on 9 November 2026, after which its runs use`cpu1` and count towards the `cpu1` limit. See [Runner Type](../configuration/runner-type.md).
15
+
The `gpu1` runner type was removed on 9 November 2026. Runs that still pass it run on`cpu1` and count towards the `cpu1` limit. See [Runner Type](../configuration/runner-type.md).
0 commit comments