Flutter App Stuck on Splash Screen: A dev_dependencies Mistake
Recently, i added some features to my side project flutter app. The app is available on both platforms: Google Play Store and App Store. If I release to both platforms at once and some bugs occur, ...

Source: DEV Community
Recently, i added some features to my side project flutter app. The app is available on both platforms: Google Play Store and App Store. If I release to both platforms at once and some bugs occur, it would be difficult to handle. So I decided to release my new build to the Google Play Store first. After the new build was released on the Google Play Store, I installed the app. But something went wrong. I couldn't access the main page. The app was stuck on the splash screen. At that moment, something came to my mind. I had just resolved an issue related to the sign_button package. I was using the sign_button package on the login page, but the Apple login button didn't render correctly. So I replaced it with the sign_in_button package and added it to dependencies in the pubspec.yaml file. I started to think that I might have messed up the pubspec.yaml structure while doing this. I might have placed the package in the wrong section. It should have been in dependencies, but I accidentally a