Skip to content

Add test for logging deprecation warning for API 36 #165220

Description

@ash2moon

On this PR: #165195 there were no tests added due to robolectric requiring an update once Android 36 is released.

AC: Add a test for the PR.

Activity

  1. self-assigned this
    on Mar 14, 2025
  2. added
    P2Important issues not at the top of the work list
    on Mar 18, 2025
  3. added
    platform-androidAndroid applications specifically
    engineflutter/engine related. See also e: labels.
    team-androidOwned by Android platform team
    on Nov 7, 2025
  4. self-assigned this
    on Nov 11, 2025
  5. reidbaker commented on Nov 11, 2025

    @reidbaker
    Contributor

    Roboletric should be updated to handle api 36 now (right @jesswrd ?)

  6. jesswrd commented on Nov 11, 2025

    @jesswrd
    Contributor

    Not yet. This has to merge first: flutter/packages#10193. I've been rerunning checks for a week. Basically the upgrade to Robolectric 4.16 (supports api 36) requires Java 21.

    Edit: jk i'm pretty sure you can use robolectric 4.16 in the PR from the issue: #165195. Engine and flutter/flutter are already testing against Java 21. Also it looks like robolectric may have already been updated for this issue here: #175550

  7. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Mar 17, 2026
  8. flutter-triage-bot commented on Mar 17, 2026

    @flutter-triage-bot

    This issue is assigned to @reidbaker but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  9. flutter-triage-bot commented on Jun 2, 2026

    @flutter-triage-bot

    This issue was assigned to @reidbaker but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

  10. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Jun 2, 2026
  11. added a commit that references this issue on Jun 11, 2026
    247ac96
  12. added a commit that references this issue on Jun 26, 2026
    fdce609
  13. github-actions commented on Jul 14, 2026

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  14. locked as resolved and limited conversation to collaborators on Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listengineflutter/engine related. See also e: labels.platform-androidAndroid applications specificallyteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions