Approval request created but no UI available to approve/reject (Nextcloud 33, Approval 3.1.0)

[PeViz]

Title

Approval request created but no UI available to approve/reject (Nextcloud 33, Approval 3.1.0)

Describe the bug

An approval workflow can be triggered successfully, but there is no UI available for approvers to approve or reject the request.

The approval request appears correctly in:

• the Dashboard widget ("Pending approvals")
• the file activity log

However, there is no Approval section in the file details sidebar, and no Approve / Reject actions appear in the file action menu.

As a result, the approval request exists but cannot be processed by the approver.

---

Steps to reproduce

1. Install and enable the Approval app.
2. Create a new approval workflow.
3. Configure:
   • Requesters
   • Approvers
   • Pending tag
   • Approved tag
   • Rejected tag
4. Add the pending tag to a file to trigger the approval request.
5. Open the file as a user who is configured as an approver.

---

Expected behaviour

When opening the file as an approver, there should be a UI to process the request, such as:

• an Approval section in the file sidebar, or
• Approve / Reject actions in the file action menu

---

Actual behaviour

• Approval request is created successfully.
• Request is visible in:
  • Dashboard ("Pending approvals")
  • File activity log

However:

• No approval section appears in the file details sidebar
• No Approve / Reject actions appear in the file action menu
• The request cannot be processed.

---

Environment

• Nextcloud version: 33
• Approval app version: 3.1.0

---

Additional context

The workflow backend appears to work correctly because the approval request is created and visible in both the dashboard and the activity log.

However, the approval UI components are not registered in the Files frontend, so approvers have no way to approve or reject the request.

This looks like a frontend integration issue with the Files UI rather than a workflow configuration problem.

---

Optional debugging information

If needed, I can also provide:

• Output of occ app:list
• Browser console logs
• Nextcloud server logs
• Screenshots of the dashboard and file sidebar

[nlublovary]

Same here NC 33.0.0.16 & Approval 3.1.0. Turned on debug and see no errors in the log. Checked in webdev, approval-approvalTab.mjs is being loaded & no errors. Other apps for instance Versions or Libresign do appear in the sidebar. I tried to disable every app and keep only Approval enabled, still Approval refuses to show up in the sidebar. Approval Workflow in the config does work and adding tag manually triggers the Approval request, just nothing appears in Files to approve/reject the request.

[PeViz]

Thanks for confirming that you see the same behaviour.

In my setup the situation is the same: the approval request is created successfully and appears in the Dashboard widget and in the file activity log, but there is no approval UI available anywhere (no sidebar section and no Approve/Reject actions in the file menu). So currently there is no way to actually process the request.

I also checked the browser console and network panel and did not see any obvious errors. The approval JavaScript modules seem to load, but the sidebar component never appears.

Could you suggest what additional checks or debugging steps would help to narrow this down?
For example:

• specific entries to look for in nextcloud.log
• database tables related to approval state
• a way to verify whether the sidebar hook is being registered correctly
• any debug flags for the Approval app

One more detail that might be relevant: this instance was not a fresh installation.
It has been upgraded gradually from Nextcloud 30 → 31 → 32 → 33.

Could this possibly affect the registration of the Approval sidebar integration or leave some outdated configuration behind?

If needed I can also provide:

• occ app:list
• screenshots
• logs
• steps to reproduce on my instance.

Thanks for any hints on what to check next.

[lukasdotcom]

Hi @PeViz and @nlublovary,

This is fixed in #380 which was released in v3.2.0 that was released today. If you have any other issues feel free to ping me.