Support

Connect your WebCalendar installation

1. Use an iPhone running iOS 17 or later and an existing WebCalendar account. Ask your administrator whether the compatible mobile API is installed and enabled. Not every WebCalendar installation includes it.
2. Enter the full HTTPS installation URL, including any subdirectory. For example: https://calendar.example.com/webcalendar.
3. Contempleau automatically adds /api.php/v1. A URL already ending in that suffix is accepted without adding it again. Do not include a username, password, query string, or fragment in the URL.
4. Continue and sign in with your WebCalendar username and password. The resulting device token is stored in Keychain; the password is not persisted.

The server needs a valid HTTPS certificate trusted by your iPhone and must be reachable from its current network. Check VPN access if your installation is private. Contempleau does not create accounts or connect to Apple Calendar or iCloud.

What you can create and edit

Browse the weekly agenda, years, months, days, and event details. Create and edit supported personal, accepted, non-recurring events when the server supports event writes and your account and device token have permission. The form supports title, date, timing/duration, location, and plain-text description.

Shared, recurring, linked, and continuation records, and invitations are read-only. Event deletion, recurrence creation/editing, participant management, tasks, and other users’ calendars are not supported.

New timed events use the account timezone returned by the server. Older compatible read APIs may lack the metadata needed for editing. After an event-write backend upgrade, sign out and sign in again to obtain a token with the new permissions; server read-only settings and account permissions still apply.

Troubleshooting

API unavailable or not found

Check the URL, including the installation subdirectory. Ask the administrator to confirm API enablement, Composer dependencies, migrations, PHP path handling, and forwarding of the Authorization header. An ordinary WebCalendar website working in a browser does not establish mobile API compatibility.

Username or password rejected

Check your credentials for that installation. Contact its administrator for password resets. If sign-in is accepted but the newly issued session is rejected, ask them to check API authentication and Authorization-header forwarding.

Session expired or no longer valid

Sign in again when prompted. The server decides whether a device token is valid. A network outage alone does not mean your account or calendar has been deleted.

Server or network errors; events will not load

Check connectivity, VPN, certificate validity, and server availability, then use Retry or pull to refresh. For rate limits, wait until the retry time shown. Persistent internal-server errors need the installation administrator’s attention.

Save unavailable or permission denied

Check that the event is a supported personal event. The administrator must deploy the event-write API and required transactional storage support, and allow writes for the account and token. Missing edit metadata is not permission to edit.

A save could not be confirmed

Check the calendar before retrying to avoid duplicates. The server may already have saved the change even if its response was lost. Use Check calendar and inspect the event before deliberately saving again.

The calendar is busy and changes were not saved

The app retains the draft in the open editor. Wait, then tap Save to retry. Closing the editor discards unsaved drafts; they are not stored as an offline backup.

What to include in an app issue report

• Your Contempleau version and iOS version.
• Steps to reproduce, what you expected, and what happened.
• Redacted error details or screenshots, if useful.

Do not send passwords, bearer tokens, or private calendar content. Remove personal information from screenshots and messages.

Sign-out is not account deletion

Account → Sign out removes the selected saved token on your iPhone and attempts server revocation. If revocation fails, ask the server administrator to revoke it. Sign-out does not delete your remote account/events or necessarily remove all nonsecret preferences or other servers’ saved credentials.

Direct account creation/deletion, password resets, server administration, permissions, backups, and server-data access/correction/deletion requests to the installation’s administrator. App support cannot administer independently operated servers. Read the Privacy Policy for more detail.