Upgrade dependency versions for v1.4.5 #208
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR overall upgrade both aos and ios dependencies and some of their environment configs.
It aims for dealing with some potential issues existing in outdated dependencies.
However, we may not able to update all dep's version since some of them require
Dart v3
It seems that there's no any breaking changes among those upgraded deps.
AOS side
1.9.10
.pubspec.yml
.namespace
field has been added intoandroid
block in for fitting with the upcoming new gradle version (v8.x). This behavior tries to prevent any un-recognizable issues due to environment changes.iOS side
ENABLE_USER_SCRIPT_SANDBOXING
has been disabled due to errors outputs by flutter.This PR also patches the security issue: CVE-2023-39139
Implementation
Testing Instructions
Testing this pr's changes may rely on what dependencies has updated.
Here are some possible paths to test those changes:
information system
on theother
tab of the app. See if we can still browse normally in the school's information system without askinglogin again
.Downloads
page to see if it will ask permissions normally. Then, after approving all required permissions, try to download a file form ischool and open that downloaded file to see if these steps works.Finally consider trigger a release build to see if there's any error. (under appropriate environment)
Additional Notes
This PR is opened by experience. There's actually no any rapid requirement to do these change