Skip to content
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

Don't start Collabora Editor #11979

Closed
4 tasks done
koebi80 opened this issue Sep 20, 2023 · 10 comments
Closed
4 tasks done

Don't start Collabora Editor #11979

koebi80 opened this issue Sep 20, 2023 · 10 comments

Comments

@koebi80
Copy link

koebi80 commented Sep 20, 2023

⚠️ Before posting ⚠️

  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

  1. Start NextCloud App 3.26.0
  2. click on a office document (doc, docx, ods, ...)

Expected behaviour

The office document is opend in the Collabora Editor within the NextCloud.

Actual behaviour

The office document are downloaded to the device and then the "open with" dialog will apear.

In the last version of the app, the documents were opened for editing within the app without any problems.

Android version

8.0.0

Device brand and model

SHIFT5me

Stock or custom OS?

Stock

Nextcloud android app version

3.26.0

Nextcloud server version

26.0.2 / 27.1.0

Using a reverse proxy?

I don't know

Android logs

No response

Server error logs

No response

Additional information

These Apps are installed on the NextCloud Servers

Nextcloud Server 26.0.2:

  • Collabora Online - Built-in CODE Server 23.5.301
  • Nextcloud Office 8.0.4

Nextcloud Server 27.1.0:

  • Collabora Online - Built-in CODE Server 23.5.301
  • Nextcloud Office 8.2.0
@koebi80 koebi80 added the bug label Sep 20, 2023
@rzech
Copy link

rzech commented Sep 20, 2023

I can confirm this for a similar setup (NC 27.1.0, CODE 23.5.301, NC Office 8.2.0) on Android 13 (Nextcloud App 3.26.0)

@w9hdg
Copy link

w9hdg commented Sep 21, 2023

I believe this is a duplicate of #11975

@koebi80
Copy link
Author

koebi80 commented Sep 21, 2023 via email

@rzech
Copy link

rzech commented Sep 21, 2023

i think it is the same issue as in #11975 because the mentioned workaround worked for me:

sudo -u www-data php occ config:app:set richdocuments mobile_editing --value="yes"

@zpackrat
Copy link

Can confirm, latest updates to v26. The issue started with v3.26 of the client. 3.25 worked fine. Pixel 7 if it matters.

@thgoebel
Copy link
Contributor

thgoebel commented Sep 22, 2023

For me it started with the upgrade from Server 27.0 to Server 27.1, keeping the Android version at 3.25.0.
Notably for me the iOS Files app (4.8.6.4) is NOT affected.

Another symptom of this is in the "Create new file"-picker, where "Create new document/spreadsheet/presentation" options are now missing:

The occ command above (occ config:app:set richdocuments mobile_editing --value="yes") only fixed this symptom in the "Create new file"-picker for me. When I click on an .ods file, it still does NOT open in Collabora, but Android prompts me to chose an app.

@koebi80
Copy link
Author

koebi80 commented Sep 24, 2023

The parameter config:app:set richdocuments mobile_editing --value="yes" worked for me too.

Why has this parameter never had any influence on the ability to mobile edit Office documents before?

@BiglifeMatt
Copy link

Same on my setup (NC 27.0.2, CODE 22.05.18.1, NC Office 8.2.0) on Android 12 (Nextcloud App 3.26.0). No errors as others mention. Just cannot open the files in Collabora anymore. They want to open in local mobile apps. And the option to create a file is only .md file types.

@joshtrichards
Copy link
Member

The issue was fully fixed here: nextcloud/richdocuments#3184.

Hint to future readers: If occ config:app:set richdocuments mobile_editing --value="yes" does not fix the matter for you then you have a different issue and should look elsewhere / create a dedicated issue.

@thgoebel
Copy link
Contributor

then you have a different issue

FYI: I've narrowed my issue down to the fact that it appears when a file is downloaded (= set as available offline). I've opened #12039 for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants