Skip to content

Update AVD Depedency To Support API 36 #165922

Closed

Description

@jesswrd

Update AVD to depedencies in framework, engine, and packages to one that supports Android 16 (api 36).

Activity

  1. added
    P1High-priority issues at the top of the work list
    team-androidOwned by Android platform team
    on Mar 25, 2025
  2. self-assigned this
    on Mar 25, 2025
  3. Sudhirkumar620617 commented on Mar 26, 2025

    @Sudhirkumar620617

    C:\Users\rahul\AppData\Local\Pub\Cache\hosted\pub.dev\webview_flutter_android-2.10.4\android\src\main\java\io\flutter\plugins\webviewflutter\FlutterAssetManager.java:60: error: cannot find symbol
    final PluginRegistry.Registrar registrar;
    ^
    symbol: class Registrar
    location: interface PluginRegistry
    C:\Users\rahul\AppData\Local\Pub\Cache\hosted\pub.dev\webview_flutter_android-2.10.4\android\src\main\java\io\flutter\plugins\webviewflutter\FlutterAssetManager.java:70: error: cannot find symbol
    RegistrarFlutterAssetManager(AssetManager assetManager, PluginRegistry.Registrar registrar) {
    ^
    symbol: class Registrar
    location: interface PluginRegistry
    C:\Users\rahul\AppData\Local\Pub\Cache\hosted\pub.dev\webview_flutter_android-2.10.4\android\src\main\java\io\flutter\plugins\webviewflutter\WebViewFlutterPlugin.java:63: error: cannot find symbol
    public static void registerWith(io.flutter.plugin.common.PluginRegistry.Registrar registrar) {
    ^
    symbol: class Registrar
    location: interface PluginRegistry
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    3 errors
    3 warnings

    FAILURE: Build failed with an exception.

    • What went wrong:
      Execution failed for task ':webview_flutter_android:compileDebugJavaWithJavac'.

    Compilation failed; see the compiler error output for details.

    • Try:

    Run with --info option to get more log output.
    Run with --scan to get full insights.

    BUILD FAILED in 2m 17s
    Running Gradle task 'assembleDebug'... 139.4s

    ┌─ Flutter Fix ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │ [!] Consult the error logs above to identify any broken plugins, specifically those containing "error: cannot find symbol..." │
    │ This issue is likely caused by v1 embedding removal and the plugin's continued usage of removed references to the v1 embedding. │
    │ To fix this error, please upgrade your current package's dependencies to latest versions by running flutter pub upgrade. │
    │ If that does not work, please file an issue for the problematic plugin(s) here: https://github.com/flutter/flutter/issues │
    └─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
    Error: Gradle task assembleDebug failed with exit code 1

  4. jesswrd commented on Apr 10, 2025

    @jesswrd
    ContributorAuthor

    @Sudhirkumar620617 Can you provide some context to the error you are seeing and why you think it's related to updating the AVD depedency to one supported by android api 36? Also did you try the suggested fix in the log?

  5. Sahad2701 commented on Apr 13, 2025

    @Sahad2701

    Hi @Sudhirkumar620617 ,

    Clarification: This is not an issue related to AVDs running API level 36.

    The actual issue is due to the usage of the deprecated PluginRegistry API, which was officially deprecated starting from Flutter 3.19.0+. If you're using Flutter 3.19.0 or above, you'll need to migrate to the new FlutterPlugin API to ensure compatibility.

    To resolve the issue:
    Please upgrade the webview_flutter plugin to the latest stable version that supports Android API 34+.
    Also, be sure to run the following clean-up steps:

    flutter pub catch clean
    flutter pub get
    

    This should resolve the issue and restore proper functionality in the latest Flutter versions.

  6. github-actions commented on Jul 23, 2025

    @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.

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

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listteam-androidOwned by Android platform team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions