Releases: aws-amplify/amplify-android
Amplify Android 1.16.12
Amplify Android 1.16.11
Miscellaneous fixes
MatchAllQueryPredicateandMatchNoneQueryPredicateare made private. Customers should useQueryPredicates.all()andQueryPredicates.none(), instead. #1127- Fix for
SQLiteException: ambiguous column name#1130 - Use correct schema field in output when announcing cascading deletes #1131
- Store model name inside
QueryField. #1133
⚠️ Notice on Version Bump to 1.16.11
This release is identical to version 1.6.11.
On January 29th, the Amplify team accidentally released Amplify Android version 1.16.11, in place of 1.6.11. Due to technical constraints in publishing Maven artifacts, we have decided to continuing our versioning from this new base. Please note that no additional releases are planned between 1.6.11 and 1.16.11.
Amplify Android 1.6.11 (Deprecated)
This release is deprecated. Do not use this version.
This release is identical to Amplify Android 1.16.11. Please use it instead.
Amplify Android 1.6.10
DataStore
- Added support for delete by model type with predicate (#1106)
- Only include changed fields in update mutations (#1110)
Misc
Amplify Android 1.6.9
DataStore
- Put missing column name in a verbose log (#1068)
- Verbose log instead of warn when deleting a non existent item (#1081)
- Remove overloaded query method in favor of just one (#1092)
- fix: Publish
networkStatusevent at correct times (#1067) - fix: Defer
merger.mergeto avoid failure if outbox has mutation (#1082) - fix: Make PersistentMutationOutbox operations synchronized (#1085)
- fix: Publish each cascading delete (#1059)
- fix: Continue processing outbox items after removal (#1084)
Auth
- Add explicit error for signin cancelation (#1073)
API
Amplify Android 1.6.8
DataStore
- Send unix epoch in
OutboxMutationEventinstead ofTemporal.Timestamp. (#1052) (Thanks @kjones!) - fix:
MutationProcessor- Fix missing schema onSerializedModelmutations. (#1051) (Thanks @kjones!) - fix: resolves an app crash that occurred when going offline (#1039)
- fix: ignore foreign key error during sync (#1058)
- fix: Query results should be sorted when sort order provided (#1049)
API
- fix: response deserialization should only skip top level for specific response types (#1062)
Other
- Added IDE codestyle to match checkstyle expectations (#1048)
Amplify Android 1.6.7
DataStore
-
Encountering error while publishing mutation no longer crashes DataStore. See PR #976.
-
Fixed a race condition in the sync engine. See Issue #1010.
-
Storage engine behavioral updates:
-
Improved Flutter support:
Auth
- Now supports specifying custom browser for web UI. See PR #1030.
API
- Fix Rest API's DELETE operation. See Issue #1028.
Amplify Android 1.6.6
Minor improvements to the DataStore:
- Fixes issue #1012, aligning the
OutboxMutationEventto the design on iOS (See PR #1015.) - Fixes issue #1011, addressing a failure while merging AppSync deletions, when being used by Flutter (See PR #1014.)
- Improves the recovery suggestions in the error messages arising when subscriptions fail (See #1016.)
Amplify Android 1.6.5
Fixes various bugs in the DataStore.
Fixes benefiting all DataStore customers:
- #993 addressing #984, "Error events in DataStore.observe cause an app crash"
- #1000, "Prevent NPE while inspecting GraphQL errors," resolving #977
Fixes benefiting customers who use the Android DataStore via Flutter:
- #1004 resolving #994, "Remote delete mutations are not getting saved locally"
- #1001 addressing #998, "ClassCastException when saving Temporal types from Flutter"
- #1007 addressing #997, "
ClassNotFoundException: booleanon app start"
A complete manifest of changes since 1.6.4 can be seen here.
Amplify Android 1.6.4
Fixes a DataStore bug where-in Flutter users publishing connected models to AppSync could fail.