-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parce amplfy_outputs.json on IOS #1749
Comments
Acknowledging the issue. Can you please share the link to the documentation you are following? |
Answering my own question. I think you are trying to mention this documentation. |
Hey @yegenpres 👋 thanks for raising this! I was able to confirm this behavior and have marked this as a bug |
note: these properties should also be marked as required in the outputs schema for the password policy block https://github.com/aws-amplify/amplify-backend/blob/main/packages/client-config/src/client-config-schema/schema_v1.json#L59-L82 |
Yes, this doc. |
Describe the bug
It to redefine auth password cfnUserPool.policies like in official documentation.
json looks like this:
amplify_outputs.json does not contain property name of passwordPolicy object if value is set to false.
Then Swift Coding fail to decode this object as result initAmplify just fails, because official library expects this fields like required.
So we can every boolean value should be set to try or else it just miss in json file, and fail to parse it.
It means that output json should always generate fields with values set to false, or Codable struct accept optional parameters.
Steps To Reproduce
Expected behavior
Amplify should init success.
Amplify Framework Version
6.3.7
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.9
CLI version
12.12.4
Xcode version
15.4
Relevant log output
Is this a regression?
Yes
Regression additional context
Amplify gen 2
Platforms
iOS
OS Version
iOS 17+
Device
Any iOS device
Specific to simulators
Iphone 15 pro max
Additional context
No response
The text was updated successfully, but these errors were encountered: