Bugs Found in Layla – AI Trip Planner for iOS
Layla is an AI-powered travel assistant that helps users create itineraries, book trips, and find interesting places to visit at their destinations.
When we studied it during our bug crawl, the QAwerk team found the application helpful and user-friendly for trip planning. The AI-guided flow is convenient, and the generated trips include traveler-friendly information. Suggested responses further support the quick, straightforward planning process.
However, we found several bugs in AI flows and when accessing some screens. Take a look at our detailed breakdown of these issues below.
Main navigation and profile are unavailable immediately after sign-up until app restart
Severity:
Critical
Precondition:
- The user has successfully signed up.
- The user has completed onboarding.
- A trip has been created during onboarding.
- The user is currently on the ‘Trip’ page created during onboarding.
Steps to Reproduce:
- Tap the ‘Home’ navigation button.
- Check the available navigation/menu options.
- Try to access the ‘Profile’ section.
- Close the app.
- Reopen the app.
- Check the navigation options again.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
After signing up and completing onboarding, the ‘Home’ navigation button fails to work. Other main navigation/menu options are not available, and the user cannot access the ‘Profile’ section. The user can only interact with the trip created during the onboarding process. After reopening the app, the missing navigation options appear and function as expected.
Expected Result:
Once sign-up and onboarding are successfully completed, the user should have immediate access to the full application navigation from the onboarding-created ‘Trip’ page, including ‘Home’, ‘Profile’, and other sections, without restarting the app.
Password validation does not indicate uppercase letter requirement during account creation
Severity:
Major
Precondition:
The user is on the ‘Create Account page.
Steps to Reproduce:
- Fill in the required account creation fields.
- Enter a password that contains letters, numbers, and special symbols but doesn’t contain uppercase letters.
- Attempt to create the account.
- Observe the password validation.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
The password is rejected when it does not contain an uppercase letter. The system does not display password requirements to the user. The user is not informed beforehand that an uppercase letter, or any other specific password criteria, is required.
Expected Result:
All enforced password requirements should be clearly displayed during account creation so the user knows what constitutes a valid password. If an uppercase letter is mandatory, this requirement should be explicitly communicated before or while the user enters the password.
Extended loading time on chat screen after submitting trip request with image attachment
Severity:
Major
Precondition:
- The user is logged in.
- The user is on the trip request creation screen.
Steps to Reproduce:
- Attach an image to the trip request.
- Enter a request, e.g., ‘I want to visit the place from the photo.’
- Tap the ‘Start’ button.
- Observe the ‘Chat’ screen while the request is being processed.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
An endless loading spinner is displayed after submitting the trip request. The loading state does not complete automatically, giving the impression that trip creation is still in progress. However, the trip has actually been successfully created in the background. If the user manually navigates to the ‘Trips’ list, the newly created trip is available. Opening it displays the generated trip details correctly.
Expected Result:
After trip creation completes successfully, the loading state should stop automatically, and the user should see the generated trip details without additional navigation.
AI repeatedly instructs user to tap non-existent ‘New Chat’ button when starting another trip
Severity:
Major
Precondition:
- The user has an existing trip.
- The user is in the chat associated with that trip.
Steps to Reproduce:
- Ask the AI to change the trip destination to another country, e.g., Albania.
- Observe that the AI recommends starting a new chat because the destination is significantly different.
- Select/enter ‘Start new chat’.
- Continue selecting/entering ‘Start new chat’ when prompted.
- Observe the AI responses and available UI controls.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
The AI tells the user to tap the ‘New Chat’/’Start New Chat’ button. No such button is available on the current screen. When the user explicitly enters/selects ‘Start new chat’, a new chat is not created. The AI repeatedly gives the same instruction to use a button the user cannot access, creating a conversational loop. The user cannot proceed with the new-trip flow through the instructions provided by the AI.
Expected Result:
The AI should only instruct the user to use UI actions that are actually available in the current context. If starting a separate chat is required, the app should either:
- provide an actionable ‘New Chat’ control
- automatically initiate the new-chat flow when the user selects ‘Start new chat.’
The AI should not repeatedly instruct the user to interact with a UI element that does not exist.
Chat automatically scrolls up after selecting suggested reply
Severity:
Major
Precondition:
- The user has an active trip-planning conversation.
- The conversation contains enough messages to be scrollable.
- Suggested reply options are displayed at the bottom of the conversation.
Steps to Reproduce:
- Open the trip-planning chat.
- Scroll to the bottom of the conversation.
- Tap one of the suggested reply options.
- Observe the chat position after the suggestion is selected.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
After selecting a suggested reply, the conversation automatically scrolls upward to an earlier part of the chat. The user is moved away from the latest conversation context and has to manually scroll back down.
Expected Result:
After selecting a suggested reply, the chat should remain at the bottom/latest conversation position so the user can see the selected message and the AI’s subsequent response. The application should not unexpectedly change the user’s scroll position to an earlier part of the conversation.
‘No flights found’ message is shown for non-flight transportation filters
Severity:
Minor
Precondition:
- The user has an existing trip with transportation details.
- The trip does not contain any Train or Ferry transportation options.
Steps to Reproduce:
- Open the trip.
- Navigate to the ‘Transportation’ section.
- Select the Train filter.
- Observe the empty-state message.
- Select the Ferry filter.
- Observe the empty-state message.
Environment:
iPhone 14 Pro, iOS version 26.6
Actual Result:
When Train or Ferry is selected, and no matching transportation records exist, the screen displays: ‘No flights found’. The message refers specifically to flights regardless of the currently selected transportation type.
Expected Result:
The empty-state message should correspond to the selected filter.
During testing, I discovered several issues that could negatively affect user experience. The main problems involve loading and state synchronization. For instance, the app gets stuck loading even after a trip has been created. I recommend implementing testing best practices, particularly when verifying AI flows.
