Skip to content

feat(device_info_plus)!: Migrate Android plugin to built-in Kotlin#3819

Closed
mohamed-foly wants to merge 1 commit intofluttercommunity:mainfrom
mohamed-foly:feat/device-info-plus-built-in-kotlin
Closed

feat(device_info_plus)!: Migrate Android plugin to built-in Kotlin#3819
mohamed-foly wants to merge 1 commit intofluttercommunity:mainfrom
mohamed-foly:feat/device-info-plus-built-in-kotlin

Conversation

@mohamed-foly
Copy link
Copy Markdown

Description

Move the Android plugin to Flutter's built-in Kotlin setup and remove the old kotlin-android wiring. This keeps the plugin aligned with the supported Android build path before the old KGP flow becomes a build problem.

Related Issues

None.

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I titled the PR using Conventional Commits.
  • I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
  • I ran the available validation for this change: flutter pub get and the example build on the Flutter 3.44 line.
  • I checked the app side with flutter analyze; it only reports the pre-existing infos.

Breaking Change

Yes, this raises the minimum Flutter/Dart floor for the package release.

@vbuberen
Copy link
Copy Markdown
Collaborator

vbuberen commented May 4, 2026

I would also ask to read the contributors guide, because it would be better to start with an issue open in the repo.

environment:
sdk: ">=3.12.0-0 <4.0.0"
flutter: ">=3.44.0-0.0.pre"

There will be no such sharp bump of requirements. I don't plan to do such a bump for now unless there is a real need, like latest Flutter stable (not pre or alpha or whatever) version requires to do so because of some change.

For now this PR and the rest make no sense and even if they in a draft. I will close them as there is no plan to accept them now.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants