Dao Hoang Son

It has been a whole year !

  It has been ten months ...

If you are building Flutter app and shows app version in-app for users to see (mostly testers). You may run into a weird issue that the version code is different from the configured value. E.g. if you run ` flutter build --build-number=1234 ` it will show up as ` 3234 `, 123 shows up as ` 2123 `... What the hell is happening? flutter.gradle#L864-L876  is the culprit. Basically ` --split-per-abi ` will increase the version code number by 1000, 2000, 3000, etc. as seen above. If you don't want that behavior, just build one single fat APK.

  It only takes eight months  😅

Yay! flutter_widget_from_html .

If you follow the FCM tutorial Send an image in the notification payload and encountered this error message: 'FirebaseMessaging/FirebaseMessaging.h' file not found You are on the right place, I'm going to show you how to fix it. My app was working fine but one day it stopped compiling. Apparently Flutter 1.20 changed the way it uses CocoaPod so the service extension no longer has the proper library configured. After some tinkering, I came up with this pod config, it has to be added to ios/Podfile below the main Runner target. target 'FcmImage' do use_frameworks! use_modular_headers! require File.expand_path('../.symlinks/plugins/firebase_core/ios/firebase_sdk_version.rb', __FILE__) firebase_sdk_version = firebase_sdk_version! pod 'Firebase/Messaging', "~> #{firebase_sdk_version}" end FcmImage is my extension name, replace it with yours We can use a hardcoded version for Firebase/Messaging pod but doing so m...