Ios: Collabora view broken if Collabora not available

[MorrisJobke]

• having an abc.odt document in your Nextcloud
• having Collabora app enabled in your server
• having the collabora service not running (for whatever reason) on the server, so that the reverse proxy returns a 502 return code
• click on the abc.odt in the iOS app
• expected: I get a nice warning with "Can't reach the Collabora service - try again later" and a back button
• actual: completely white screen without any button or way to go back and []

This is how it looks. The only way out is to kill the app forcefully:

cc @marinofaggiana

[marinofaggiana]

@MorrisJobke, I tested the return of createLinkRichdocuments ... your test is strange ... the end point createLinkRichdocuments return yes but do not open file ? can you give me an account for test this condition?

[MorrisJobke]

@MorrisJobke, I tested the return of createLinkRichdocuments ... your test is strange ... the end point createLinkRichdocuments return yes but do not open file ? can you give me an account for test this condition?

I send them via e-mail to you ;)

[marinofaggiana]

@tobiasKaminsky have you resolved this issue ?

[MorrisJobke]

This is only in the iOS app or did I miss something?

[marinofaggiana]

I don't know .. but I want know from @tobiasKaminsky how (and if) he detect the collabora page

[tobiasKaminsky]

I fear that this will also happen on android.
We simply call richDocuments to get us a link. And then we are opening this link.
On Android it might look a bit nicer as we show a spinner until COOL is loaded (which then will never be).
And clicking back will also closes the webview.

But I do not see a quick possibility how to detect if the given link from rich documents app is valid and working, other than trying it…

[MorrisJobke]

This is fine, but it should be a better looking error than a white page without any button

[tobiasKaminsky]

For inspiration, @marinofaggiana
https://nextcloud.kaminsky.me/index.php/s/oFBDWoHtaZqsgqJ

[tobiasKaminsky]

@rullzer the direct link you generate returns [] and 204 (empty content).
This is not really possible to detect with android.
However any status >400 (error) would be a lot easier to detect.
Can this be changed?

[marinofaggiana]

For inspiration, @marinofaggiana
https://nextcloud.kaminsky.me/index.php/s/oFBDWoHtaZqsgqJ

Thanks Toby, already exist the activity when loading the Collabora but this issue is for:

@rullzer the direct link you generate returns [] and 204 (empty content).
This is not really possible to detect with android.

and with iOS .. @rullzer and this : [] ... ??

However any status >400 (error) would be a lot easier to detect.
Can this be changed?

yes ! Correct.

[tobiasKaminsky]

@marinofaggiana I am showing the loading spinner / screen as long until I receive via JS bridge "documentLoaded". As this will never be sent on a broken Collabora, it is at least a bit more "error handling".

[MorrisJobke]

With https://github.com/nextcloud/richdocuments/pull/382 I now get the "502 Bad Gateway" page of Nginx. cc @juliushaertl

[juliushaertl]

Ah so we need to check if the actual collabora frame is loading properly as well. :thinking:

[MorrisJobke]

@marinofaggiana Any update here - still broken.