Before changing a password, reinstalling anything, or calling anyone, settle one question: which of three separate systems failed. A refused login, a signed-in session that lists no trips, and a boarding pass that will not move into a phone's wallet are three different failures with three different fixes. All three get reported the same way, and treating them as one problem is why the same steps get repeated with no result.
The conclusion up front. A refused login is an identity problem, and American documents one recovery route for it: a password reset, which doubles as the only published way to unlock a locked account. A trip that will not appear is rarely a credentials problem — the reservation exists, but nothing ties it to the signed-in AAdvantage number. A boarding pass that will not save is a handoff to the phone's own wallet software, and by then the pass has already been issued.
Every figure and menu path below comes from American's own published pages — technical support, the website and app FAQs, the reservations and tickets FAQs, and the App Store listing — read in August 2026. Where American publishes no figure, that gap is stated rather than filled in. Check-in eligibility and timing are a separate subject, left out here.
What the American login accepts as identity
Establish first what is being typed into the username box, because American accepts two different things there. The technical support page states it plainly: "You can log in with your AAdvantage number or username and password." Those are alternatives, not a pair. An account has a numeric AAdvantage number assigned by the programme, and it may also have a username chosen by the member. Either one, plus the password, gets in.
A detail that trips people up sits in the FAQ entry for the Remember me checkbox: "Check 'Remember me' at login so you don't have to re-enter your AAdvantage number / username and last name every time you visit the site." The stored set includes the last name. Where the box was ticked long ago, that field is pre-filled and effectively invisible, so a failure that looks like a bad password can be a stale surname nobody has looked at in years. Logging out and re-entering all three values by hand is a cheaper first test than a reset.
If the AAdvantage number is the missing piece, the FAQ points at a retrieval link on the login screen: "If you don't remember your AAdvantage number, you can retrieve it at login where it says, 'Need AAdvantage number?'." The matching link for credentials is Need password? on the same screen. The AAdvantage FAQ adds two more routes: an online form that sends the number by email, and an existing AAdvantage credit card, which may already carry a number set up automatically.
To change either value once inside, the documented path is: log in, open profile / settings, select information and password, edit, save. That is the only place American describes for changing a username.
Resetting the password, and what "locked" means here
American's technical support page gives the reset requirements exactly: "You can create or reset your password online with your AAdvantage number, first and last name." Three values, no email link named as a prerequisite, no security-question step described. If the names on file do not match what is typed — a married name, a hyphenation, a middle name stored in the first-name field — the reset fails for a reason unrelated to the password.
The same page settles the lockout question in one sentence: "You can unlock your account by resetting your password." That is the whole documented procedure. There is no separate unlock form and no described waiting period. Anyone sitting out a supposed cooling-off interval is waiting on a rule American does not publish.
A reset can also fail for a reason that looks like a server fault. American's FAQ describes a compromised-password check: a security partner identifies passwords that may have been exposed on the web, and such passwords "can't be used to join AAdvantage or change your password." The fix is a password never used elsewhere, not another attempt at the same one.
What American does not publish matters as much. No minimum password length, character-class rule or reuse rule appears on the public help pages. No count of failed attempts and no lock duration is given. No session lifetime is published for the app, so a session that quietly expires cannot be called a defect on the available evidence. The one app-side control that does exist is a toggle: the FAQ answer for stopping the app remembering credentials is "Log out and when you log in again, make sure the option to 'Keep me logged in' is off."
Logging out is itself platform-specific, and the FAQ marks it as version-dependent: on recent builds, iPhone users scroll down on the home screen and choose log out, while Android users open the menu button at the top left. Two different locations for one action is worth knowing before concluding the option was removed.
A booking that does not appear under Trips
This failure is misdiagnosed as a login problem because it happens after a successful login. The app's rule for the home screen is narrow and specific: "If you're logged in and have a flight departing within 72 hours, your home screen will show your flight information. All additional flights will display on the home screen and under 'Later trips.'" A booking four weeks out that is not on the front screen is behaving as documented. Look under Later trips.
The second rule is about linkage. American's feature FAQ describes two modes: "Log in to the app and your upcoming trips will display on the home screen. If you 'Continue as guest,' choose 'Find Reservation/Check In' on the home screen and enter your name and confirmation code." Guest mode ties nothing to an account. Anyone who tapped through as a guest is looking at a screen that was never going to list a trip.
The third rule is the one that accounts for most genuine disappearances. A reservation booked without the AAdvantage number entered is not attached to the account, and no amount of signing in will surface it. American's AAdvantage FAQ gives the repair: find the trip online using the confirmation code from the trip confirmation email, then add the AAdvantage number in the passenger information section. The same FAQ sets the posting windows that follow: up to 10 days for travel on American, up to 30 days on partner airlines, and a missing-miles claim available online within 12 months of the flight.
The lookup value is precise. American's reservations FAQ defines it as "a unique 6-digit confirmation code made up of letters. It's also known as a record locator," with JCQNHD as the example. Six characters, letters only, printed on the confirmation email and the boarding pass. Anything longer, or with digits in it, is not the record locator — most likely it is the 13-digit ticket number.
Codeshare flights and tickets issued by another airline
The ticket number is the cleanest test of whether a booking belongs in American's systems at all. American's definition: "Your ticket number is a unique 13-digit number that identifies your reservation. The first 3 digits of your ticket number are the airline code, which is always '001' for American Airlines." A number starting with anything other than 001 was issued by a different carrier. American does not publish which non-001 tickets surface in its app, so the ticket number tells you who issued it, not what the app will do with it.
There is a related boundary the app FAQ does state outright. Among the reasons app check-in is not offered, American lists that the first flight is not operated by American Airlines. A ticket sold under an American flight number but flown by a partner falls on the wrong side of that line for the first segment. The FAQ does not name a substitute channel, so the practical plan is the operating airline's own site or an airport agent — not more attempts in the American app.
For flights bought through American on a partner, the reservations FAQ describes an additional delay that is easy to mistake for a broken booking: "Revenue tickets on partner airlines booked on aa.com or the American app are only available on request because they must be confirmed with the other airline. This can take 24 hours or more." The same answer notes that some airlines may require the reservation to be reconfirmed after booking. A partner segment sitting unconfirmed for a day is described behaviour, not a fault.
Bookings made through a travel agency or a third-party site are a further case. American states that changing one on aa.com carries no extra fee from American, but adds a consequence: once a change is made there, "any future changes will need to be made on aa.com or through American Reservations." The booking's home moves.
App version, the operating system floor, and what a reinstall costs
An app that will not open, crashes on launch, or refuses to update is worth checking against the published requirements before anything else. As listed on the App Store in August 2026, the American Airlines app is published by American Airlines, Inc., carries version 2026.25, weighs 332.2 MB, and requires iOS 18.0 or later on iPhone, iPadOS 18.0 or later on iPad, and watchOS 10.0 or later on Apple Watch. A device held back on iOS 17 will not receive current builds, and no amount of reinstalling changes that.
The Android side is different, and the difference is worth stating rather than guessing. The Google Play listing shows the developer as American Airlines, Inc. and a download count above 10 million, but it does not display a minimum Android version. There is no published Android floor to check a handset against, so any specific minimum quoted for this app did not come from the listing.
Reinstalling is the step reached for first, and it has a specific cost. American's FAQ states that a mobile boarding pass, once viewed, "will be cached in the app for 48 hours" and reopens from the boarding pass button without a connection. Deleting the app discards that cache, trading a working offline pass for a login screen. With a pass already saved and the flight close, reinstalling is the wrong move.
If the app is unusable and the browser is the fallback, American publishes requirements there too: the site is supported on current versions of Chrome, Firefox, Edge and Safari on Mac, and JavaScript, cookies and SSL must be turned on. A hardened browser profile with cookies blocked will fail a login that the same credentials pass elsewhere.
The boarding pass, the digital wallet, and what is not documented
Two American statements bound this area. First, on eligibility: the FAQ answer to why a mobile boarding pass was not issued is "You must be departing from and connecting through TSA approved cities." American directs travellers to its airport information pages to confirm a specific airport, and points to home printing or an airport kiosk where a mobile pass is not accepted. Second, on the wallet handoff: the mobile boarding pass page says to "Add your boarding pass to your digital wallet on your iPhone or Android device to get the latest flight updates."
That sentence is as far as American goes. It does not name Apple Wallet or Google Wallet, gives no operating system versions for the wallet step, and does not describe what happens when a save fails.
The two platform owners fill part of the gap. Apple's Wallet documentation describes the mechanism as an Add to Apple Wallet control inside an app, email or notification, and gives the diagnostic directly: "If you don't see an option to add your ticket or pass to the Wallet app, contact the merchant or company that issued it to make sure they support passes in the Wallet app." A missing button is an issuer-side condition, not a phone setting to hunt for. Google's Wallet documentation adds its own caveat — "Some passes or cards in Google Wallet are only available in certain countries, on certain devices, or select partners that support it" — so a save that works on one handset and not another is documented wallet behaviour, not proof of a broken airline app.
One further behaviour is documented and often mistaken for a crash: American's FAQ states the app hands the traveller to the website when travelling with an infant under 2, or when there is no seat assignment. That jump to a browser is the designed route, not a failure.
When to stop and escalate
Two published numbers cover the two problems, and they are not the same desk. For logging in, passwords, or using aa.com, American lists technical support at 800-222-2377 for the U.S. and Canada, staffed 24 hours in English and 24 hours in Spanish; callers elsewhere are directed to Reservations. For the account itself — a name that will not match, a number that cannot be recovered, miles that never posted — AAdvantage account service is listed at 800-882-8880, also 24 hours. The Play listing publishes aa.mobile@aa.com as an app contact address.
Two changes are documented as outside self-service: a name change and a date-of-birth change both require contacting American and sending supporting documents. A login that fails because the name on file is wrong is a support ticket, not a reset.
When This Doesn't Apply
This diagnosis assumes a consumer AAdvantage account and a ticket sold by American. It does not apply cleanly here.
- Partner-issued tickets. A ticket number not starting with
001was issued elsewhere, and American publishes no rule for how such records behave in its app. - Agency-managed travel. Changing an agency booking on aa.com moves future changes to aa.com or American Reservations. Where a travel policy forbids that, the app is not the right tool.
- Accounts with a name mismatch. The reset route requires the AAdvantage number plus first and last name. If the name on file is wrong, no online step recovers the account.
- Airports that do not accept mobile boarding passes. American conditions the mobile pass on departing from and connecting through TSA approved cities. Where that fails, the pass is not a troubleshooting target at all.
- Devices below the published floor. An iPhone or iPad that cannot run iOS or iPadOS 18.0 is outside the current app's stated compatibility; the browser is the remaining route.
- Check-in eligibility and timing. Who may check in, and when the window opens, are governed by a separate set of rules not addressed here.
A closing note on evidence. Several things commonly asserted about this app — a lockout attempt count, a lockout duration, a minimum password length, a minimum Android version, a session timeout — are not published by American anywhere in the material above. Treating an unpublished number as a fact is how a troubleshooting session ends up waiting for something that was never going to happen.
Comments
Post a Comment