From a57d93a49aebfeae5607244cc7a30e2696d99a27 Mon Sep 17 00:00:00 2001 From: Kevin Date: Mon, 7 Sep 2026 18:49:04 +0200 Subject: [PATCH] chore(android): align the plugin's AGP classpath with the example's 9.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #145 landed AGP **9.4.0** in `purchasely/example/android/settings.gradle` — not the 9.3.1 its title says: Dependabot re-targeted to the latest when it rebased. #143, which would have moved `purchasely/android`'s buildscript classpath, was closed as superseded and its branch deleted, so the two declarations diverged: example/settings.gradle com.android.application 9.4.0 (effective) purchasely/android com.android.tools.build 9.0.1 (stale) The classpath here only takes effect for a standalone module build — when Flutter builds the plugin as part of the example, the applied version comes from the example's pluginManagement. So this is not a build fix; it is keeping the two declarations from drifting, which is what makes the next AGP bump reviewable. Both wrappers clear AGP 9.4's Gradle floor: `purchasely/android` on 9.7.1 (#150), the example on 9.6.1 (#140). Verified: `flutter build apk --debug` green on the example, which exercises the effective AGP. Co-Authored-By: Claude Opus 5 (1M context) --- purchasely/android/build.gradle | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/purchasely/android/build.gradle b/purchasely/android/build.gradle index 33fd46df..117f0fe0 100644 --- a/purchasely/android/build.gradle +++ b/purchasely/android/build.gradle @@ -9,7 +9,7 @@ buildscript { } dependencies { - classpath 'com.android.tools.build:gradle:9.0.1' + classpath 'com.android.tools.build:gradle:9.4.0' classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version" } }