Aaron Ritter

@alex-fusionauth we are currently working on the FusionAuth 1.50.1 upgrade, we fixed most of it but are still looking into some unexpected behaviour https://github.com/FusionAuth/fusionauth-android-sdk/pull/60. So if you don't find anything...

@alex-fusionauth added a few comments, otherwise mostly merged and updated a few other additional wrong links/references. The `Not authorized` issue mentioned by you above is something which we did not...

We're good to go. @alex-fusionauth

Thanks a lot for the additional review @mark-robustelli I've updated most of your feedback, and as well fixed the styling which was fixed for all previous versions but not 1.51...

This Addresses: https://github.com/FusionAuth/fusionauth-issues/issues/2256

Addresses: https://github.com/FusionAuth/fusionauth-issues/issues/2256

closing, new version is developed under https://github.com/FusionAuth/fusionauth-site/pull/2470

This issue is still valid with 0.1.103 in combination with fusionauth 1.49.2. I experience the exact same problem every time applying.

related issues https://github.com/FusionAuth/terraform-provider-fusionauth/issues/256 https://github.com/FusionAuth/terraform-provider-fusionauth/issues/63 The current provider only validates for schema.TypeMap: https://github.com/FusionAuth/terraform-provider-fusionauth/blob/5698966878108b4a260a8aa49744ffa49f370d1e/fusionauth/resource_fusionauth_application.go#L91-L95 Where for user.data it does some json related function in dataToUserRequest: https://github.com/FusionAuth/terraform-provider-fusionauth/blob/5698966878108b4a260a8aa49744ffa49f370d1e/fusionauth/resource_fusionauth_user.go#L130-L133 with jsonStringToMapStringInterface https://github.com/FusionAuth/terraform-provider-fusionauth/blob/5698966878108b4a260a8aa49744ffa49f370d1e/fusionauth/helpers.go#L69-L91 and userResponseToData: https://github.com/FusionAuth/terraform-provider-fusionauth/blob/5698966878108b4a260a8aa49744ffa49f370d1e/fusionauth/resource_fusionauth_user.go#L186-L190...

@TomKimber thanks for the recent update. I wanted to update the ticket to reconfirm the bug with 0.2.0, when not defining it the plan crashes because it is checking the...