Troubleshooting: Common Issues
Troubleshooting: Common Issues
For data-specific problems (missing scores, HealthKit gaps, wrong-day entries), see Troubleshooting: Missing Data. This article covers everything else.
”The app is stuck on a loading screen”
Fix: Force-quit the app and reopen it. If the issue persists, check your internet connection. Rubric requires a network connection for most features, though photos and food logs will queue locally and sync when you reconnect.
”I am stuck in an onboarding loop”
Cause: This can occur if the app loses network connectivity during the onboarding save.
Fix: Ensure you have a stable network connection, force-quit the app, and reopen. The app will detect your completed onboarding and skip to the main screen. If the problem continues, try toggling airplane mode on and off, then reopening the app.
”Notifications are not arriving”
Cause: iOS notification permissions may not be granted, or notification delivery is not enabled in the app.
Fix: First, check iOS Settings, then Notifications, then Rubric, and ensure notifications are allowed. Then, in Rubric, go to your Profile and open Notification Settings. Both the Daily Audit and Weekly Report toggles are off by default. Enable the ones you want and set your preferred delivery time (default is 8:00 AM).
If you declined notification permissions during onboarding, in-app toggles will have no effect. You must enable permissions in iOS Settings first.
”My score seems wrong”
Cause: The score is deterministic. The same inputs always produce the same score. If the number seems low, the issue is usually missing data (which can reduce your Adherence Multiplier) or a protocol requirement you missed.
Fix: Long-press the score card on your dashboard to see the full breakdown. Look for missing data indicators or protocol adherence issues. See The Daily Rubric Score and Adherence Multiplier Explained for how the calculation works.
”An entry will not save or keeps failing”
Cause: Network connectivity issue, or the entry may contain content that triggers a validation error.
Fix: Check your network connection. If the issue persists, try logging the entry with simpler text (e.g., “chicken and rice” instead of a detailed paragraph). If you are offline, the entry will queue locally and sync automatically when connectivity returns.
”I cannot edit an old entry”
Cause: Entries older than 3 days are locked and cannot be edited or deleted. This is by design.
Fix: The 3-day rolling window is a core part of how Rubric maintains data integrity. After 72 hours, your record is finalized. See Daily Check-Ins and the 3-Day Window for the reasoning behind this limit.
”The Coach is not responding”
Cause: The Coach relies on external AI services which may experience temporary outages.
Fix: Wait a moment and try again. If the Coach is unresponsive, an error message will appear with a Retry button. Tap it to resend your message. Rubric has multiple fallback providers, so outages are typically brief. If the error persists for more than a few minutes, close and reopen the conversation.
”The app looks different on my iPad / desktop browser”
Cause: Rubric uses a responsive layout. On wider screens (tablets, desktops), the navigation moves from bottom tabs to a top bar, and some screens display a two-pane layout.
Fix: This is expected behavior. The content and features are identical across screen sizes.
Related Articles