ZSH: trace trap ./apollo-ios-cli generate

[xLuciferSx]

Summary

I am currently on Apollo 1.3.1(iOS) and i am unable to generate the GraphQL files for the reason bellow.

ApolloCodegenLib/JavaScriptBridge.swift:343: Precondition failed: Expected JavaScript array but found: undefined
zsh: trace trap ./apollo-ios-cli generate

Version

1.3.1

Steps to reproduce the behavior

Download the latest version - 1.3.1
Go in terminal to your SPM and type the command - ./apollo-ios-cli generate

Logs

No response

Anything else?

Mac Studio M2 Max. Mac OS Ventura 13.4.1

[MaxFritzhand]

Facing this issue too

[xLuciferSx]

I've tried to downgrade to 1.2.0 and 1.0.6. All off this started on 1.0.6 and i thought that it might be related to Apollo being outdated but apparently it happens on every version.

[BobaFetters]

@xLuciferSx @MaxFritzhand There is likely something in your schema or an operation that is unexpected, we had an issue like this reported not long ago #3047 I recommend checking out that issue and using the sample project that @calvincestari provided to be able to breakpoint and debug specifically what the issue is.

Alternatively if you are able to share your schema/operations privately we can assist in debugging, if so you can send them to zach.fetters[at]apollographql.com

[xLuciferSx]

I've sent you an email. Thank you very much! @BobaFetters

[BobaFetters]

For future reference for others who may experience this issue, OP's issue was related to mismatches between fields defined in schema and fields being used/accessed in operations.

Closing this issue as no work is needed, for anyone experiencing this in the future the recommendation is to use the sample project provided in #3047 to aid in debugging and finding schema/operation issues

[BobaFetters]

Update on this, after further investigation I discovered an issue with how the errors reported from graphql-js are handled due to a max error limit, this was resulting in the precondition failure instead of getting proper error logs pointing to specific schema/operation issues. We will be updating the handling of the errors to resolve this and that work can be tracked in issue #3126