flutter-action | Flutter environment for use in GitHub Actions | Continous Integration library

It maybe the null-safety of Flutter 2.0.1 cause build release failed(I found other error may cause this error, but the build error tips has no relation with the real error). I fix it by prebuild project add this line in workflow ci file:

You can use GitHub Action secrets.

Put your dev.json contents in a secret (for example, DEV_JSON_CONTENTS), and write it to the correct location with a command.

You probably did not change the base path in web/index.html

The issue was in a upper case / lower case file name typo. OSX filesystem is by default case insensitive, while Ubuntu, on which the GitHub Action runs, is not.

Your build log shows the following error:

As the error suggests, the Google-Info.plist is not available in the provided path. This happens since your username is not the same as the username used by Github actions and also, you have not loaded it to the Downloads directory. I would suggest checking it into your version control and place it inside the ios directory. Remember to update your references

You could store it somewhere and download it to your Github Actions instance. But loading it directly with the rest of your files is much easier and convenient

Google-Info.plist can be checked into source control. But others can misuse it if your services are not well protected by security rules. For open source projects, it is suggested to guide others to setup their own Firebase project. If you are using a private repository then this does not apply. Learn more here

As per the notes you either need to specify an existing tag or specify a branch or commit for the commit input of the action, based on which a tag will be created:

• You must provide a tag either via the action input or the git ref (i.e push / create a tag). If you do not the action will fail.
• If the tag of the release you are creating does not exist yet, you should set both the tag and commit action inputs. commit can point to a commit hash or a branch name (ex - main).

from https://github.com/ncipollo/release-action#notes

Using the following will give you a new version tag with every run, where the last place of the version is incremented for every run.

Instead of using the local.properties file, set ndkVersion in your build.gradle to match the one available on your CI server. i.e.

I found the problem. The workflow was failing because the keytool was trying to create debug.keystore file in C:\Users\runneradmin\.android but the folder was not created at the time of execution.

Updated YAML -