-
Notifications
You must be signed in to change notification settings - Fork 11
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
Reply feature does not work properly #39
Comments
@NablaMetal Hello once again. Unfortunately my Nextcloud instance is currently down and I wouldn't be able to reproduce your issue, so can you please try grabbing any exceptions while responding with quick replies. Though probably the problem is that new notification APIs in S already dropped support of that APIs that I have used in this app, but it is still worth trying |
I'm not seeing anything suspicious in nextcloud logs, with level 0. Did you meant greping error on the server or the client (I mean the "nextcloud services" app) ? |
Yes, I mean grepping exceptions from client app as I do not really think that Nextcloud would change API for sending messages in talk on server side |
Sorry I don't know how to do that on Android, there's no log related option in the app and I'm no dev. |
Use provided link to the conversation instead of the object_id filed in the notification to extract the chatroom id. background in the settings_activity.xml was removed to make the app in the main branch run.
fix to issue #39 Reply feature does not work properly
Reply feature is fixed in 1.0-beta13 by @freeflyk |
I also am on GrapheneOS (latest) and latest NextcloudServices (v1.0-beta12)
Notifications are working on my device, including talk/spreed. However, the "Reply" functionality in the Android notification, doesn't send message. @TheDarkula do you still have this issue ?
Originally posted by @NablaMetal in #38 (comment)
The text was updated successfully, but these errors were encountered: