搜尋分類、套件與程式碼儲存庫

force_update_helper 封面
套件詳情v0.3.0

force_update_helper

一個用於顯示由遠端控制的強制更新提示的套件。

AndroidiOS
近 30 天下載
5630
喜歡數
116
Pub 分數
150

安裝套件

flutter pub add force_update_helper

套件介紹

根據套件公開資料產生的選型評估,僅供參考。

一個 Flutter 套件,可為 Android 與 iOS 應用程式啟用遠端控制的強制更新提示。它允許開發者在應用程式啟動時檢查遠端設定(例如 JSON 端點),以強制執行應用程式更新。若需更新,使用者將立即收到更新提示,確保所有使用者皆使用最新版本。此套件輕量且可無縫整合至現有應用程式中,無需複雜設定。

適用情境

  • 強制執行關鍵錯誤修復
  • 推送安全更新
  • 在使用者之間維持功能一致性
  • 控制更新發布時機
  • 確保符合新的應用政策

主要特色

  • 透過HTTP端點進行遠端設定
  • 簡單的整合,程式碼量最少
  • 對 Android 和 iOS 的支援
  • 可定制的提示UI
  • 可選延遲,然後強制更新

適合對象

  • 需要嚴格版本控制的應用程式
  • 企業或受監管的應用
  • 頻繁發布功能的應用程式
  • 管理多個應用版本的團隊

使用建議

  • 需要穩定的互聯網連接
  • 依賴外部伺服器的可用性
  • 如果過度使用,可能會影響使用者體驗
  • 需要對失敗的檢查進行適當的錯誤處理
  • 不適用於沒有後端支援的應用程式

原始 README

以下為關聯原始碼儲存庫的 README 原文快照,最新內容請造訪原始碼儲存庫。

Force Update Helper

Pub Language License Twitter

A package for showing a force update prompt that is controlled remotely.

Force update alert preview

Features

  • Remote control: control the force update logic remotely with a custom backend, or Firebase Remote Config, or anything that resolves to a Future<String>.
  • UI-agnostic: the package tells you when to show the update UI, you decide how to show it (localization is up to you).
  • Small and opinionated: the package is made of only two classes. Use it as is, or fork it to suit your needs.

Getting started

Depend on it:

dependencies:
  force_update_helper:

Use it by adding a ForceUpdateWidget to your MaterialApp's builder property:

void main() {
  runApp(const MainApp());
}

final _rootNavigatorKey = GlobalKey<NavigatorState>();

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      navigatorKey: _rootNavigatorKey,
      builder: (context, child) {
        return ForceUpdateWidget(
          navigatorKey: _rootNavigatorKey,
          forceUpdateClient: ForceUpdateClient(
            // * Real apps should fetch this from an API endpoint or via
            // * Firebase Remote Config
            fetchRequiredVersion: () => Future.value('2.0.0'),
            // * Example ID from this app: https://fluttertips.dev/
            // * To avoid mistakes, store the ID as an environment variable and
            // * read it with String.fromEnvironment
            iosAppStoreId: '6482293361',
          ),
          allowCancel: false,
          showForceUpdateAlert: (context, allowCancel) => showAlertDialog(
            context: context,
            title: 'App Update Required',
            content: 'Please update to continue using the app.',
            cancelActionText: allowCancel ? 'Later' : null,
            defaultActionText: 'Update Now',
          ),
          showStoreListing: (storeUrl) async {
            if (await canLaunchUrl(storeUrl)) {
              await launchUrl(
                storeUrl,
                // * Open app store app directly (or fallback to browser)
                mode: LaunchMode.externalApplication,
              );
            } else {
              log('Cannot launch URL: $storeUrl');
            }
          },
          onException: (e, st) {
            log(e.toString());
          },
          child: child!,
        );
      },
      home: const Scaffold(
        body: Center(
          child: Text('Hello World!'),
        ),
      ),
    );
  }
}

Note that in order to show the update dialog, a root navigator key needs to be added to MaterialApp (this is the same technique used by the upgrader package).

How the package works

Unlike the upgrader package, this package does not use the app store APIs to check if a newer version is available.

Instead, it allows you to store the required version remotely (using a custom backend or Firebase Remote Config), and compare it with the current version from your pubspec.yaml.

Here's how you may use this in production:

  • Submit a new version of your app to the stores
  • Once it's approved, publish it
  • Wait for an hour or so, to account for the time it takes for the new version to be visible on all stores/countries
  • Update the required_version endpoint in your custom backend or via Firebase Remote Config
  • Once users open the app, the force update logic will kick in and force them to update

Additional details

