Create a system to check the minimum app version needed and throw error if needed.

[nazrinharris]

Basically, the database now properly reject writes (provided that the user uses app version 0.3.2 and above where custom claims will be implemented), but there will not be a beautiful error message, just a simple permission denied. I will need to implement this version checking client side.

I'm thinking of simply having a new collection called configs and have a document called app-meta, and having a field minimum-app-version. Then whenever there is a major data structure change, this field (and the field in security rules) will be changed.

This will also open a possibility to have a latest-version, and the app will compare against this field to suggest the user to update the app.

---

Firebase Remote Config seems like a good solution for this rather than a document in firestore, here's the general overview of steps I need to take.

• [x] Add Firebase Remote Config to your project.
• [x] Define the parameters for minimum app version and latest app version in the Firebase Console.
• [x] Fetch the Remote Config values in your app.
• [x] Implement a isAppVersionAllowed() method in a seperate AppVersionHelper
• [x] Handle update requirements and suggestions based on the comparison.

[nazrinharris]

Methods to check version before execution (all write methods in <any>Repository:

• [x] AuthRepository
• [x] ProduceManagerRepository
• [x] FarmShopManagerRepository

[nazrinharris]

In ProduceManagerRepository, it seems like Firestore doesn't properly block admins from creating produce with an app version lower than minimum.

[nazrinharris]

Actually, it seems like the isAppVersionAllowed() in rules doesn't really work

[nazrinharris]

Should be done with e9b143f