Bugs Found in Routewise: AI Trip Planner for iOS
Routewise: AI Trip Planner is a dynamic online platform that organizes and streamlines your travel plans. It provides an integrated solution for travelers seeking a personalized, well-coordinated trip experience. The app offers features such as managing bookings, creating detailed itineraries, and providing real-time travel advice.
We tested Routewise during our recent bug crawl. Overall, it provides a good and intuitive travel planning experience. The app has a clean UI, and the main trip creation and itinerary management flows are easy to understand. However, we did discover a few bugs that may confuse the user. Check out our detailed report and recommendations below.
Deleted day’s places are restored after optimizing itinerary
Severity:
Major
Precondition:
- An itinerary contains at least 2 days.
- A place is added to the day that will be deleted.
Steps to Reproduce:
- Open an itinerary containing multiple days.
- Add/verify a place on Day 2.
- Delete Day 2 using the ‘Delete entire day’ option.
- Verify that the itinerary now contains only Day 1 and the deleted day’s place is no longer displayed.
- Tap the ‘Optimize Itinerary’ button.
- Confirm the optimization.
- Wait for optimization to complete, then review the itinerary.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
The place from the deleted Day 2 is restored and added to Day 1 after itinerary optimization.
Expected Result:
Places belonging to a deleted day should be removed from the itinerary and should not be restored or included during subsequent optimization.
‘Edit day name’ and ‘Rearrange days’ options are unresponsive for existing itineraries on ‘Discover’ tab
Severity:
Major
Precondition:
The user has an itinerary with multiple days.
Steps to Reproduce:
- Open an existing itinerary on the ‘Discover’ tab.
- Tap the day name/header to open the day options.
- Tap the ‘Edit day name’ option.
- Observe the response.
- Open the day options again.
- Tap the ‘Rearrange days’ option.
- Observe the response.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
Nothing happens after selecting either the ‘Edit day name’ or ‘Rearrange days’ options. No corresponding screen, dialog, or editing functionality is opened.
Expected Result:
Tapping the ‘Edit day name’ option should open the functionality for changing the selected day’s name.
Similarly, tapping the ‘Rearrange days’ option should open the functionality for changing the order of itinerary days.
Unable to scroll and view all affected itinerary data on ‘Update Trip Dates’ modal
Severity:
Major
Precondition:
The trip contains multiple days/places that will be removed after changing the trip dates (at least 10-20 days).
Steps to Reproduce:
- Open an existing trip.
- Navigate to the ‘Edit Trip Dates’ section.
- Change the trip dates to reduce the trip duration to, for example, 5 days.
- Tap the ‘Save’ button.
- Observe the ‘Update Trip Dates’ modal.
- Scroll down to review all days and places that will be removed.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
The user cannot scroll far enough to view all days and places that will be removed. Some itinerary data remains hidden at the bottom of the ‘Update Trip Dates’ modal.
Expected Result:
The user should be able to scroll through and view all days and places that will be removed before confirming the trip date update.
No validation message is displayed for required ‘Last Name’ field on ‘Profile Setup’ screen
Severity:
Minor
Precondition:
The user is on the ‘Set up your profile’ page.
Steps to Reproduce:
- Navigate to the ‘Set up your profile’ screen.
- Leave the ‘First Name’, ‘Last Name’, and ‘Username’ fields empty.
- Tap the ‘Continue’ button.
- Observe the validation messages.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
Validation messages are displayed for the empty ‘First Name’ and ‘Username’ fields, while no validation message is displayed for the empty required ‘Last Name’ field.
No validation messages are displayed for spaces-only input as well.
Expected Result:
A required-field validation message should also be displayed for the ‘Last Name’ field to maintain consistency with the other required fields.
During testing, I identified several areas requiring additional attention, mainly around itinerary editing, data synchronization/state consistency, and UI behavior. I recommend focusing additional testing on editing existing trips, synchronization after itinerary changes, user input validation, scrolling/content visibility, and preserving the correct app state after updates or app relaunch.
