datastore adds UTC mark to AWSTime values even when they don't have it on android - next

[ragingsquirrel3]

Description

In the next branch on Android, if I have a model with type of AWSTime and I save a time that does not include timezone (which is optional), the version of the model that I query from the datastore will always include "Z" to indicate UTC.

Expected: AWSTime values respect inclusion/omitting timezone as saved

This is on next branch (built with aft). I suspect the issue is with amplify-android but will raise issue over there after collecting a little more data.

Categories

• [ ] Analytics
• [ ] API (REST)
• [ ] API (GraphQL)
• [ ] Auth
• [ ] Authenticator
• [X] DataStore
• [ ] Storage

Steps to Reproduce

      final now = TemporalTime.now();
      print(now.toString()); // => "21:37:56.955359000"
      final model =
          ModelWithAppsyncScalarTypes(awsTimeValue: TemporalTime.now());
      await Amplify.DataStore.save(model);

      var queriedModels = await Amplify.DataStore.query(
          ModelWithAppsyncScalarTypes.classType,
          where: ModelWithAppsyncScalarTypes.ID.eq(model.id));
      print(queriedModels.first.awsTimeValue); // => "21:37:56.957149000Z"

Screenshots

No response

Platforms

• [ ] iOS
• [ ] Android
• [ ] Web
• [ ] macOS
• [ ] Windows
• [ ] Linux

Android Device/Emulator API Level

No response

Environment

n/a

Dependencies

n/a

Device

android emulator

OS

n/a

Deployment Method

Amplify CLI

CLI Version

No response

Additional Context

No response

Amplify Config

graphql config

[HuiSF]

Is this happening only in Android? If I remembered correctly, amplify-ios datastore enforces this iso8601 string format too before store data, time strings into local DB.

[ragingsquirrel3]

Only happening in Android on next.