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

Collabora not loading existing documents in app v3.27.0 #12338

Closed
4 tasks done
expert-geeks opened this issue Jan 3, 2024 · 7 comments · Fixed by #12349
Closed
4 tasks done

Collabora not loading existing documents in app v3.27.0 #12338

expert-geeks opened this issue Jan 3, 2024 · 7 comments · Fixed by #12349

Comments

@expert-geeks
Copy link

expert-geeks commented Jan 3, 2024

⚠️ 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. Upgrade Nextcloud android app to version 3.27.0
  2. Open document in app

Expected behaviour

Collabora should start and open the document as usual

Actual behaviour

App seems to try to open the document, but does not complete and hangs at the opening document screen. App hangs permanently and does not time-out. No error returned. CODE Admin console doesn't show the user attempting to log in.

Downgrade from v3.27.0 to v3.25.0 and the documents open as usual.

Android version

10

Device brand and model

OnePlus 5

Stock or custom OS?

Stock

Nextcloud android app version

3.27.0

Nextcloud server version

25.0.13

Using a reverse proxy?

Yes

Android logs

No response

Server error logs

There's nothing in the nginx error log, here are the access logs;

xx.xx.xx.xx - user [03/Jan/2024:17:14:34 +0000] "PROPFIND /remote.php/dav/files/user/path/ HTTP/1.1" 207 1331 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.27.0"
xx.xx.xx.xx - user [03/Jan/2024:17:14:34 +0000] "GET /ocs/v2.php/apps/files_sharing/api/v1/shares?path=%2FDocuments%2F&reshares=true&subfiles=true HTTP/1.1" 200 2480 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.27.0"
xx.xx.xx.xx - user [03/Jan/2024:17:14:36 +0000] "GET /ocs/v2.php/cloud/user?format=json HTTP/2.0" 200 566 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.27.0"

then nothing...

Additional information

logcat file doesn't seem to contain any information about app usage, there's plenty in there about signal strength etc but nothing that seems related to nextcloud. Is there a recommended 'filter' to use with logcat to generate useful logs ?

There doesn't appear to be an apk in releases for 3.26.0 (https://github.com/nextcloud/android/releases/tag/stable-3.26.0) or I would have tested that also.

@jakobroehrl
Copy link

Same problem.
After the update to 3.27.0 all office docs does not open. They are loading endless.
No problem with the 3.26.0

@joshtrichards
Copy link
Member

Reproduced in both v3.27 and master/latest Dev. Thank you for reporting!

@r4tt4
Copy link

r4tt4 commented Jan 6, 2024

+1 same problem here. Downgrade to 3.2.25 re-enables mobile editing again. Hope that will be fixed soon.

@joshtrichards
Copy link
Member

New document creation appears to work fine; just opening existing documents is broken.

@alperozturk96 The main change #12158, but that in theory shouldn't have changed any behavior.

@JonasMayerDev JonasMayerDev linked a pull request Jan 9, 2024 that will close this issue
1 task
@sentsev
Copy link

sentsev commented Jan 10, 2024

Sorry. I'm new here. Is it my imagination, or are you suggesting that users recreate all their documents so that they can use this version?

@joshtrichards
Copy link
Member

@sentsev No I was clarifying which use cases were failing. In any case, the bug has now been fixed. It'll be in the next minor release.

@sentsev
Copy link

sentsev commented Jan 10, 2024

@joshtrichards Thanks for explaining.

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

Successfully merging a pull request may close this issue.

5 participants