Skip to content
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

remove IllegalStateException from IDLE / TERMINATED state in terminate and responseCallback #4383

Conversation

WilliamsDHI
Copy link

@martinbonnin Here is the PR in reference to this thread.

@apollo-cla
Copy link

@WilliamsDHI: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

@netlify
Copy link

netlify bot commented Sep 12, 2022

👷 Deploy request for apollo-android-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 4b0c44b

@martinbonnin
Copy link
Contributor

Hi 👋 thanks for opening this. As this more of a workaround than an actual fix for the root cause, I'm a bit reluctant to merging this as-is, even if 2.x is in maintainance mode. What I can offer is to publish a 2.5.13-absent-callback version with the fix to an alternate repsy.io repository. This way you can test it and let us know how that works for you before we decide what to do with the release-2.x branch? How does that sound?

@WilliamsDHI
Copy link
Author

That sounds great and I think would serve our purposes. We are really just looking for a work-around until we have bandwidth to update and refactor our app to Apollo 3.

@martinbonnin
Copy link
Contributor

Sounds good. It's getting a bit late here but I'll do that first thing tomorrow.

@martinbonnin
Copy link
Contributor

Hi 👋 The 2.5.14-absent-callback version should be available now at https://repsy.io/mvn/mbonnin/default/com/apollographql/apollo/apollo-runtime/2.5.14-absent-callback/.

Add the repsy repo:

repositories {
  maven("https://repo.repsy.io/mvn/mbonnin/default")
}

and use in dependencies:

dependencies {
  implementation("com.apollographql.apollo:apollo-runtime:2.5.14-absent-callback")
}

@martinbonnin martinbonnin added the ⌛ Waiting for info More information is required label Sep 14, 2022
@WilliamsDHI
Copy link
Author

As expected, no issues with this absent-callback version. We're using in develop now and will be pushing a hotfix soon to production with this version. Thanks again.

@martinbonnin
Copy link
Contributor

Nice! Thanks for the update!

@martinbonnin
Copy link
Contributor

@WilliamsDHI any news from production? Is everything looking good?

@WilliamsDHI
Copy link
Author

@martinbonnin Because the crash has stabilized, we are not putting out a hot fix. This update will now go in production in a few more weeks with a different release. But so far things are working well in our test environment.

@WilliamsDHI
Copy link
Author

@martinbonnin The 2.5.14-absent-callback version has been in production for a week now and is looking very good. Please keep it up and we'll continue to use it. If the merge or another fix is made in the future to Apollo 2 then we'll update our version again.

@martinbonnin
Copy link
Contributor

Thanks for the update :). I'll merge this PR and it'll be part of the next 2.x release.
Thanks again for all the investigations!

@martinbonnin martinbonnin merged commit deee859 into apollographql:release-2.x Oct 25, 2022
@WilliamsDHI WilliamsDHI deleted the possibleClientFatalExceptionCrashFix branch November 10, 2022 14:31
@martinbonnin
Copy link
Contributor

This is fixed in #4383 and will be released in 2.5.14

@martinbonnin martinbonnin added ✔️ Fixed in SNAPSHOTs and removed ⌛ Waiting for info More information is required labels Nov 15, 2022
@WilliamsDHI
Copy link
Author

This is fixed in #4383 and will be released in 2.5.14

Awesome! Any timeline for a 2.5.14 release?

@martinbonnin
Copy link
Contributor

Not much activity these days in the release-2.x branch. I guess we could do one this week unless something comes up. I'll double check internally if we have anything else planned for 2.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants