CrewLink notification<\/span> is a pending (waiting for confirmation) CrewLink roster change issued by the Airline.<\/li>\n<\/ul>\nNotifications<\/span> are sent for:<\/p>\n\n- Pending CrewLink notifications<\/span><\/li>\n
- CrewLink validity end date<\/span> changes<\/li>\n<\/ol>\n
Both actions above are called Server check<\/span>. The Server check<\/span> always does both actions together in that order, and in one go. It checks for any pending CrewLink notifications<\/span> and for a CrewLink validity end date<\/span> change.<\/p>\nWhen does a Server check<\/span> trigger?<\/p>\n\n- Automatic<\/strong> : Rostoics uses the iOS background fetch (BF) framework, which is active when the App is in background (= App is still running but not in foreground). To avoid hammering the servers, Server checks<\/span> are spaced by at least 15 minutes (as of this writing – hardcoded, might change in the future). This doesn’t mean that BF fires every 15 minutes. The spacing could be hours, depending on battery life, user’s habits regarding his device and\/or this App, the time of the day, network quality, … Basically, BF is a blackbox. Apple doesn’t reveal details when exactly it triggers. BF tries to optimize in terms of battery life and users need\/wish to have updated information available when requested (some kind of simple artificial intelligence).<\/li>\n
- Manual – App suspended<\/strong> : Because of the somewhat random behavior of BF, a Server check<\/span> also fires when the App is starting up from suspended mode (= when the App doesn’t run in background, = the App was suspended (e.g. by App Switcher)).<\/li>\n
- Manual – App in foreground<\/strong> : On top, notifications can also be forced while the App is running in foreground by using the Pull-to-refresh feature from the Info Tab.<\/li>\n<\/ol>\n
Info Tab shows details about the Server checks<\/span>:
\nLast notif. check<\/span> : when (date & time) the last Server check<\/span> took place
\nCrewLink validity end date<\/span> : last date roster can be downloaded<\/p>\nBadge icons are used to show the user on the Home screen if there are any notifications. 1<\/span> can either be a pending CrewLink notification<\/span> or a change in CrewLink validity end date<\/span>. Check the Notification Centre which one fired. 2<\/span> means both were triggered. They appear the as grouped notifications in the Notification Centre.<\/p>\nWhen are badge icons reset?<\/p>\n
\n- Pending Crewlink notifications<\/span>:\n
\n- when confirmed<\/li>\n
- anytime automatic or manual Server checks<\/span> don’t find a pending CrewLink notification<\/span> (anymore)<\/li>\n
- when Reset settings<\/span> (Settings Tab) is used<\/li>\n<\/ul>\n<\/li>\n
- CrewLink validity end date<\/span> changes:\n
\n- after a successful download of a roster, using the CrewLink validity End date is used as End date<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
Be advised about the following terminology used on this page. By Notifications, iOS notifications are meant. They appear on the Lock Screen and Notification Centre of your Apple device. A CrewLink notification is a pending (waiting for confirmation) CrewLink roster change issued by the Airline. Notifications are sent for: Pending CrewLink notifications CrewLink validity end… <\/p>\n
Read More<\/i><\/a><\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[32],"tags":[],"class_list":["post-831","post","type-post","status-publish","format-standard","hentry","category-rosterx"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5mjlH-dp","jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/posts\/831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/comments?post=831"}],"version-history":[{"count":23,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/posts\/831\/revisions"}],"predecessor-version":[{"id":885,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/posts\/831\/revisions\/885"}],"wp:attachment":[{"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/media?parent=831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/categories?post=831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.geohei.lu\/geoheiWP\/wp-json\/wp\/v2\/tags?post=831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}