If needed, change your Deployment Target. Navigate to your ios folder within the Flutter project, and run: rm Podfile.lock I usually prefer deleting Podfile as a whole and then reinstalling the Pods, as this is more effective and will help resolve any package version conflicts. If you have previously installed any iOS packages using Cocoapods, then you need to update your Podfile. Your pubspec.yaml file will be successfully upgraded with the new versions of the current packages when null-safety is enabled. You can upgrade all the package dependencies by running: dart pub upgrade -null-safety If any package that cannot be migrated persists, then you may have to find an alternative at pub.dev. You will now be able to see the packages that can be safely migrated within the produced output. You can check which dependencies can be updated by running:

If you don’t have any third-party dependencies, feel free to skip this step.

Check if all the dependencies within the app can be upgraded.

Here, null-safety is the branch name where the new migrated code will be committed. This is to make sure that none of your project files are affected within the master branch.

Create a new git branch to push the new migrated project.

To indicate that there might be a null value within the variable, ? is used.įlutter 2.0 now supports Null Safety luckily, migrating previous projects to Null Safety is as simple as running dart migrate in your project root.īut, before you do this, there are certain steps you need to take care of:

Null Safety can be high of value when your app is in production because it makes sure your app won’t crash due to nullable errors. With Null Safety enabled, you will no longer have any runtime null errors. When a developer adapts to Null Safety, all the types in the program are non-nullable by default.

Ios pod lock in flutter