Dealing with Flutter Dependency Conflicts and Third-Party Plugin Changes

In this podcast episode, Krish discusses recent changes made to their mobile app built on Flutter. They highlight the challenges faced when upgrading dependencies and dealing with breaking changes. He shares their experience with dependency conflicts and the need to update dependencies incrementally. He also discuss the changes in Facebook login and the introduction of limited login. Krish provides insights into debugging and finding solutions to these challenges. He concludes by mentioning their exploration of AI technologies and the availability of their APIs on AWS Marketplace.

Takeaways

Regularly upgrading dependencies in a mobile app is important to avoid dependency issues and breaking changes.
Handling dependency conflicts can be challenging, especially when using third-party plugins and libraries.
Changes in third-party plugins, like Facebook login, can introduce new features and limitations that need to be accounted for.
Debugging and finding solutions to issues with upgrades and changes require thorough investigation and sometimes trial and error.
Exploring AI technologies and leveraging existing APIs can save time and effort in software development.

Chapters

00:00 Introduction and Apologies for the Delay

04:12 Handling Dependency Upgrades and Breaking Changes

08:38 Challenges with Facebook Login and Limited Login

13:04 Debugging and Finding Solutions to Issues

15:28 Importance of Keeping Up to Date with Software Changes

18:16 Exploring AI Technologies and APIs

29:20 Future Topics and Conclusion

Podcast

Check out on Spotify.

Summary

Challenges

Flutter frequently releases updates, leading to potential dependency issues if not updated regularly.
Discussing recent challenges faced during Flutter upgrades.

Flutter Upgrade Process

Team recently upgraded to Flutter version 3.22.3, encountering typical upgrade issues.
Dependency conflicts arise when multiple versions are involved.
Importance of managing dependencies and maintaining a clean development environment.

Handling Dependency Issues

Approach includes updating dependencies one by one and addressing any errors or warnings.
Another method involves updating all dependencies at once and then resolving issues.
Both methods have their pros and cons, and the team uses them interchangeably.

Specific Changes and Examples

Example of handling breaking changes, such as renaming a class in a third-party plugin.
Mention of the Quill dependency used for rich text editing in the mobile app.
Live demonstration of updating the Quill dependency and verifying no breaking changes.