Go Back  FlyerTalk Forums > Miles&Points > Airlines and Mileage Programs > Air Canada | Aeroplan
Reload this Page >

The Newly Redesigned Air Canada Mobile App (Fall 2019)

Community
Wiki Posts
Search
Old Oct 28, 2019, 2:48 pm
FlyerTalk Forums Expert How-Tos and Guides
Last edit by: codfather

Print Wikipost

The Newly Redesigned Air Canada Mobile App (Fall 2019)

Thread Tools
 
Search this Thread
 
Old Jun 25, 2020, 10:49 am
  #541  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
Originally Posted by Adam Smith
This has been fixed, now showing up as "Airbus A220-300"
It's almost like they read this thread ​​​​​​​

They also fixed my 1A SFO to nowhere issue. The booking doesn't show up in any list, nor can I pull it up by booking reference. I wonder if it still exists...
G23 and Adam Smith like this.
canadiancow is online now  
Old Jun 29, 2020, 2:09 pm
  #542  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342


Clearly I'm in J and I'm SE MM.

The app, however, shows no indication of million miler, and "Class of service" is blank after clicking "More".


canadiancow is online now  
Old Jun 30, 2020, 2:51 pm
  #543  
 
Join Date: Jun 2010
Programs: AC SE100K , 1MM, Hilton Diamond, KLM
Posts: 579
Scott I notice this when flying yesterday same thing boarding pass ok App did not show anything in remarks
traacs is offline  
Old Jul 30, 2020, 12:51 am
  #544  
Moderator, Air Canada; FlyerTalk Evangelist
 
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,775
Does the app no longer provide notifications when check-in is open? I think I'm over half a dozen bookings in the last few weeks where there has been no notification when check-in opened, or any time.

Also, AC app team, let us snooze this $&@#&$/+&@ notification. I'm getting so tired of seeing it every single time I open this bloody app.



Surely there's a smarter way. If dismissing it until something actually changes is too hard, at least make it snooze for a week or even a couple of days.
canadiancow and YYC3722 like this.

Last edited by Adam Smith; Jul 30, 2020 at 9:35 am Reason: Corrected typo
Adam Smith is offline  
Old Jul 30, 2020, 3:09 pm
  #545  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
