RemoteConfig : new published value is not updating , getting old value from storage

[NibhaJ]

When we have a higher version available on the play store. This feature redirects users to the app store to install updates. But it is not working on a few devices. The user still using the older version. when the user clears the storage alert from the update is coming, we can not ask all users to clear the storage. We require a force update due to some database changes. What can we do to make it work?

  versionCheck(context) async {
    //Get Current installed version of app
    final PackageInfo info = await PackageInfo.fromPlatform();
    double currentVersion =
        double.parse(info.version.trim().replaceAll(".", ""));

    //Get Latest version info from firebase config
    final FirebaseRemoteConfig remoteConfig =
        await FirebaseRemoteConfig.instance;

    try {
      // Using default duration to force fetching from remote server.
      await remoteConfig.fetch();
      await remoteConfig.fetchAndActivate();
      remoteConfig.getString('force_update_current_version');
      double newVersion = double.parse(remoteConfig
          .getString('force_update_current_version')
          .trim()
          .replaceAll(".", ""));
      print("new " +  newVersion.toString()  + " current: " +currentVersion.toString() );
      if (newVersion > currentVersion) {
        _showVersionDialog(context);
      }
    } on Exception catch (exception) {
      // Fetch throttled.
      print(exception);
    } catch (exception) {
      print('Unable to fetch remote config. Cached or default values will be '
          'used');
    }
  }

Flutter doctor

Run flutter doctor and paste the output below:

Click To Expand

PASTE OUTPUT INSIDE HERE

---

### Flutter dependencies
name: xxx
description: A new Flutter application.

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.9.2+23

environment:
  sdk: '>=2.12.0 <3.0.0'


dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:

    sdk: flutter
  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^1.0.4
  http: ^0.13.4
  #firebase_core_platform_interface: 4.5.2 # note removed ^
  firebase_messaging: ^14.1.4 # previously I only had this which was pulling in 4.5.2 which you do not want
  firebase_core: ^2.4.0
  sqflite: ^2.0.2
  path_provider: ^2.0.9
  device_info: ^2.0.3
  mime_type: ^1.0.0
  expandable: ^5.0.1
  permission_handler: ^9.2.0
  connectivity: ^3.0.6
  shared_preferences: ^2.0.13
  datetime_picker_formfield: ^2.0.0
  intl: ^0.17.0
  flutter_speed_dial: ^5.0.0+1
  camera: ^0.9.7+1
  fluttertoast: ^8.0.8
  video_player: ^2.2.10
  url_launcher: ^6.1.4
  file_picker: ^4.5.1
  image_picker: ^0.8.4+11
  share_plus: ^4.0.4
  quiver: ^3.0.1+1
  syncfusion_flutter_pdfviewer: ^19.4.50-beta
  sms_autofill: ^2.2.0
  flutter_native_image: ^0.0.6+1
  whatsapp_unilink: ^2.0.2
  smooth_star_rating_null_safety: ^1.0.4+2
  encrypt: ^5.0.1
  percent_indicator: 4.0.0
  paytm_allinonesdk: ^1.1.5
  google_maps_flutter: ^2.1.5
  package_info: ^2.0.2
  light_compressor: ^1.2.2
  firebase_remote_config: ^3.0.7
  flutter_html: ^2.2.1
  regexpattern: ^2.0.1
  eva_icons_flutter: ^3.1.0
  http_client: ^1.5.1
  excel: ^2.0.0-null-safety-3
  footer: ^0.0.4
  cached_network_image: ^3.0.0
  flutter_exif_rotation: ^0.5.1
  visibility_detector: ^0.3.3
  flutter_local_notifications: ^12.0.2


dev_dependencies:
  flutter_test:
    sdk: flutter


# For information on the generic Dart part of this file, see the
# following page: https://dart.dev/tools/pub/pubspec

# The following section is specific to Flutter.
flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - assets/logo_new.png
    - assets/
    #    - assets/logo_xtra_trust.png
    - assets/XTRANET_CPS_Ver4.0.0_signed.pdf
    - assets/subscriber_agreement.pdf
    - assets/subscriber_agreement_hindi.pdf

  # An image asset can refer to one or more resolution-specific "variants", see
  # https://flutter.dev/assets-and-images/#resolution-aware.

  # For details regarding adding assets from package dependencies, see
  # https://flutter.dev/assets-and-images/#from-packages

  # To add custom fonts to your application, add a fonts section here,
  # in this "flutter" section. Each entry in this list should have a
  # "family" key with the font family name, and a "fonts" key with a
  # list giving the asset and other descriptors for the font. For
  # example:
  fonts:
    - family: Poppins
      fonts:
        - asset: fonts/poppins_regular.ttf
  # fonts:
  #   - family: Schyler
  #     fonts:
  #       - asset: fonts/Schyler-Regular.ttf
  #       - asset: fonts/Schyler-Italic.ttf
  #         style: italic
  #   - family: Trajan Pro
  #     fonts:
  #       - asset: fonts/TrajanPro.ttf
  #       - asset: fonts/TrajanPro_Bold.ttf
  #         weight: 700
  #
  # For details regarding fonts from package dependencies,
  # see https://flutter.dev/custom-fonts/#from-packages

[darshankawar]

Thanks for the report @NibhaJ

We require a force update due to some database changes. What can we do to make it work?

It's not a good practice to force update app on every update in the store. Also, some users can see the updated version in given store later than others. This is just how Google Play and AppStore work.

Thus, when you really need to force update the application you can increment the parameter on Firebase e.g. a day after update in the store.
You may take a look at the plugin example as how the version is incremented and its implementation to give you an idea.

But it is not working on a few devices.

This probably indicates that the value not getting updated is not an issue, but could be a glitch specific to devices.

I suggest you to ask this question on support channels like StackOverflow to get solution.
Closing from here, as this doesn't seem to be plugin issue. If you disagree, write in comments and I'll reopen it.

[NibhaJ]

It's not a good practice to force update the app on every update in the store.

It is a business requirement and as a developer, I do feel that is it fair one as business to expect or enforce a force update.

This probably indicates that the value not getting updated is not an issue, but could be a glitch specific to devices.

I suggest you to ask this question on support channels like StackOverflow to get solution.
Closing from here, as this doesn't seem to be plugin issue

It is disappointing to know that the moderator of the community is more interested in closing than enriching the plugin