The package is made of two classes: ForceUpdateClient and ForceUpdateWidget.

  • The ForceUpdateClient class fetches the required version and compares it with the current version from package_info_plus. Versions are compared using the pub_semver package.
  • The fetchRequiredVersion callback should fetch the required version from an API endpoint or Firebase Remote Config.
  • When creating your iOS app in App Store Connect, copy the app ID and use it as the iosAppStoreId, otherwise the force upgrade alert will not show. I recommend storing an APP_STORE_ID as an environment variable that is set with --dart-define or --dart-define-from-file and read with String.fromEnvironment.
  • The Play Store URL is automatically generated from the package name (which is retrieved with the package_info_plus package)
  • If you want to make the update optional, pass allowCancel: true to the ForceUpdateWidget and use it to add a cancel button to the alert dialog. This will make the alert dismissable, but the prompt will still show on the next app start.
  • You can catch and handle any exceptions with the onException handler. Alternatively, omit the onException and handle exceptions globally.
  • If you use the url_launcher package to open the app store URLs (which is the recommended way), don't forget to add the necessary query intent inside AndroidManifest.xml:
    <queries>
        <intent>
            <action android:name="android.intent.action.VIEW" />
            <category android:name="android.intent.category.BROWSABLE" />
            <data android:scheme="https"/>
        </intent>
    </queries>

When is the Force Update Alert shown?

The force update logic is triggered in two cases:

  • when the app has just started (from a cold boot)
  • when the app returns to the foreground (common when switching between apps)

Then, the update alert will show if all these conditions are true:

  • the app is running on iOS or Android (web and desktop are not supported)
  • the requiredVersion is fetched successfully
  • the requiredVersion is greater than the currentVersion
  • (iOS only) the iosAppStoreId is a non-empty string

If the user clicks on "Update Now" and lands on the app store page but does not update the app, the force update alert will show again when returning to the app.

If the update alert shows on Android and the back button is pressed, it will be shown again unless allowCancel is true.

Where to find the iosAppStoreId

Once you have created your app in App Store Connect, you can grab the app ID from the browser URL:

Force update alert preview

Make sure to set the correct iosAppStoreId before releasing the first version of your app, otherwise users on old version won't be able to update.

Example: fetching a remote config JSON from a GitHub Gist

The example app shows how to fetch some remote config JSON from a RemoteConfigGistClient:

ForceUpdateWidget(
  navigatorKey: _rootNavigatorKey,
  forceUpdateClient: ForceUpdateClient(
    fetchRequiredVersion: () async {
      // * Fetch remote config from an API endpoint.
      // * Alternatively, you can use Firebase Remote Config
      final client = RemoteConfigGistClient(dio: Dio());
      final remoteConfig = await client.fetchRemoteConfig();
      return remoteConfig.requiredVersion;
    },
    // * Example ID from this app: https://fluttertips.dev/
    // * To avoid mistakes, store the ID as an environment variable and
    // * read it with String.fromEnvironment
    iosAppStoreId: '6482293361',
  ),
  allowCancel: false,
  showForceUpdateAlert: (context, allowCancel) => showAlertDialog(
    context: context,
    title: 'App Update Required',
    content: 'Please update to continue using the app.',
    cancelActionText: allowCancel ? 'Later' : null,
    defaultActionText: 'Update Now',
  ),
  showStoreListing: (storeUrl) async {
    if (await canLaunchUrl(storeUrl)) {
      await launchUrl(
        storeUrl,
        // * Open app store app directly (or fallback to browser)
        mode: LaunchMode.externalApplication,
      );
    } else {
      log('Cannot launch URL: $storeUrl');
    }
  },
  onException: (e, st) {
    log(e.toString());
  },
  child: child!,
)

The RemoteConfigGistData class can be used to fetch and parse some JSON in this format:

{
  "config" : {
    "required_version": "2.0.0"
  }
}

Here's the reference RemoteConfigGistData class:

import 'dart:convert';

import 'package:dio/dio.dart';

class RemoteConfigGistData {
  RemoteConfigGistData({required this.requiredVersion});
  final String requiredVersion;

  factory RemoteConfigGistData.fromJson(Map<String, dynamic> json) {
    final requiredVersion = json['config']?['required_version'];
    if (requiredVersion == null) {
      throw FormatException('required_version not found in JSON: $json');
    }
    return RemoteConfigGistData(requiredVersion: requiredVersion);
  }
}

/// An API client class for fetching a remote config JSON from a GitHub gist
class RemoteConfigGistClient {
  const RemoteConfigGistClient({required this.dio});
  final Dio dio;

  /// Fetch the remote config JSON
  Future<RemoteConfigGistData> fetchRemoteConfig() async {
    // TODO: Update this with your GitHub username
    const owner = 'bizz84';
    // TODO: Update this with your gist IDs
    const gistId = 'e5b8041b35c58a3eba2baa23096d1678';
    // TODO: Update this with your gist file name
    const fileName = 'app_name_remote_config.json';
    const url =
        'https://gist.githubusercontent.com/$owner/$gistId/raw/$fileName';
    final response = await dio.get(url);
    final jsonData = jsonDecode(response.data);
    return RemoteConfigGistData.fromJson(jsonData);
  }
}

For more info, see this example app:

Example: fetching the required version from a backend endpoint

The package comes with a sample server-side app that implements a required_version endpoint using Dart Shelf.

This can be used as part of the force update logic in your Flutter apps.

For more info, see this example app:

Are contributions welcome?

I created this package so I can reuse the force update logic in my own apps.

While you're welcome to suggest improvements, I don't want the package to become bloated, and I only plan to make changes that suit my needs.

If the package doesn't suit your use case, consider forking and maintaining it yourself.

LICENSE: MIT

所屬分類

依賴

依賴清單 2 項

原始碼儲存庫

使用此套件的專案