[Halted] Upcoming changes that impact getting and setting memberships and access levels

[Phil_Seeman]

Hi @anon34195150,

@anon34195150

Is it possible that the requests that I make with the help of java Asana client will stop working in the future due to the api changes?

Yes! Per this timeline above, they will stop working on 3/10 unless you add an Asana-Disable="new_memberships" header, and they will stop working altogether on 4/19.

@anon34195150

Are there going to be some updates of the java Asana client so that it will start utilizing the new version of asana memberships endpoints?

I’m sure there will be, but the question of course is, when? @sasha_f @Andrew-asana ?

@anon34195150

Is it possible to turn off these warnings somehow now?

Not sure but perhaps if you add the header I mentioned above, it might stop the warnings (though I wouldn’t bet on it).

FYI if you want to set the header in the current Java client, this post shows an example of how you can do that:

Java Client: Sometimes a task creation request returns null instead of throwing the actually occurring error

@sasha_f sry for the long delay (I was on holidays :D). Yeah the taskRequestBuilder is part of a selfWritten library - I modified my example to use the plain java asana-api-client which can reproduce the described null behaviour (as described before it can take up to a few hundred runs) @Unroll def "taskCreation sometimes returns to null if it would fail with an error otherwise - v2 - #times"() { setup: def connectTimeout = 90000 def readTimeout = 90000 …