fix(package_info_plus): data serialization converts installTime to String instead of DateTime

[dharambudh1]

This commit addresses an issue where the installTime was not being properly serialized due to being a DateTime object. When attempting to convert the object to JSON, an error occurred as DateTime is not natively encodable. The installTime is now explicitly converted to a string before being included in the JSON, preventing the serialization failure.

Description

This PR addresses an issue where the installTime (a DateTime object) was not being properly serialized into JSON, causing errors when trying to encode the object. The installTime is now explicitly converted to a string before it’s included in the JSON, ensuring compatibility with the encoding process. This change prevents the "Converting object to an encodable object failed" error and allows for correct JSON handling.

Related Issues

• Fixes [Bug]: Unhandled Exception: Converting object to an encodable object failed: Instance of 'DateTime' #3461

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[miquelbeltran]

Thanks for catching this up. It is probably better to use toIso8601String() instead.

[miquelbeltran]

Seems that some tests need to be fixed as well.

[dharambudh1]

@miquelbeltran, I updated installTime format to ISO 8601 string for consistency (hope this helps with parsing and compatibility).

[miquelbeltran]

Github actions is showings lots of errors, please ensure that the project has no analysis errors and all tests pass

[dharambudh1]

@miquelbeltran, I'm almost there, but one of the GitHub Actions is failing. All tests work fine locally, and I believe the failing test isn't critical. Can we move ahead? Could you review my PR and merge it?

[vbuberen]

Don't worry about failing Android integration tests - they are flaky and having time outs not because of your changes.

[miquelbeltran]

Thanks for fixing the CI issues!

[miquelbeltran]

I changed the conditional access, since the variable is already checked if it was null.

I've added a test to check JSON conversion of the Data payload to ensure this doesn't break in the future.

[dharambudh1]

@miquelbeltran & @vbuberen, thanks so much for considering, reviewing, and merging the PR! I really appreciate the time and effort put into it. Looking forward to more collaborations!