[Bug] iOS exposes two inconsistent medication logging dead ends when no active medications exist

[lutzkind]

Summary

When an account has no active medications, the iOS app exposes two different medication-logging entry points that both lead to dead ends, use inconsistent terminology, and do not offer the only useful next action: adding a medication.

Affected client

• HealthLog iOS/TestFlight
• Observed with HealthLog-iOS 0.17.0
• Self-hosted server connected and otherwise healthy

Reproduction

Use an account with no active medications.

Path 1: Log a dose

1. Open the general Log flow.
2. Choose the medication/dose option.
3. The app opens a sheet titled Log a dose.

Actual result:

• The screen says No active medications to log against.
• The sheet is mostly empty.
• Both a back button and a Cancel button are shown.
• The primary Log button is disabled.
• There is no Add medication action.

Path 2: Log an intake

1. Open the medication intake flow from the medication-related surface.
2. The app opens a sheet titled Log an intake.

Actual result:

• The screen says No pending intake.
• It adds Nothing scheduled is due right now. Head back and check in later.
• Log manually appears disabled.
• There is no Add medication action.

Why this is inconsistent

The server model legitimately distinguishes:

• an active medication that can receive a manual intake; and
• a scheduled intake that is currently due.

However, when the account has no active medications at all, the second screen's message is misleading: nothing will become due by checking again later. Both screens become dead ends, while using dose and intake for nearly identical user intent.

Expected behavior

The empty state should depend on account state:

1. No active medications

   • Show one clear empty state: No active medications.
   • Offer Add medication as the primary action.
   • Use one close/cancel affordance, not both back and cancel.

2. Active medications exist, but none is due

   • Show No dose due right now.
   • Keep Log manually enabled so the user can select an active medication.

3. A scheduled intake is due

   • Show the due-intake action flow.

4. Manual logging opened directly

   • Show the active-medication selector immediately.

Terminology should be consistent across both paths, or the distinction between a scheduled intake and a manually logged dose should be made explicit.

Suggested implementation

• Resolve active-medication count before choosing the empty state.
• Route the no-active-medication state to a shared component with an Add medication deep link.
• Reserve No pending intake for accounts that actually have active scheduled medications but no currently due slot.
• Keep manual logging available whenever at least one active medication exists, regardless of whether a slot is due.
• Remove duplicate dismissal controls from the empty form.

Regression tests

• No active medications → Add medication is shown; no misleading check in later copy.
• Active as-needed medication, nothing scheduled → manual logging is available.
• Active scheduled medication, none due → manual logging remains available.
• Scheduled medication due → pending-intake flow is shown.
• Empty manual form uses a single dismissal affordance.

Evidence

Screenshots from the same account state show the two inconsistent empty flows:

• Log a dose → No active medications to log against.
• Log an intake → No pending intake / check in later, with disabled Log manually.

[MBombeck]

Thank you, @lutzkind. This one is entirely in the native client, so it needs to live in the iOS tracker rather than here — I will re-file it there and link it back, because you should not have to know which repository a defect belongs to in order to report it.

The substance is right and worth stating plainly: two entry points, two different vocabularies for the same act, both ending in a dead end, and neither offering the only thing that would help. An empty state that tells you what is missing without offering the way out is a wall with a label on it.

The terminology half is a real finding beyond the empty states. "Log a dose" and "Log an intake" are the same action to a person and different words in the product, which means the two paths were built at different times without anyone reconciling them. That is worth fixing even once the empty state offers to add a medication.

The native side of this project lags the server, and it is on TestFlight review cycles rather than my own, so I cannot promise a date the way I can for a server fix. What I can do is make sure it is filed where the person who works on it will see it, with your reproduction intact.

Leaving this open until it is re-filed, then I will close it here with a link.

[MBombeck]

Filed in the native tracker, @lutzkind, and I owe you a correction on how I put it last time.

I said I would link it back here. That tracker is private, so a link would just be a door you cannot open. Saying "linked" and handing you a 404 would be worse than saying nothing, so here is the substance instead.

Both halves of your report went in, and they went in as two things rather than one, because they are. The dead end is one: an empty state that names what is missing without offering the only action that helps is a wall with a label on it, and adding a medication belongs right there rather than in another menu. The vocabulary is the other: "dose" and "intake" are the same act, two entry points should not give it two names, and one of them has to win everywhere. The double exit, back and Cancel side by side in a sheet that offers nothing, went in with it.

Nothing is missing on the server side for this. An empty list of active medications is the correct answer to an account with none, so there is no contract change waiting on us.

I am leaving this open rather than closing it, because it is your report and you have not seen it fixed yet. When a TestFlight build lands with it, I will say so here and you can decide.

Thank you for writing it up as carefully as you did. Two paths described separately is what made it obvious they had drifted apart.