There seems to be an issue in version 0.2.0 where the previous response is not being closed, causing an exception to be thrown and therefore leaving the access code in an undefined state for us (we don't know whether it was deleted or not). As this doesn't occur every time, I suppose this might be related to cases where an automated retry happens.
java.lang.IllegalStateException: cannot make a new request because the previous response is still open: please call response.close()
okhttp3.internal.connection.RealCall.enterNetworkInterceptorExchange (RealCall.kt:229)
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept (RetryAndFollowUpInterceptor.kt:66)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.kt:109)
com.seam.api.core.RetryInterceptor.retryChain (RetryInterceptor.java:43)
com.seam.api.core.RetryInterceptor.intercept (RetryInterceptor.java:28)
okhttp3.internal.http.RealInterceptorChain.proceed (RealInterceptorChain.kt:109)
okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp (RealCall.kt:201)
okhttp3.internal.connection.RealCall.execute (RealCall.kt:154)
com.seam.api.resources.accesscodes.AccessCodesClient.delete (AccessCodesClient.java:152)
com.seam.api.resources.accesscodes.AccessCodesClient.delete (AccessCodesClient.java:129)
There seems to be an issue in version
0.2.0
where the previous response is not being closed, causing an exception to be thrown and therefore leaving the access code in an undefined state for us (we don't know whether it was deleted or not). As this doesn't occur every time, I suppose this might be related to cases where an automated retry happens.