[v1.0.0 Alpha] 'Sendable' class 'JavaScriptError' cannot inherit from another class other than 'NSObject'

[TizianoCoroneo]

Bug report

I'm trying out the new alpha version for v1.0.0 using Xcode 13.3 beta. I encountered this error while trying to run the codegen using Swift Scripting.

Versions

Please fill in the versions you're currently using:

• apollo-ios SDK version: v1.0.0-alpha-1
• Xcode version: 13.3 beta 1
• Swift version: 5.6
• Package manager: SPM

Steps to reproduce

Try to run a Swift Scripting setup of the Apollo codegen.

[calvincestari]

Thanks for digging into the alpha so quickly @TizianoCoroneo and for the PR, much appreciated.

[Jerrot]

The issue already exists on v0.5.0 with Xcode 13.3 beta 1.

[calvincestari]

@Jerrot - this is now fixed in main, it will go out in release 0.51.0 if you need a tagged release.
@TizianoCoroneo - I've also merged main into release/1.0 so the alpha has the fix too.

[Jerrot]

Great, thanks @calvincestari and @TizianoCoroneo as well.

[deepcodingios]

I could see this error getting resolved but I am facing "Missing package product 'ApolloCore'" error now.

[andyBettis]

I'm seeing this issue with Xcode 13.3 (13E113) using 0.41.0. If I move up to 0.51.0 I get a whole bunch of errors. Any advice?

[TimoWaelischIdealo]

I'm seeing this issue with Xcode 13.3 (13E113) using 0.41.0. If I move up to 0.51.0 I get a whole bunch of errors. Any advice?

The latest release is 0.51.2, maybe try that first. Works just fine here with Xcode 13.3.

[calvincestari]

@andyBettis it really depends on what those errors are. There are a lot of breaking changes between 0.41.0 and 0.51.0.

[andyBettis]

Yes, all sorted, I just had to follow the changes. Thanks for your help.

[jwoodard4-chwy]

I am still getting this issue after upgrading to 0.51.2 and I'm using Xcode 13.3. What is causing this?

error: 'Sendable' class 'JavaScriptError' cannot inherit from another class other than 'NSObject'

[calvincestari]

I'm really not sure @jwoodard4-chwy. Take a look at the code in your dependency version of apollo-ios/Sources/ApolloCodegenLib/Frontend/JavaScriptBridge.swift. Verify that you've got @unchecked Sendable in the definition of JavaScriptError.

[strahinja-mem]

I am still getting this issue after upgrading to 0.51.2 and I'm using Xcode 13.3. What is causing this?

error: 'Sendable' class 'JavaScriptError' cannot inherit from another class other than 'NSObject'

I'm having the same problem here. I did check JavaScriptBridge.swift and I do have @unchecked Sendable.

[calvincestari]

Are you able to replicate this in a standalone sample project you could share with me? I'm not able to reproduce the error on the latest version.

[donnywdavis]

We just updated to from version 0.39.0 to 0.51.2 and I am seeing this error now. We are still using Xcode 13.1. The weird thing for us, is that I only see this error in our CI environment, but everything works fine locally. 🤔

One thing to note is that we are using the Codegen Package Template to handle the schema download and codegen scripts.

Update:
Turns out the fix for me was to update the Apollo CLI node package to the latest version of 2.33.11. Once I did that then everything started working again.

[jwoodard4-chwy]

Donny: Is the CI environment using the same version of Xcode you are? I ran into this last month (using the App Store version of Xcode, which bundles Swift 5.6 – see https://swiftversion.net for more info) and had to downgrade to Xcode 13.2 to get it to build. Chris Woodard Practice Hub team From: Donny Davis ***@***.***> Date: Wednesday, May 11, 2022 at 4:15 AM To: apollographql/apollo-ios ***@***.***> Cc: James Christopher Woodard ***@***.***>, Mention ***@***.***> Subject: Re: [apollographql/apollo-ios] [v1.0.0 Alpha] 'Sendable' class 'JavaScriptError' cannot inherit from another class other than 'NSObject' (Issue #2146) We just updated to from version 0.39.0 to 0.51.2 and I am seeing this error now. We are still using Xcode 13.1. The weird thing for us, is that I only see this error in our CI environment, but everything works fine locally. 🤔 — Reply to this email directly, view it on GitHub<https://protect-us.mimecast.com/s/MmZ2CNkBjBIpNZM6hmDMaT?domain=github.com>, or unsubscribe<https://protect-us.mimecast.com/s/Gsc1COYDkDSkAN2OHvfACO?domain=github.com>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[strahinja-mem]

We just updated to from version 0.39.0 to 0.51.2 and I am seeing this error now. We are still using Xcode 13.1. The weird thing for us, is that I only see this error in our CI environment, but everything works fine locally. 🤔

One thing to note is that we are using the Codegen Package Template to handle the schema download and codegen scripts.

Update: Turns out the fix for me was to update the Apollo CLI node package to the latest version of 2.33.11. Once I did that then everything started working again.

Isn't the latest version 2.33.04? I still have this error, tried everything from this post.

[calvincestari]

The latest release is 2.34.0 however apollo-ios is pinned to use 2.33.9.

@strahinja-mem it would be worth it to try again removing any interim build, I've found that to be the most problematic.

[strahinja-mem]

The latest release is 2.34.0 however apollo-ios is pinned to use 2.33.9.

@strahinja-mem it would be worth it to try again removing any interim build, I've found that to be the most problematic.

Sure, I can try that - What do you mean by interim build?

[calvincestari]

The prebuilt artifacts that the compiler uses to speed up compilations between builds. In an Xcode project these are probably in the DerivedData folder and on an SPM project they're in the .build/ and .swiftpm/ folders.

[strahinja-mem]

I delete /DerivedData at least once a month, and I did try removing ~/Library/Caches/org.swift.swiftpm/ now, unfortunately, no luck. 😕

[calvincestari]

What about in the root of the folder where the Package.swift file is? There should be .build and .swiftpm folders in there too.

[strahinja-mem]

I don't see those, tried searching too.

[calvincestari]

@strahinja-mem are you able to replicate this build error in a new standalone project?

[strahinja-mem]

I tried running the same project on a different Mac, and it worked, so yeah, this has something to do with my cache. The question is, which cache since I tried both reinstalling the Xcode and re-cloning the repo. 🤔

[ahaTB]

@strahinja-mem Any updates on this issue?

[strahinja-mem]

No unfortunately, I still run the script from my older Mac.