Originally Posted by
RTWSTARALLIANCE
We all know UA is going backwards in technology. Yesterday at ORD look at boarding pass on app. Shows F6. Walk to F6 and no flight for MKE. Check flight status on app and it shows F2. Walk to F2 where flight is actually departing from. With hope all these bugs will start to get fixed.
By the way. The app boarding pass never corrected even after refreshing at F2 gate. I boarded with my app boarding pass showing F6.
What seems to happen is that the BP gets "frozen in time" once its issued until something specific to the boarding pass gets changed (e.g. seat assignment/cabin of service, etc.) and/or the BP gets reissued.
Since gate changes aren't part of the PNR unless you "checkin" again to regenerate the BP the gate on the BP portion of the app will never update -- much like the gate on a paper BP.
The only exception I've noticed (and this seems to be sporadic) is if its "Not Yet Assigned" the BP may pick up the assigned gate once one is assigned. Maybe someone put in logic specifically looking for NYA to force the BP to refresh as a workaround?
Not that that's the way it should be but at least it gives some insight on the way things
seem to work...