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
Remove references to deprecated v1 Android embedding
To ensure this plugin will work with users running the next stable version of Flutter remove references to the v1 embedding.
The v1 embedding was deprecated around 6 and a half years ago. In Flutter 3.22, the Flutter tool dropped support for building v1 apps entirely. Flutter plans to delete version one of it's Android embedding in the next stable release, per https://medium.com/flutter/whats-new-in-flutter-3-22-fbde6c164fe3 (in the "Removal of v1 Android embedding" section).
When that deletion happens, any apps using plugins that still have references to the removed classes will fail to build when updating to the next stable version (probably Flutter 3.26).
As a part of this deprecation, the Flutter Android team is doing community outreach by filing bugs and submitting some pull requests to update plugins to minimize the impact this removal has on the community.
This change should have no impact on users of this plugin that are building apps using the v2 embedding (we don't have a percentage to share, but this is the vast majority of users).
It will remove support for users that are still using the v1 embedding on versions of Flutter older than 3.22.
If this change doesn't land, this plugin will instead be broken for all apps building on the next stable version of Flutter and beyond.
Is there a way to support both v1 and v2 embedding apps in the next stable version of Flutter?
No.
This is the PR where we are removing the deprecated engine classes: flutter/engine#52022
Minimal Reproduction
Any flutter app built using this plugin and engine pull request flutter/engine#52022
Exception or Error
compilation error, missing classes
Expected Behaviour
compile
Screenshots
n/a
Additional context
n/a
Device
all
OS
android
Browser
n/a
Flutter version
future
flutter_web_auth_2 version
3.2.1
Checklist
I have read and followed the entiretroubleshooting guide and it has not provided the solution I need.
I have provided all the information I can.
The text was updated successfully, but these errors were encountered:
Description
Remove references to deprecated v1 Android embedding
To ensure this plugin will work with users running the next stable version of Flutter remove references to the v1 embedding.
The v1 embedding was deprecated around 6 and a half years ago. In Flutter 3.22, the Flutter tool dropped support for building v1 apps entirely. Flutter plans to delete version one of it's Android embedding in the next stable release, per https://medium.com/flutter/whats-new-in-flutter-3-22-fbde6c164fe3 (in the "Removal of v1 Android embedding" section).
When that deletion happens, any apps using plugins that still have references to the removed classes will fail to build when updating to the next stable version (probably Flutter
3.26
).As a part of this deprecation, the Flutter Android team is doing community outreach by filing bugs and submitting some pull requests to update plugins to minimize the impact this removal has on the community.
Some example PRs:
android_alarm_manager_plus
fix(android_alarm_manager_plus): Remove references to v1 embedding fluttercommunity/plus_plugins#2864Consequences:
3.22
.If this change doesn't land, this plugin will instead be broken for all apps building on the next stable version of Flutter and beyond.
Is there a way to support both v1 and v2 embedding apps in the next stable version of Flutter?
No.
This is the PR where we are removing the deprecated engine classes: flutter/engine#52022
Minimal Reproduction
Any flutter app built using this plugin and engine pull request flutter/engine#52022
Exception or Error
compilation error, missing classes
Expected Behaviour
compile
Screenshots
n/a
Additional context
n/a
Device
all
OS
android
Browser
n/a
Flutter version
future
flutter_web_auth_2 version
3.2.1
Checklist
The text was updated successfully, but these errors were encountered: