flutter_store_listing 1.4.0
flutter_store_listing: ^1.4.0 copied to clipboard
Flutter plugin to handle app reviews with the StoreKit review API, generate app store links and open them for iOS or android.
1.4.0 #
Android gets a native implementation, and the market:// probe is gone.
launchStoreListing used to ask canLaunchUrl('market://') and open
market://details?id=… when that said yes. On a device where the app was
installed from the Play Store it generally did say yes: Android makes "the app
that installed your app" visible automatically, with no <queries> entry and
whatever the targetSdk. For most users, then, market://details?id=… is
what actually opened, and this release changes the route rather than the
destination — both it and the https URL with the package set land in the
Play Store app.
The probe did fail for installs from outside the Play Store — sideloaded, or
from another store — on an app targeting API 30 or higher with no <queries>
entry of its own, because com.android.vending is then not automatically
visible. Those users got the https URL in a browser, and still do whenever the
Play Store app is absent.
It now opens the listing the way Google's "Linking to Google Play" guide
documents: an ACTION_VIEW intent for the play.google.com URL with the
package set to com.android.vending, which url_launcher cannot express.
When the Play Store app is absent or disabled the same URL is viewed without
the restriction, so devices without Play — F-Droid installs among them — still
reach the listing in a browser. No <queries> entry is needed: the
implementation attempts the intent and handles ActivityNotFoundException
rather than querying, which package visibility does not filter.
For most users this is the behaviour they already had, now arrived at on purpose and by the route Google documents, rather than through a probe whose answer depended on how the app had been installed. On a device without the Play Store app, the listing still opens in whatever claims Play links.
- The package declares
androidinflutter.plugin.platformsfor the first time, so pub.dev lists Android support that was always there in practice. Every consumer's Android build therefore gains a Gradle module and a Kotlin compile step, and the module declaresminSdk 24— Flutter's own floor, and the same valueurl_launcher_androiddeclares, so an app already pullingurl_launcheris at 24 regardless. - The Android side has no
implementationdependencies: no androidx, and in particular no Play Core, so Play's in-app review API is still deliberately out of this package and it stays clean in F-Droid builds. JUnit, Mockito and Robolectric aretestImplementationonly, resolved when the module's own tests are run. FlutterStoreListing.customize(urlCanLaunch: …)still compiles but is no longer called by this package. It is removed in 2.0.FlutterStoreListing.playStorePackageNameis exposed for callers building their own intents.
1.3.0 #
Requires Flutter 3.44 / Dart 3.10. Swift Package Manager support needs the
generated FlutterFramework Swift package, which Flutter only produces from
3.44.0 on.
Behaviour change: launchRequestReview no longer contradicts its own
documentation. It was inverted in both branches, so iOS callers got the
opposite of what the API said:
- A successful native prompt also opened the App Store write-review page, ejecting the user to the App Store immediately after the in-app dialog. The two are now exclusive — the store listing is the fallback for when the native dialog is unavailable, which is what the doc comment always claimed.
onlyNative: truereturnedfalseprecisely when the prompt had been shown, and the iOS branch returnedtruewhen the native call had failed and nothing at all had happened. Both are now the right way round:truemeans a review was asked for,falsemeans it was not.
If you branch on the return value of launchRequestReview(), re-check it. If
you call it for its side effect only, the visible change is that iOS users are
no longer sent to the App Store after being shown the in-app prompt.
- Allow
package_info_plus10.x (widened to>=1.0.3 <11.0.0). This was the only thing making version solving fail for apps that needpackage_info_plus10.x. - Add Swift Package Manager support. The plugin ships
ios/flutter_store_listing/Package.swiftalongside the podspec, so it no longer appears in Flutter's "plugins do not support Swift Package Manager" warning. CocoaPods consumers are unaffected; both build the same sources. - Rewrite the iOS plugin in Swift. This is a prerequisite for the item
below:
AppStore.requestReview(in:)is a Swift-only StoreKit 2 API and cannot be called from Objective-C. - iOS: use
AppStore.requestReview(in:)on iOS 16+. The wholeSKStoreReviewControllerclass is deprecated as of iOS 18; the deprecatedrequestReview(in:)remains the fallback for iOS 15. The old@available(iOS 10.3, *)guards and the no-scenerequestReview()call are gone. - Remove the Android platform entry. Its
onMethodCallonly ever returnednotImplemented(), and the Dart side never invoked the channel off iOS, so consumers were building an AAR for nothing. Nothing changes at runtime: Android still opens the Play listing throughurl_launcher. Play's in-app review API is deliberately left out so this package stays free of proprietary dependencies, which would otherwise reach F-Droid builds. - Fix
forceAndroidPackageNamebeing ignored bylaunchStoreListing(), which read the package name straight frompackage_info_plus. - The package is now WebAssembly-compatible:
dart:iois behind a conditional import instead of being imported unconditionally forPlatform. - Remove the discontinued
pedanticdependency (it was unused, and declared as a runtime instead of a dev dependency). - iOS: use
httpsfor the iTunes lookup API — App Transport Security blocks cleartexthttpby default, so this likely failed on device unless the host app carried an ATS exception. - iOS: generate store listing URLs for
apps.apple.comwithout a hardcoded/us/storefront, instead of the legacyitunes.apple.com/us/app/id…form. - Give the iOS podspec real metadata (it was unedited template boilerplate) and a 15.0 deployment target, matching the oldest iOS that Flutter 3.44 itself supports.
- Add an actual test suite — the previous one was an empty
main()— and a GitHub Actions workflow that analyzes, formats, tests and builds the example for iOS.
1.2.0 #
- Update AGB Version, Android SDK Version, etc.
1.1.0 #
- Compatibility with Flutter 3.29
1.0.0 #
- Upgrade
package_info_plusdependency.
0.3.1 #
- Upgrade dependencies.
0.3.0 #
- Upgrade dependencies
- Android: Upgrade to AGP 8.1, migrate namespace, etc.
0.2.2 #
- Update dependencies, dart 3.0
0.2.1+1 #
- Update dependencies.
0.2.1 #
- update to dependency
package_info_plus
0.2.0+1 #
- Remove unnecessary casts.
0.2.0 #
- Nullsafety migration.
0.1.1+2 #
- More documentation, updated links.
- No longer a singleton, override app store id and android package name.
- Add isSupported() methods.
- Made API more consistent.
- Added simple example.
0.1.0 #
- First release
0.0.1 #
- Initial version