Code:
07-30 17:08:32.969 22019 22019 D AndroidRuntime: Shutting down VM
07-30 17:08:32.970 22019 22019 E AndroidRuntime: FATAL EXCEPTION: main
07-30 17:08:32.970 22019 22019 E AndroidRuntime: Process: com.aircanada, PID: 22019
07-30 17:08:32.970 22019 22019 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.aircanada/com.aircanada.mobile.activity.MainActivity}: kotlin.TypeCastException: null cannot be cast to non-null type com.aircanada.mobile.service.model.flightStatus.FlightStatusSegment
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3449)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3601)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:106)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:223)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:7656)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
07-30 17:08:32.970 22019 22019 E AndroidRuntime: Caused by: kotlin.TypeCastException: null cannot be cast to non-null type com.aircanada.mobile.service.model.flightStatus.FlightStatusSegment
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.aircanada.mobile.ui.flightstatus.details.l0.onCreate(SourceFile:24)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.performCreate(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.r.c(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:120)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.j(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.i(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:174)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.c(SourceFile:33)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.e(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.restoreChildFragmentState(SourceFile:3)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.onCreate(SourceFile:2)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.aircanada.mobile.ui.flightstatus.details.FlightStatusDetailsFragment.onCreate(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.performCreate(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.r.c(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:120)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.j(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.i(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:174)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.c(SourceFile:33)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.e(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.restoreChildFragmentState(SourceFile:3)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.onCreate(SourceFile:2)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.navigation.fragment.NavHostFragment.onCreate(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.Fragment.performCreate(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.r.c(SourceFile:5)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:120)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.j(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.i(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.a(SourceFile:174)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.c(SourceFile:33)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.l.e(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.g.b(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.fragment.app.d.onCreate(SourceFile:18)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at androidx.appcompat.app.e.onCreate(SourceFile:4)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.aircanada.mobile.activity.y0.onCreate(SourceFile:1)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at com.aircanada.mobile.activity.MainActivity.onCreate(SourceFile:2)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.Activity.performCreate(Activity.java:7995)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.Activity.performCreate(Activity.java:7979)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1309)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3422)
07-30 17:08:32.970 22019 22019 E AndroidRuntime:     ... 11 more
canadiancow is online now  
Old Jul 30, 2020, 3:26 pm
  #546  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
And ignoring that crash, I'm noticing some naughty behavior.

The AC app has been in the background for about a minute. It should not be doing anything. And yet...


Code:
   PID USER         PR  NI VIRT  RES  SHR S[%CPU] %MEM     TIME+ ARGS
 22952 u0_a323      20   0  15G 221M 117M R  11.0  4.0   2:09.42 com.aircanada


Code:
% adb logcat --pid=22952
07-30 17:24:51.300 22952 23829 V AppSyncOfflineMutationInterceptor: Thread:[42823]: processing Mutations
07-30 17:24:51.300 22952 23829 V QueueUpdateHandler: Thread:[42823]: Got message to take action on the mutation queue.
07-30 17:24:51.300 22952 23829 V QueueUpdateHandler: Thread:[42823]: Got message to process next mutation if one exists.
07-30 17:24:51.301 22952 23829 V AppSyncOfflineMutationManager: Thread:[42823]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:51.301 22952 23829 V AppSyncOfflineMutationManager: Thread:[42823]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:53.982 22952 23134 V AppSyncOfflineMutationInterceptor: Thread:[42279]: processing Mutations
07-30 17:24:53.983 22952 23134 V QueueUpdateHandler: Thread:[42279]: Got message to take action on the mutation queue.
07-30 17:24:53.983 22952 23134 V QueueUpdateHandler: Thread:[42279]: Got message to process next mutation if one exists.
07-30 17:24:53.984 22952 23134 V AppSyncOfflineMutationManager: Thread:[42279]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:53.985 22952 23134 V AppSyncOfflineMutationManager: Thread:[42279]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:54.534 22952 23212 V AppSyncOfflineMutationInterceptor: Thread:[42360]: processing Mutations
07-30 17:24:54.534 22952 23212 V QueueUpdateHandler: Thread:[42360]: Got message to take action on the mutation queue.
07-30 17:24:54.534 22952 23212 V QueueUpdateHandler: Thread:[42360]: Got message to process next mutation if one exists.
07-30 17:24:54.537 22952 23212 V AppSyncOfflineMutationManager: Thread:[42360]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:54.537 22952 23212 V AppSyncOfflineMutationManager: Thread:[42360]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:54.627 22952 23209 V AppSyncOfflineMutationInterceptor: Thread:[42358]: processing Mutations
07-30 17:24:54.627 22952 23209 V QueueUpdateHandler: Thread:[42358]: Got message to take action on the mutation queue.
07-30 17:24:54.627 22952 23209 V QueueUpdateHandler: Thread:[42358]: Got message to process next mutation if one exists.
07-30 17:24:54.630 22952 23209 V AppSyncOfflineMutationManager: Thread:[42358]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:54.630 22952 23209 V AppSyncOfflineMutationManager: Thread:[42358]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:54.778 22952 23210 V AppSyncOfflineMutationInterceptor: Thread:[42357]: processing Mutations
07-30 17:24:54.778 22952 23210 V QueueUpdateHandler: Thread:[42357]: Got message to take action on the mutation queue.
07-30 17:24:54.778 22952 23210 V QueueUpdateHandler: Thread:[42357]: Got message to process next mutation if one exists.
07-30 17:24:54.780 22952 23210 V AppSyncOfflineMutationManager: Thread:[42357]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:54.780 22952 23210 V AppSyncOfflineMutationManager: Thread:[42357]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:54.976 22952 23238 V AppSyncOfflineMutationInterceptor: Thread:[42381]: processing Mutations
07-30 17:24:54.976 22952 23238 V QueueUpdateHandler: Thread:[42381]: Got message to take action on the mutation queue.
07-30 17:24:54.976 22952 23238 V QueueUpdateHandler: Thread:[42381]: Got message to process next mutation if one exists.
07-30 17:24:54.978 22952 23238 V AppSyncOfflineMutationManager: Thread:[42381]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:54.978 22952 23238 V AppSyncOfflineMutationManager: Thread:[42381]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.027 22952 23272 V AppSyncOfflineMutationInterceptor: Thread:[42415]: processing Mutations
07-30 17:24:57.027 22952 23272 V QueueUpdateHandler: Thread:[42415]: Got message to take action on the mutation queue.
07-30 17:24:57.027 22952 23272 V QueueUpdateHandler: Thread:[42415]: Got message to process next mutation if one exists.
07-30 17:24:57.030 22952 23272 V AppSyncOfflineMutationManager: Thread:[42415]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.030 22952 23272 V AppSyncOfflineMutationManager: Thread:[42415]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.033 22952 23276 V AppSyncOfflineMutationInterceptor: Thread:[42419]: processing Mutations
07-30 17:24:57.033 22952 23276 V QueueUpdateHandler: Thread:[42419]: Got message to take action on the mutation queue.
07-30 17:24:57.033 22952 23276 V QueueUpdateHandler: Thread:[42419]: Got message to process next mutation if one exists.
07-30 17:24:57.033 22952 23281 V AppSyncOfflineMutationInterceptor: Thread:[42424]: processing Mutations
07-30 17:24:57.033 22952 23281 V QueueUpdateHandler: Thread:[42424]: Got message to take action on the mutation queue.
07-30 17:24:57.033 22952 23281 V QueueUpdateHandler: Thread:[42424]: Got message to process next mutation if one exists.
07-30 17:24:57.035 22952 23281 V AppSyncOfflineMutationManager: Thread:[42424]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.035 22952 23281 V AppSyncOfflineMutationManager: Thread:[42424]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.035 22952 23276 V AppSyncOfflineMutationManager: Thread:[42419]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.035 22952 23276 V AppSyncOfflineMutationManager: Thread:[42419]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.042 22952 23280 V AppSyncOfflineMutationInterceptor: Thread:[42423]: processing Mutations
07-30 17:24:57.042 22952 23280 V QueueUpdateHandler: Thread:[42423]: Got message to take action on the mutation queue.
07-30 17:24:57.042 22952 23280 V QueueUpdateHandler: Thread:[42423]: Got message to process next mutation if one exists.
07-30 17:24:57.042 22952 23285 V AppSyncOfflineMutationInterceptor: Thread:[42426]: processing Mutations
07-30 17:24:57.042 22952 23285 V QueueUpdateHandler: Thread:[42426]: Got message to take action on the mutation queue.
07-30 17:24:57.042 22952 23285 V QueueUpdateHandler: Thread:[42426]: Got message to process next mutation if one exists.
07-30 17:24:57.043 22952 23285 V AppSyncOfflineMutationManager: Thread:[42426]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.043 22952 23285 V AppSyncOfflineMutationManager: Thread:[42426]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.043 22952 23280 V AppSyncOfflineMutationManager: Thread:[42423]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.043 22952 23280 V AppSyncOfflineMutationManager: Thread:[42423]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.050 22952 23270 V AppSyncOfflineMutationInterceptor: Thread:[42413]: processing Mutations
07-30 17:24:57.050 22952 23270 V QueueUpdateHandler: Thread:[42413]: Got message to take action on the mutation queue.
07-30 17:24:57.050 22952 23270 V QueueUpdateHandler: Thread:[42413]: Got message to process next mutation if one exists.
07-30 17:24:57.050 22952 23273 V AppSyncOfflineMutationInterceptor: Thread:[42416]: processing Mutations
07-30 17:24:57.050 22952 23273 V QueueUpdateHandler: Thread:[42416]: Got message to take action on the mutation queue.
07-30 17:24:57.050 22952 23273 V QueueUpdateHandler: Thread:[42416]: Got message to process next mutation if one exists.
07-30 17:24:57.051 22952 23273 V AppSyncOfflineMutationManager: Thread:[42416]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.051 22952 23273 V AppSyncOfflineMutationManager: Thread:[42416]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.052 22952 23270 V AppSyncOfflineMutationManager: Thread:[42413]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.052 22952 23270 V AppSyncOfflineMutationManager: Thread:[42413]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.066 22952 23282 V AppSyncOfflineMutationInterceptor: Thread:[42425]: processing Mutations
07-30 17:24:57.066 22952 23282 V QueueUpdateHandler: Thread:[42425]: Got message to take action on the mutation queue.
07-30 17:24:57.066 22952 23282 V QueueUpdateHandler: Thread:[42425]: Got message to process next mutation if one exists.
07-30 17:24:57.067 22952 23282 V AppSyncOfflineMutationManager: Thread:[42425]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.067 22952 23282 V AppSyncOfflineMutationManager: Thread:[42425]: In Memory mutations queue was EMPTY!. Nothing to process, exiting
07-30 17:24:57.318 22952 23359 V AppSyncOfflineMutationInterceptor: Thread:[42496]: processing Mutations
07-30 17:24:57.318 22952 23359 V QueueUpdateHandler: Thread:[42496]: Got message to take action on the mutation queue.
07-30 17:24:57.318 22952 23359 V QueueUpdateHandler: Thread:[42496]: Got message to process next mutation if one exists.
07-30 17:24:57.320 22952 23359 V AppSyncOfflineMutationManager: Thread:[42496]:Persistent mutations queue is EMPTY!. Will check inMemory Queue next
07-30 17:24:57.320 22952 23359 V AppSyncOfflineMutationManager: Thread:[42496]: In Memory mutations queue was EMPTY!. Nothing to process, exiting

I've only included a few seconds of log entries from well after I ran the logcat command, so these weren't just old messages in the buffer. The AC app is doing stuff in the background, hogging CPU, memory, battery (maybe - my phone's plugged in for the debugging, so it might behave differently while charging), etc.
canadiancow is online now  
Old Aug 31, 2020, 1:54 pm
  #547  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
5.7.0 has a new home tab.

Lots of Aeroplan adverting at the bottom.

I'm curious to see how it behaves when I have an actual flight coming up.

Originally Posted by Adam Smith
Also, AC app team, let us snooze this $&@#&$/+&@ notification. I'm getting so tired of seeing it every single time I open this bloody app.

...

Surely there's a smarter way. If dismissing it until something actually changes is too hard, at least make it snooze for a week or even a couple of days.
It's now just a persistent banner. Popup is gone (unless you click the banner).
Aselwyn likes this.
canadiancow is online now  
Old Aug 31, 2020, 3:14 pm
  #548  
 
Join Date: Apr 2018
Location: Ontario Canada
Programs: Air Canada 50K - Hilton Diamond - Marriott Platinum
Posts: 282
Originally Posted by canadiancow
5.7.0 has a new home tab.

Lots of Aeroplan adverting at the bottom.

I'm curious to see how it behaves when I have an actual flight coming up.



It's now just a persistent banner. Popup is gone (unless you click the banner).
well here is mine. i have 2 trips setup in the app and click the trips tab on the bottom for the others
G23 and TechnoTourist like this.
Aselwyn is offline  
Old Aug 31, 2020, 4:25 pm
  #549  
Moderator, Air Canada; FlyerTalk Evangelist
 
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,775
I still haven't been offered the option to upgrade to 5.7, but one thing you FOTSGs might not have noticed is the app now includes check-in reminders again, even on the previous version.
G23 and canadiancow like this.
Adam Smith is offline  
Old Sep 5, 2020, 1:45 pm
  #550  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
I really wish I could see more details about my bookings.

I have a booking in a few weeks and I have no idea if it's a Comfort fare I bought as a backup in case Europe fell through, or if it's an Aeroplan placeholder under the 50% promotion.

If it's the former, I definitely want to cancel it. If it's the latter, I think I want to move it.

But I can't tell from the app.

Edit: I reopened the app, I was on the home screen, but the Trips tab was selected.

Last edited by canadiancow; Sep 5, 2020 at 1:58 pm
canadiancow is online now  
Old Sep 27, 2020, 5:34 pm
  #551  
 
Join Date: Jun 2010
Programs: AC SE100K , 1MM, Hilton Diamond, KLM
Posts: 579
5.7.0 Iphone

Still am unable to check in on my Iphone 10
When i click checkin from the app it goes to a new screen which stays white and blank
using android it goes to the next page / screen and the wheel turns and allows me to check in
traacs is offline  
Old Oct 2, 2020, 4:32 pm
  #552  
Moderator, Air Canada; FlyerTalk Evangelist
 
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,775
The app no longer seems to show upgrades that are cleared in advance. I've done 7 eUped segments in the last week and on none of them have I showed up on the eUp list with the green check. It seems like it's now only standby and upgrades cleared at the gate.
Adam Smith is offline  
Old Oct 2, 2020, 4:49 pm
  #553  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
Originally Posted by Adam Smith
The app no longer seems to show upgrades that are cleared in advance. I've done 7 eUped segments in the last week and on none of them have I showed up on the eUp list with the green check. It seems like it's now only standby and upgrades cleared at the gate.
I'm pretty sure that's been the case since DCS migrated.
canadiancow is online now  
Old Oct 2, 2020, 4:53 pm
  #554  
Moderator, Air Canada; FlyerTalk Evangelist
 
Join Date: Feb 2015
Location: YYC
Programs: AC SE MM, FB Plat, WS Plat, BA Silver, DL GM, Marriott Plat, Hilton Gold, Accor Silver
Posts: 16,775
Originally Posted by canadiancow
I'm pretty sure that's been the case since DCS migrated.
Ah, okay. Pretty much all my tickets since then have been confirmed J, either paid or Aeroplan. I think I've only used eUps once since DCS migration before last week.
Adam Smith is offline  
Old Oct 5, 2020, 3:41 pm
  #555  
A FlyerTalk Posting Legend
 
Join Date: Sep 2012
Location: SFO
Programs: AC SE MM, BA Gold, SQ Silver, Bonvoy Tit LTG, Hyatt Glob, HH Diamond
Posts: 44,342
5.8

• Bid for an upgrade: Take advantage of the 'AC Bid Upgrade' program from the 'Overview' tab of your Trip details. You can now also use your Aeroplan miles to place your bid!
• Disrupted bookings: We've made it easier to identify and review bookings which have been disrupted by flights which are no longer operating or pending itinerary changes.
• Updated colours: Applied a fresh coat of paint to make text and buttons easier to read.
• Bug fixes to improve the stability of the app.
Bids just take you to the plusgrade site.
I don't have any current disrupted bookings to inspect.

I still think my top requests are:
1. Native seat selection
2. Native eUpgrades
3. More information about the booking (fare brand, fare class, etc.)
canadiancow is online now  


Contact Us - Manage Preferences - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service -

This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.