Release Notes for Flutter SDK version 1.1.7 #7635
Closed
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.
Release Notes for Flutter SDK version 1.1.7
Release Date - 21st May 2025.
Fixes Github Issue #144 - Up to version 1.1.6, the
setFlushPolicies
method inadvertently overwrote theConfiguration.collectDeviceId
property. This issue has been resolved in version 1.1.7.Fixes Github Issue #147 - The
compileSdkVersion
in thebuild.gradle
file has been updated from 31 to 35. Previously, this caused the following error:Android build error "Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type 'android.content.pm.ApplicationInfo?"
. This update resolves the issue withcompileSdkVersion 35
.Fixes Github Issue #138 - Prior to version 1.1.7, the version field returned the browser's version string instead of the app version from
pubspec.yaml
. Sincepubspec.yaml
is a build-time configuration file and not accessible at runtime (especially in browser environments), this was expected behavior.As of version 1.1.7, if the following tag is added to
<project-root>/web/index.html
:<meta name="app-version" content="1.2.3">
the app will return the value in the
content
attribute.Note: This value should be manually synchronized with the version in
pubspec.yaml
.Fixes Github Issue #152 and #98 - Until version 1.1.6, the
integrations: {}
field was missing in the data payload sent to the Segment server. This has been addressed in version 1.1.7.Fixes Github Issue #157 - Resolves the
Concurrent modification during iteration: Instance(length: 6) of '_GrowableList'
error that occurred when multiple plugins were added simultaneously.