-
Notifications
You must be signed in to change notification settings - Fork 29
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
Instantiating Void
does no longer work with AGP 8
#541
Comments
One possible solution I could imagine is to provide a new type like |
Signed-off-by: Stefan Niedermann <info@niedermann.it>
Signed-off-by: Stefan Niedermann <info@niedermann.it>
Reminder that updating ProGuard rules might be necessary after fixing this: https://github.com/nextcloud/Android-SingleSignOn/pull/545/files |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Are you aware of any of those used by the notes app maybe? Than I could give them a try |
@AndyScherzinger please do not hesitate to call me as soon as possible if you have any questions, because I can not guarantee that I continue to understand this complex topic if we don't care about it for another year 😅😅 I have a guest account on the talk instance on cloud.nextcloud.com which we can use. I have finally been able to understand and reliable reproduce the original issue:
You will see, that one and the same request will be successfull when using This was the reason, we introduced the Understanding this, we need to get rid of the Here we have two options:
The first solution is okay for me, because we are currently migrating Deck Android from |
I'd have the tendency to say we should go for Option 1 but would leave the final decision and say to you (being the most prominent consumer of the API) and @tobiasKaminsky being in the lead of another app affected by this (notes client) |
Thank you for your feedback! Personally I would recommend Option 2 because
Both options are valid though and both are a breaking change. @tobiasKaminsky looking forward to a decision so I can clean up all the branches and finally fix this issue 🚀 Of course I can also offer you a call to explain the topic before if you want 🙂 |
Well, if you put it this way, than option 2 seems to be favorable since it is more flexible in terms of devs having more of a choice on how to implement it - while yeah this can be seen as a good or bad thing. |
I also like Option 2, as then there is still a breaking change to used EmptyResponse instead of Void, but all other stays the same. |
Thanks for this great work! |
fix(void): Introduce new EmptyResponse type as successor for Void (#541)
Awesome, thanks! Here my proposal for the next steps:
|
Shouldn't we go straight for #629 @stefan-niedermann ? |
@AndyScherzinger absolutely! #629 is from today and that's what I meant with "I'll do a more up to date variant" 😄 However, I definitely wanted to get Java 17 in, too (it's really about time). But the Drone testing environment threw an error because it runs on Java 11. Any help is highly appreciated as I don't quite understand the |
Talk Android runs on Java17 already -> https://github.com/nextcloud/talk-android/blob/master/.drone.yml But apart from that @tobiasKaminsky knows the drone containers best |
We implemented a hacky way to instantiate
Void
using reflection. This does no longer work with new Java versions and encumbers users while upgrading to AGP 8 and newer Java versions.Why did we implement this at all? See comment, TLDR; Using REST endpoints that return an empty body as
Observable<Void>
leads to a crash. (See #231).CC @desperateCoder @David-Development @AndyScherzinger @tobiasKaminsky
The text was updated successfully, but these errors were encountered: