How can we help?

First, make sure you are using the same sign-in method you used when creating the account. Many login issues happen because a user originally chose Apple or Google sign-in but later tries a password instead, or vice versa. If you use email and password, try a password reset and open the newest reset email only. If you use Apple or Google, retry that same provider from the login screen. Also check that you are on a stable connection. If the app appears stuck after login, close and reopen it so the session can refresh properly.

Check junk, spam, promotions, and any filtered folders first, then confirm that the email address entered during signup was correct. If you requested more than one message, use the newest verification email because older links can expire or stop working. If you open the email on a different device from the one you are using the app on, the callback may feel less smooth. The easiest path is usually to open the latest link on the same device where FlightLeague is installed and then wait a moment for the app to finish processing it.

If profile setup seems stuck, check whether a required field is still missing, such as your name, mode choice, or another key onboarding detail. Optional items like a profile photo can usually wait, but the core profile fields need to be complete before the app can finish shaping your dashboard correctly. A poor connection can also interrupt the final save step, so try again on a stronger network and keep the app open until the process finishes. If it still looks frozen, reopen the app and review the setup screen for anything highlighted or still incomplete.

When an entry refuses to save, the most common causes are missing required route details, an incomplete date or duration field, or a temporary connection issue. For pilots, airport and aircraft details are especially important because they drive maps and stats. For travelers, departure, arrival, and airline details are usually the first things to review. If you are adding more optional fields, save the basics first and then edit the entry afterward if needed. That can help isolate whether a specific field is causing the problem rather than the whole logging flow being broken.

AI scan works best when the source image is clear, well lit, flat, and easy to read. Warnings or odd-looking results often happen when handwriting is difficult to interpret, airport codes are unclear, or the image crops off part of the record. The safest approach is to treat the scan as a draft and review every field before saving. If you can, retake the image with better lighting and less blur, then try again. If you are on the free tier and hit a usage limit, Pro expands scan access for users who rely on the tool more often.

A feed that looks stale is often just showing cached data while waiting for a refresh. Pull to refresh first, then check whether your network is stable. If you recently changed an entry from private to public, it may also take a moment before it feels visible in the social flow. A quiet feed can also be normal if you have few connections or little public activity in your network. If you are expecting more activity, confirm that your entries are public where intended and that you are looking at the right feed, such as Friends versus For You.

Go to the connections area and check whether the request is listed under outgoing rather than accepted. A missing request is often just still waiting for the other user to act. If you searched by name, verify that you targeted the right profile, especially if the name is common. Friend codes are usually more reliable for direct adds. If you removed or blocked a user previously, that can also affect how the connection behaves. In most cases, the request is not lost. It is simply still pending or tied to a different profile than the one you intended.

Start by checking the in-app notifications screen to see whether activity is arriving there even if device alerts are quiet. If nothing appears at all, confirm that there has actually been new activity such as comments, reactions, or connection requests. A slow or unstable connection can delay fresh notification states. If device alerts are the only thing missing, review your phone’s app notification permissions and make sure FlightLeague is allowed to send them. Marking items as read does not remove the underlying activity, so you can still review recent events from the notifications area itself.

Check the leaderboard metric and timeframe before assuming there is a bug. Weekly, monthly, and all-time leaderboards can look very different, and so can boards based on hours, flights, distance, or destinations. Pilot and Traveler mode also emphasise different kinds of logged activity. If your recent activity does not seem reflected yet, refresh the screen and confirm the relevant flights or trips were saved correctly. The sticky self-rank view can also make your position easier to follow even when you are lower down. In many cases the rank is correct, but the metric being viewed is not the one the user expected.

If export is unavailable, first confirm that you are looking in the right place, such as the relevant profile or history screen. Then check whether your current subscription level covers the export type or volume you are trying to use. Some export access, especially unlimited export use, is part of Pro. It is also worth reviewing whether there is enough complete data in the app to make the export useful. If you have only a handful of entries, the export may seem lighter than expected. Refreshing the screen or reopening the export entry point can also help if the option has not updated yet.

Analytics depend on having enough clean activity data to interpret. If your charts look blank, sparse, or delayed, check whether you have logged enough flights or trips and whether those entries include the key route and date details needed for summaries. Pilot analytics and Traveler analytics also differ, so make sure you are expecting the right type of insight for your mode. Some deeper analytics are part of Pro, so free-tier users may see a lighter version of the experience. A manual refresh is often enough to update a screen that is slightly behind.

If you deleted an entry, check that you are not still seeing an older cached view of the same screen. Refresh the relevant page or reopen the app. If you changed something from public to private, remember that it may still take a short moment for every social surface to catch up. In general, private means the entry should no longer behave like public social content, while deletion is the stronger step that removes the record itself. If you are unsure whether you deleted or only hid the item, review your history list first before recreating it and accidentally ending up with duplicates.