During the meeting, the State Changers discussed a problem they were facing with their app development, stemming from issues with pod files involving versions, dependencies, and connections with Firebase messaging. Their app includes components from Firebase Messaging, but the project presented errors during the compile phase, failing to recognize Firebase Messaging's functionalities.
The participants explored potential solutions, including deleting the podfile.lock and the 'Pods' directory which is generated by CocoaPods. They also talked about clearing the cache which could potentially be causing issues in their build environment. However, these solutions were proposed with uncertainty because of the complex nature of the issue.
One participant suggested that the problem might be due to conflicting versions of Firebase messaging being downloaded into the project. Changes in the Flutterflow version were also mentioned as a potential cause of the problems, with some dependencies perhaps not working with a newer version of Flutterflow. Moreover, there was an issue with Firebase messaging's function becoming unrecognized, making previously functional parts of the app non-functional.
A significant part of the meeting was spent trying to debug these issues, by looking at the app's configurations and package dependencies, and checking aspects like the target URI for Firebase Messaging in the custom function, or the call to Firebase in the Swift code.
Finally, it was suggested to circumvent these issues by starting a high-speed rebuild of the problematic parts. Since the meeting participants were comfortable with the UI interface, focusing on the underlying parts with issues was more strategic. They would first rebuild the Firebase Messaging feature, then add more features incrementally, to isolate issues effectively.
(Source: Office Hours 9/26/2023 - Plus an Extra! )