Skip to content

Mobile App Issues

Having trouble with the Clefora mobile app? Find your issue below for steps to resolve it.


Problem: The app closes immediately after opening, shows a white screen, or becomes unresponsive.

Solutions:

  1. Force-close and reopen. Swipe the app away from your recent apps list, then open it again.
  2. Restart your device. A restart clears temporary issues that can cause app instability.
  3. Update the app. Go to the App Store (iOS) or Google Play (Android) and check for updates. Crashes are often fixed in the latest version.
  4. Check available storage. If your device is nearly full, the app may not have enough space to run. Free up storage and try again.
  5. Reinstall the app. Delete the app and install it again from the App Store or Google Play. Your data is stored in the cloud, so nothing is lost.

Problem: You’re not receiving notifications for new messages, lesson updates, or invoices.

Solutions:

  1. Check app notification permissions. Go to your device settings:
    • iOS: Settings → Notifications → Clefora → ensure “Allow Notifications” is on
    • Android: Settings → Apps → Clefora → Notifications → ensure notifications are enabled
  2. Check in-app notification settings. Open Clefora → Settings → Notifications and confirm the categories you want to receive are turned on.
  3. Check Do Not Disturb. If your device is in Do Not Disturb or Focus mode, notifications may be silenced.
  4. Check battery optimisation (Android). Some Android devices aggressively restrict background apps. Go to Settings → Battery → Clefora and select “Unrestricted” or “Don’t optimise”.
  5. Sign out and sign back in. This refreshes the push notification registration.

Problem: Changes made on the Hub don’t appear in the mobile app, or vice versa.

Solutions:

  1. Check your internet connection. Syncing requires an active connection. Open a browser on your device to verify you’re online.
  2. Pull to refresh. On most screens, pull down to force a sync with the server.
  3. Force-close and reopen. This re-establishes the real-time connection.
  4. Check for app updates. Older app versions may have sync issues that have been fixed.

Problem: The Google or Apple sign-in flow fails or loops back to the sign-in screen.

Solutions:

  1. Check your internet connection. SSO requires a connection to Google or Apple servers.
  2. Update the app. Authentication issues are often resolved in app updates.
  3. Make sure you’re using the correct account. If you have multiple Google accounts on your device, the wrong one may be selected. Check which account is being used during the SSO flow.
  4. Clear the app cache.
    • iOS: Delete and reinstall the app.
    • Android: Settings → Apps → Clefora → Storage → Clear Cache.
  5. Check for system updates. Google and Apple SSO rely on system-level services that may need updating.

Problem: The app takes a long time to load screens, or buttons and gestures feel delayed.

Solutions:

  1. Check your internet connection. A slow connection causes delays when loading data.
  2. Close other apps. If your device is running many apps simultaneously, performance may suffer.
  3. Restart your device. This frees up memory and can improve app performance.
  4. Update the app. Performance improvements are included in regular updates.

Offline mode — what works without internet?

Section titled “Offline mode — what works without internet?”

Problem: You want to use Clefora when you don’t have an internet connection.

What’s available offline:

  • Viewing cached data: Previously loaded lessons, student profiles, and messages remain visible.
  • Lesson notes: You can draft lesson notes offline. They sync when you reconnect.

What requires internet:

  • Sending messages
  • Creating or editing lessons
  • Generating or paying invoices
  • Signing in for the first time

If none of the solutions above resolve your issue, contact support with:

  • Your device model and operating system version
  • The Clefora app version (found in Settings → About)
  • A description of the issue and when it started
  • A screenshot if applicable