Upgrading the dependencies and versions

[andoriyaprashant]

Fixes #240

Describe the changes you have made in this PR -

There are many updates are available and I upgrade dependencies, I have simultaneously tested with new dependencies, and there were no errors, unlike before when errors were occurring. After upgrading some dependencies to their compatible version, those errors have also been fixed

And I have tested all the dependencies with Flutter version 3.7.11, and all the dependencies are compatible with this version

Screenshots of the changes (If any) -

• I upgrade dependencies with the help of "flutter pub upgrade --major -version" command

Changes in -

[Akshatji800]

@andoriyaprashant the Flutter CI is failing and the PR includes some packages which are not useful now after migrating to bloc for example - the package provider is not needed now. Please look into these issues if you want to get the PR merged. Also, next time while resolving the issues in this PR please don't close this PR and raise a new one but makes the necessary changes and update this PR itself. Just google - how to update a PR.

[amitamrutiya]

@andoriyaprashant, we have upgraded to Flutter version 3.10.5. Please ensure that all dependencies are compatible and functioning correctly with the new Flutter version. So fetch latest changes and update this PR accordingly.

[andoriyaprashant]

@Akshatji800 Sir, as @amitamrutiya2210 has changed the Flutter version, it is now Flutter version 3.10.5. I have ensured that all the changes I made in the dependencies are compatible with the new Flutter version.

The new dependencies-

However, when @amitamrutiya2210 made changes to the Flutter version, some dependencies were duplicated.

and flutter ci is failing because of this

I have removed those duplicates If you'd like, I can commit these changes, and the changes I made are the same as shown in my screenshot. Please review those changes.
Thank you.

[amitamrutiya]

Yes, @andoriyaprashant, please remove the duplicate dependencies and commit the changes. In the new commit, make sure to remove the pubspec.yaml file as it is not necessary for this issue.

[andoriyaprashant]

Hey @amitamrutiya2210 As you mentioned, I have removed the duplicate changes.
However, by mistake, this commit got pushed to the branch in my forked repository.

You can see this commit in the commit graph, but I'm unable to display it in this pull request. Could you please assist me with resolving this issue?

[amitamrutiya]

Try with this command git push origin flood2 -f. I think this has to work.

[andoriyaprashant]

@amitamrutiya2210 Sorry but still not working with "git push origin flood2 -f"
When I was working on this same branch, I committed the changes and used "git push --force origin flood2 " command. Now those changes are not appearing in the code of the "flood2" branch as well, but my commit is visible in commit graph.

[andoriyaprashant]

Hey @amitamrutiya2210 @Akshatji800 I have implemented the changes you requested, and now Flutter CI is not failing. So, could you please review my pull request now
Thank you so much for your support

[amitamrutiya]

@andoriyaprashant, Before merging the pull request, you need to ensure two things in your PR:

1. Remove the pubspec.lock file from your commits. This is not necessary for this particular PR.
2. Squash all commits into a single one.

If you are unsure about these steps, simply search for them on Google. These tasks are easy to figure out.

[Akshatji800]

@andoriyaprashant the Flutter CI is still failing and also please look into what @amitamrutiya2210 asked you do in his previous comment to get this PR merged.

[andoriyaprashant]

@Akshatji800 Thank you, I will definitely work on this.

[amitamrutiya]

@andoriyaprashant, please make sure to pull the latest changes before making any new commits.

[andoriyaprashant]

Hello sir @Akshatji800 , I'm a little confused and would appreciate your guidance.
So far, I have only upgraded dependencies, and the last time the Flutter CI failed because there were duplicate dependencies, which I removed in a subsequent commit titled "flutter ci fixed." Now, you mentioned making changes to the pubspec.yaml file, but I'm unsure about what to do next. I have already upgraded all the dependencies according to the Flutter version. Could you please provide further instructions? Thank you so much for your support.

[Akshatji800]

Hello sir @Akshatji800 , I'm a little confused and would appreciate your guidance. So far, I have only upgraded dependencies, and the last time the Flutter CI failed because there were duplicate dependencies, which I removed in a subsequent commit titled "flutter ci fixed." Now, you mentioned making changes to the pubspec.yaml file, but I'm unsure about what to do next. I have already upgraded all the dependencies according to the Flutter version. Could you please provide further instructions? Thank you so much for your support.

@andoriyaprashant why you are still including the pubspec.lock file in the commit and if you are including then resolve the conflicts.

[andoriyaprashant]

Sir @Akshatji800 as you mentioned, I have resolved the conflicts from the pubspec.lock file, and I have also squashed all the commits. Please take a look once, and if there are still any conflicts, I will be happy to resolve them.
Thank you

[andoriyaprashant]

@Akshatji800 Sir, can you review it again now?

[Akshatji800]

@andoriyaprashant everytime I come and try to review this PR and give approval to run the CI I find some or the other reason for the build to be failing :/ . Make sure you resolve the issue and none of the build failes next time so that we can finalize this PR.

[andoriyaprashant]

@Akshatji800 Sorry sir, I am currently learning about workflows, but as you advised, I have made the changes in it. Please take a look at them.