Skip to content

Bring back a deprecated AndroidHarness to make it easier to move to 3.10 #2765

Closed

Description

@8Keep

In #2727 AndroidHarness was removed entirely. We should bring back AndroidHarness, based on top of the new fragment code, to allow people to migrate to 3.10 easier, and later fix up their app to not use the deprecated code path on their own time.

Risk: the new migration friendly deprecated AndroidHarness won't be exactly the same as the old code path, though the API should be, so we will need testing from users with real apps.

Activity

  1. self-assigned this
    on May 10, 2026
  2. added this to the v3.10.0 milestone on May 10, 2026
  3. stephengold commented on May 11, 2026

    @stephengold
    Member

    See also issue #2743 .

  4. stephengold commented on Aug 15, 2026

    @stephengold
    Member

    Not resolved as of v3.10.0-beta2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions