SAS app:en - Hur kan den bli ännu bättre?

David Granström 2 skrev:”Simulated real time” I would say. At least it’s not 100 % perfect. But still very cool and helpful!Klicka för att utvidga...
Click to expand...
It's actually as close to real-time as we could get, there is a lot going on there, when a traveler passes through the gate, the boarding pass is scanned and a message is sent via the Departure Control System back to SAS where an application keeps storing the data, When you have that screen on, the app calls for backend to check whether the boarding has started, if it has, it will request every 10 seconds the count between check-in and passed the gate and keep on updating the view. The only simulation done is the slider moving smoothly, what we do there is within those 10 seconds we check the last data received by the client and the new data received by the backend and we move within those 10 seconds the slider, instead of jumping. So data is real-time but it might take a while to get through all data journeys, which might cause delays. There are probably 5-6 systems in between the source and the device. That said, when we did a field test it, it was pretty decent, but there could be multiple factors affecting this, like gate agents pre-boarding some travelers or manually boarding some travelers, also some lags on the events dispatching or any network failure in between.
 
6857a478-4edb-4465-a216-5cabb28a4081-jpeg.134705



I can’t see my upcoming booking, the app also says Device is offline.

The legacy SAS app is working and using the legacy SAS app I can find my booking.



iOS 16.1
 
I’m still not seeing final destination presented as “trip to”. No updates pending.


01c720a5-534b-4fef-9a4e-945b602e2fb8-jpeg.134707
 
FilipJ skrev:I’m still not seeing final destination presented as “trip to”. No updates pending.Visa bifogad bild 134707Klicka för att utvidga...
Click to expand...
Hi, yes, we know, this is fixed already and will be available in the next update, we waited now 7 days for Apple to approve our latest release, and we are not sure why it takes so long this time, normally the approval process takes a day or two.
 
GOTBound skrev:Works as aspected now.Klicka för att utvidga...
Click to expand...
Can't really say why this happened, when we show that offline banner is because we detect the device without a valid internet connection, it could be connected to a network but failed to be online, so the app failed to retrieve the next booking, let's see if it was a temporary glitch as we haven't seen any other reports about this.
 
SubArcticFlyer skrev:A bug maybee? I fly from LLA to ARN this friday, and then to MIA on saturday morning. On the "homepage" it shows as my upcoming trip to Stockholm. Is it because the flights is on separat days?Visa bifogad bild 134743Visa bifogad bild 134744Klicka för att utvidga...
Click to expand...
Yes, the application detects 3 bounds here, LLA ARN, ARN-MIA + return. So it's treating LLA-ARN as a standalone due to the stopover (it's technically speaking not a stopover but still a layover).
 
@massimo I filed a bugreport yesterday about the boarding card after about 1 second switches to next flight when current flight is delayed and boarding is started after orgin departure time.

Irritating when the gate alarms as wrong boarding card is scanned data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7



/ TT
 
TasselT skrev:@massimoI filed a bugreport yesterday about the boarding card after about 1 second switches to next flight when current flight is delayed and boarding is started after orgin departure time.Irritating when the gate alarms as wrong boarding card is scanned/ TTKlicka för att utvidga...
Click to expand...
Yep, I understand that. The reason is that we cache the boarding pass for quick and offline access, when we have an internet connection and a positive response from the backend we update the boarding passes, in this case, backend doesn't return the first boarding pass as we are after STD but only the second one, this explain the flickering and updating with disappearing the first BP, which is obviously not good. We are checking our logic, we should not remove a cached boarding pass unless that flight is canceled. So, we will fix this in a way or the other. Thanks for reporting this, impossible for us to replicate this use case from the office.

Which means I should fly more myself! data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
 
MLG55 skrev:@massimoHave reinstall the app several times but still Device is offline?Klicka för att utvidga...
Click to expand...
Strange stuff, never got any reports like this.

If you can't send a report from within the app as it is offline, would you mind sending me an email [email protected] with a bit more details like EB number so I can check if we have any logs from your device? Also would you mind testing by changing your network connection? If you are on WiFi could you switch to cell network? Also, could you let me know if your device is managed by your company? There could be port blocks by your internet provider or company proxy.
 
You must log in or register to reply here.
Back
Top