fix(mobile): correctly load via direct editing#5805
Conversation
6539065 to
3bb44ec
Compare
6edf79a to
4900e2f
Compare
Assisted-by: ClaudeCode:claude-sonnet-4-6 Signed-off-by: Elizabeth Danzberger <elizabeth@elzody.dev>
4900e2f to
8d7a123
Compare
| * legacy /apps/richdocuments/api/v1/document endpoint and should not | ||
| * see the editor in OCP\DirectEditing discovery responses. | ||
| */ | ||
| private const MIN_MOBILE_CLIENT_VERSION = 34; |
There was a problem hiding this comment.
why is this comment deleted? Is this not useful to know?
There was a problem hiding this comment.
IMO it is self-explanatory from the file itself. You can tell quite clearly that it is used only to expose the editor for mobile clients >=34
|
So at the risk of being really verbose: The What still fails:
Same symptom this PR fixes for opening, on the same entry-point family. Reachable from the shipping apps — Android hits
Fix (same shape as the I've not checked this code, so verify it please: 1.
|
|
Yes, we can file this as a separate issue and get that fixed as well. |
|
/backport to stable34 please |
Summary
The mobile apps should now receive the
loaded()event andOCSController::createDirect()should now always return properly for legacy (<34) clients and prevent a 404 error.Assisted-by: ClaudeCode:claude-sonnet-4-6
TODO
Checklist