SHA256
Yuvomi Mobile Contributors
40a7962307
Replace current wrapper claims with native architecture/security/build evidence, preserve historical documents, track all thirty pages and explicit release gates, correct brand attribution and provide the twelve-section delivery report without claiming completion. Native signing remains paused and Apple application/device validation outstanding.
42 lines
2.2 KiB
Markdown
42 lines
2.2 KiB
Markdown
# Native server compatibility
|
|
|
|
Reference: Yuvomi 2.78.0 at
|
|
`10bfef7686ed7303b4c74c7fcc55a5eb16356c9d`. No general server-version range or
|
|
complete native feature compatibility is certified.
|
|
|
|
Enter a root HTTPS hostname, optionally with a custom port. HTTP, embedded
|
|
credentials, query/fragment configuration and subpath deployments are rejected.
|
|
Use a valid system-trusted TLS certificate and reachable VPN/LAN connectivity.
|
|
No certificate bypass or proprietary mobile service is introduced.
|
|
|
|
The native client probes the real public `/api/v1/version` and
|
|
`/api/v1/auth/oidc/config` shapes. Anonymous metadata does not disclose the server
|
|
version. An authentication proxy returning redirects/HTML instead of those JSON
|
|
contracts is unsupported, not silently treated as a valid Yuvomi API.
|
|
|
|
## Authentication
|
|
|
|
The implemented native slice uses setup/password login, the existing two-factor
|
|
verification endpoint, `/auth/me`, session cookies, CSRF headers and logout.
|
|
Passwords are not stored. Native session persistence is separate from browser
|
|
storage and protected by the platform keystore/keychain.
|
|
|
|
**Native SSO is not implemented yet.** The old wrapper's local-IdP WebView result
|
|
does not apply to this client. The existing server protocol does not provide a
|
|
generic browser-to-native session exchange for arbitrary self-hosted hosts; a
|
|
reviewed solution is required. SSO-only deployments cannot currently use this
|
|
native preview. Reset and invitation workflows also remain pending.
|
|
|
|
Only initial dashboard/tasks/notes/shopping capabilities are implemented; see the
|
|
[parity tracker](native-parity.md) for precise gaps. The complete server UI is not
|
|
embedded to fill those gaps. Read-only and denied module permissions affect
|
|
native controls; the server remains the enforcement point.
|
|
|
|
## Notifications, files and offline
|
|
|
|
Native remote push, uploads/camera/download/export and offline caching/editing
|
|
are not current native capabilities. The old wrapper's file handlers and the
|
|
PWA service worker are not part of the native renderer. No fake registration or
|
|
automatic offline mutation replay is supplied. Optional existing server-side
|
|
ntfy/Gotify/email integrations remain independently operated upstream features.
|