Bugs Found in Artful Agenda for iOS

Artful Agenda

4.7

Artful Agenda is an application that helps you organize your schedule and tasks in a meaningful way. With an aesthetically appealing and user-friendly interface, the app enhances conventional calendar functionality by incorporating stunning designs and customizable layouts.

Artful Agenda offers a plethora of features, including cross-platform syncing, lists, and customizable covers. Its functionality extends beyond basic calendaring, allowing users the flexibility to integrate their device’s calendar, write digital notes, set reminders, and even personalize their productivity space.

After a thorough exploration of the app through a bug crawl, the QAwerk team discovered a few bugs that could impact the app’s performance and compromise the user experience. We invite you to see our findings and learn more about how these challenges could be addressed.

7K+downloads
15K ratings

SQL Integrity Constraint Violation error is displayed after saving empty ‘First Name’ field

Severity:

Critical

Precondition:
  1. The app is installed.
  2. The user is on the ‘Account Settings’ tab.
Steps to Reproduce:
  1. Clear the ‘First Name’ field.
  2. Tap the ‘Save’ button.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

The ‘SQL Integrity Constraint Violation’ error is displayed.

Expected Result:

The user should see a validation message indicating that the ‘First Name’ field cannot be left empty.

Ability to create event for past date

Severity:

Major

Precondition:
  1. The app is installed.
  2. The user is on the main page.
Steps to Reproduce:
  1. Select a date in the past.
  2. Fill in all required fields.
  3. Save the event.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

The event is successfully created for a past date.
Additionally, the user can also set an alarm for this past event.

Expected Result:

The app should either block the creation of events in the past or clearly inform the user that creating past events is available only for historical/logging purposes.
If past events are intentionally supported, reminders or alarms for such events should be disallowed, as they cannot be activated properly.

Inability to change alarm time

Severity:

Major

Precondition:
  1. The app is installed.
  2. The user is on the ‘Event Details’ pop-up.
Steps to Reproduce:
  1. Enter the event details.
  2. Add an alarm.
  3. Try to change the alarm time.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

The app does not allow editing the alarm time.

Expected Result:

The user should be able to modify the alarm time.

Alarm unit changes to generic ‘UNITS’ after switching event to ‘All Day’

Severity:

Major

Precondition:
  1. The app is installed.
  2. The app is open.
  3. The user is on the ‘Calendar’ page.
Steps to Reproduce:
  1. Create a new event for today with a duration of 1 hour.
  2. Add an alarm with a value of ‘10 minutes’.
  3. Save the event.
  4. Open the created event in the ‘Edit’ mode.
  5. Enable the ‘All Day’ option.
  6. Observe the ‘Alarm’ section.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

The alarm unit label changes from ‘minutes’ to generic ‘UNITS’.

Expected Result:

When the user switches the event type to ‘All Day’, the alarm configuration should remain clear and consistent. The system should not display generic or internal terminology, such as ‘UNITS’, to the user.

Alarm unit changes to generic ‘UNITS’ after switching event to ‘All Day’

Event time is displayed differently in ‘Calendar’ view and ‘Event Details’ after timezone change

Severity:

Major

Precondition:
  1. The app is installed.
  2. The user has switched to another time zone in the device settings.
Steps to Reproduce:
  1. Create a new event in another timezone.
  2. Switch the timezone back to the current location.
  3. Check the created event in the ‘Calendar’.
  4. Open event details.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

There is an inconsistency in the display of event time information:

  • ‘Calendar’ view displays the event according to the current timezone.
  • ‘Event Details’ view displays the event in the timezone/time at which the event was created.
Expected Result:

The app should ensure the event time is consistently displayed across the ‘Calendar’ view and the ‘Event Details’. Alternatively, if an event is created in a different timezone, the app should explicitly indicate this and show both the original and local times.
NOTE:
The current behavior might confuse users, as there is ambiguity regarding which event time is accurate.

Event time is displayed inconsistently and partially truncated in ‘Day’ view

Severity:

Major

Precondition:
  1. The app is installed.
  2. Several events were created on the calendar: e.g., 9:00 AM and 12:10 PM.
Steps to Reproduce:

Observe the created events in the ‘Calendar’.

Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

The event time formatting is inconsistent:

  • Some events present incomplete time values, such as ‘9’.
  • Others show partially truncated values like ‘12:10p’.
Expected Result:

Event times should consistently and entirely be displayed in the calendar view (e.g., ‘9:00 AM’, ‘9 AM’, or ‘12:10 PM’), conforming to the defined design format. Time representation should not be truncated or lose its AM/PM suffixes, and it should remain consistent across all events.
NOTE:
The current behavior detracts from readability and could potentially confuse users regarding accurate event times.

Event time is displayed inconsistently and partially truncated in ‘Day’ view

Endless spinner is displayed when creating yearly recurring event on February 29

Severity:

Major

Precondition:
  1. The app is installed.
  2. The user is in the ‘Calendar’ view.
Steps to Reproduce:
  1. Create a new event on February 29 2028.
  2. Enable recurrence.
  3. Set recurrence to ‘Every Year’.
  4. Set ‘March 2029’ in the ‘Until’ field.
  5. Save the event.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

An endless spinner is displayed, and the event is not saved successfully.

Expected Result:

The application should either:

  • Successfully create the yearly recurring event with defined procedures for non-leap years.
  • Display a clear validation message stating that yearly recurrence on February 29 requires special handling.

The application should not get stuck in a loading state.
NOTE:
This issue might be related to the recurrence calculation for non-leap years, during which February 29 does not exist.

Grey screen with endless spinner is displayed after returning from YouTube tutorial, while audio continues playing

Severity:

Major

Precondition:

The app is installed.

Steps to Reproduce:
  1. Navigate to the ‘Settings’ section.
  2. Select the ‘Tutorials’ option.
  3. Verify that the user is navigated to YouTube.
  4. Return to the app.
  5. Verify that the YouTube window is automatically minimized.
  6. Observe the behavior.
Environment:

iPhone 14 Pro, iOS version 26.4.2

Actual Result:

A grey screen with a loading spinner is displayed, while the tutorial audio continues to play in the background.

Expected Result:

After returning to the app, the tutorial/video screen should be restored properly. The video playback state and the user interface should remain synchronized, with no endless loading state or grey overlay.

The application demonstrates a strong planning concept and offers a wide range of calendar and event management features. However, during testing, I identified several functional and UX consistency issues. They were primarily related to reminders, recurring events, time zone handling, calendar/event synchronization, and screen state restoration. I would recommend comprehensive UI and usability testing to help resolve these issues.
Tetiana, QA engineer

Tetiana, QA engineer

Need a reliable QA partner?

Hire us