MobilePay Purchase flow fails - State is null

[duckth]

MobilePay purchase flow fails when trying to create MobilePayPaymentDetails object after geting response from PurchaseRepository
PurchaseRepository.initiatePurchase returns a response with state = null and causes an exception:
CastError (type 'Null' is not a subtype of type 'String' in type cast)

[TTA777]

Just to add to this, in my older version of the generated code, state is correctly marked as nullable. Whether this change is caused by a change in the library that generate the httpClient code, or the OpenApiSpec I'm not sure of yet

[TTA777]

Looked at this a bit more, findings so far:

• Unable to reproduce on my environment with my current versions of flutter (3.0.1), dart (2.12.2), and swagger_dart_code_generator (http client generator, 2.5.2)
• Upgrading swagger_dart_code_generator to 2.7.0 reproduces error on my machine, without updating flutter or dart
• By adding "nullable": true, to the state property in the OpenApiSpec, it is correctly marked as nullable in the generated code, though this causes other issues on my machine

Conclusion so far:
It seems the package we use to generate the code has received an update where it is now following the spec more closely. Previously it was marking all the properties as being nullable in this class, which was not in accordance to the spec. The source of the problem then appears to be from the backend not generating the OpenApiSpec correctly, since state is not marked as Nullable, despite being it.

However, it does appear that some updates will be required on the app side as well to accommodate this change in the generated code. Those of us using older versions of flutter/ dart might also need to update in order to get everyone's dev environment inline with the rest.

[jonasanker]

Bug is introduced in the package upgrade of swagger_dart_code_generator to 2.7.8 in Pull Request #348

Analog Core does not support nullability officially yet. This requires an update of the codebase. See issue AnalogIO/analog-core#82

Probably is it the best to rollback the package to the old version for now