Dane Pilcher
Dane Pilcher
This looks like an issue with the Amplify XCode helpers. The Amplify XCode helper assumes that the API category is in use. https://github.com/aws-amplify/amplify-swift/blob/5ddf98c0ea6e2435d4be78a21c3f619a2f2a2eeb/AmplifyTools/AmplifyXcode/Sources/AmplifyXcodeCore/Commands/CommandImportModels.swift#L19
As a workaround, you can disable the addition of `__typename` in the query. In your `.graphqlconfig.yml` file set `typenameIntrospection` to false. ``` projects: typename: extensions: amplify: typenameIntrospection: false ``` Another...
For your first issue please refer to this comment on a similar issue: https://github.com/aws-amplify/amplify-category-api/issues/1338#issuecomment-1471896343 I'm not certain on the second issue. I found this thread with a similar issue. https://github.com/aws-amplify/amplify-js/issues/8738
Have you tried the suggestion in https://github.com/aws-amplify/amplify-js/issues/8738#issuecomment-901276845?
This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable...
amplify codegen generates empty API.ts and non-typescript operation files in github actions workflow
May be resolved by https://github.com/aws-amplify/amplify-codegen/pull/690. Requires testing.
amplify codegen generates empty API.ts and non-typescript operation files in github actions workflow
Can anyone confirm if this is still an issue?
I was not able to reproduce the issue with the schema from the project identifier. I uncommented the `user` field on the `User` and `Card` field and was still able...
I was able to reproduce this issue and I marking this as a bug.
Hi @sescotti, the issue was transferred from amplify-cli to amplify-codegen. The same thread is preserved when an issue is transferred (a new ticket is not created).