In this meeting, the State Changer, Paul, discusses two main issues. The first issue is related to the intermittent errors he experiences when building and launching his application after enabling push notifications. He mentions that sometimes the build doesn't work initially, but if he runs the function again, it works. The suggestion given is to prepare for this issue when deploying to a continuous delivery system by incorporating a retry mechanism. As for the second issue, Paul is concerned about the potential problems he might face when publishing his app in the app store. He asks if there is an easy way to revert to a previous version in case there are too many problems with the new Flutter version. The State Changer explains that making changes to the binary (the code running on the device) requires going through the app store approval process, which can be time-consuming. However, there are options like using feature flags to control the activation of new features and assets or data updates that can be done over the air without going through the app store. The State Changer suggests exploring Flutter's support for over the air updates and feature flags. Additionally, he advises planning ahead and getting the app through the app store well in advance of any deadlines to account for potential delays during busy periods. Overall, the meeting discussed strategies for handling intermittent build errors and considerations for publishing and managing app versions in the app store.
(Source: Office Hours 9/13/2023 )
