GFL-AUTH-001Blocking
Credentials not accepted
The email or password does not match a confirmed account.
- Platform
- Android, iOS
- Affected areas
- Sign-in
- Retry
- Yes
Likely causes
- •The email or password differs from the confirmed account details.
- •A confirmation or reset link is no longer the newest one.
- •Several attempts in a short time triggered a temporary wait.
Steps
- •Request one fresh link and use only the newest.
- •For rate limiting, wait and retry with the same confirmed email.
Start diagnosticGFL-AUTH-002Blocking
Email not confirmed
The account exists but sign-in requires the newest confirmation link first.
- Platform
- Android, iOS
- Affected areas
- Sign-in
- Retry
- Yes
Likely causes
- •The email or password differs from the confirmed account details.
- •A confirmation or reset link is no longer the newest one.
- •Several attempts in a short time triggered a temporary wait.
Steps
- •Request one fresh link and use only the newest.
- •For rate limiting, wait and retry with the same confirmed email.
Start diagnosticGFL-AUTH-003Blocking
Sign-in link expired or invalid
The link expired, was already used or no longer contains the required session data.
- Platform
- Android, iOS
- Affected areas
- Sign-in
- Retry
- Yes
Likely causes
- •The email or password differs from the confirmed account details.
- •A confirmation or reset link is no longer the newest one.
- •Several attempts in a short time triggered a temporary wait.
Steps
- •Request one fresh link and use only the newest.
- •For rate limiting, wait and retry with the same confirmed email.
Start diagnosticGFL-AUTH-004Notice
Too many requests
The service is temporarily limiting further sign-in, email or generation attempts.
- Platform
- Android, iOS
- Affected areas
- Sign-in
- Retry
- Yes
Likely causes
- •The email or password differs from the confirmed account details.
- •A confirmation or reset link is no longer the newest one.
- •Several attempts in a short time triggered a temporary wait.
Steps
- •Request one fresh link and use only the newest.
- •For rate limiting, wait and retry with the same confirmed email.
Start diagnosticGFL-SUPPORT-001Notice
Connection unavailable
The app could not complete the required online verification reliably.
- Platform
- Android, iOS
- Affected areas
- Tour resume, Sign-in
- Retry
- Yes
Likely causes
- •The tour was opened with a different account or from an outdated state.
- •The safe online check has not completed yet.
Steps
- •Use the same account and connect for verification.
- •Never start an old tour marked unsafe.
Start diagnosticGFL-LOCATION-001Blocking
Location access denied
GFL cannot currently read foreground location.
- Platform
- Android, iOS
- Affected areas
- Location
- Retry
- Yes
Likely causes
- •Location permission or the device location services are switched off.
- •Buildings, weather or the current surroundings are weakening the GPS signal.
Steps
- •Allow foreground location and enable GPS/services.
- •Move outdoors and request position again.
Start diagnosticGFL-LOCATION-002Blocking
Allow location in system settings
The system will not show another in-app prompt; permission must be changed manually.
- Platform
- Android, iOS
- Affected areas
- Location
- Retry
- Yes
Likely causes
- •Location permission or the device location services are switched off.
- •Buildings, weather or the current surroundings are weakening the GPS signal.
Steps
- •Allow foreground location and enable GPS/services.
- •Move outdoors and request position again.
Start diagnosticGFL-LOCATION-003Blocking
GPS or location services are off
The app may have permission but the device is not supplying a position.
- Platform
- Android, iOS
- Affected areas
- Location
- Retry
- Yes
Likely causes
- •Location permission or the device location services are switched off.
- •Buildings, weather or the current surroundings are weakening the GPS signal.
Steps
- •Allow foreground location and enable GPS/services.
- •Move outdoors and request position again.
Start diagnosticGFL-LOCATION-004Notice
GPS accuracy is too weak
Current accuracy is not sufficient for a reliable arrival or task check.
- Platform
- Android, iOS
- Affected areas
- Location, Compass
- Retry
- Yes
Likely causes
- •Location permission or the device location services are switched off.
- •Buildings, weather or the current surroundings are weakening the GPS signal.
Steps
- •Allow foreground location and enable GPS/services.
- •Move outdoors and request position again.
Start diagnosticGFL-TOUR-001Blocking
No safe route found
No route matched the start, mode, filters and safety policy.
- Platform
- Android, iOS
- Affected areas
- Tour planning
- Retry
- Yes
Likely causes
- •The start point, distance, duration or filters cannot be combined safely in this area.
- •Location or internet access was not stable enough while planning.
Steps
- •Check internet, location and an active mode.
- •Reduce distance/duration or loosen filters and generate once.
Start diagnosticGFL-TOUR-002Blocking
Target distance cannot be met
Available routes fall outside the allowed distance tolerance.
- Platform
- Android, iOS
- Affected areas
- Tour planning, Runner, Custom
- Retry
- Yes
Likely causes
- •The start point, distance, duration or filters cannot be combined safely in this area.
- •Location or internet access was not stable enough while planning.
Steps
- •Check internet, location and an active mode.
- •Reduce distance/duration or loosen filters and generate once.
Start diagnosticGFL-TOUR-003Blocking
Target duration cannot be met
Available routes fall outside the allowed duration tolerance.
- Platform
- Android, iOS
- Affected areas
- Tour planning, Explorer, Runner, Custom
- Retry
- Yes
Likely causes
- •The start point, distance, duration or filters cannot be combined safely in this area.
- •Location or internet access was not stable enough while planning.
Steps
- •Check internet, location and an active mode.
- •Reduce distance/duration or loosen filters and generate once.
Start diagnosticGFL-TOUR-004Blocking
Tour could not be saved safely
Start is blocked so a tour never begins without a recoverable state.
- Platform
- Android, iOS
- Affected areas
- Tour planning, Tour resume
- Retry
- Yes
Likely causes
- •The start point, distance, duration or filters cannot be combined safely in this area.
- •Location or internet access was not stable enough while planning.
Steps
- •Check internet, location and an active mode.
- •Reduce distance/duration or loosen filters and generate once.
Start diagnosticGFL-TOUR-005Blocking
Saved tour cannot resume safely
Snapshot, account or authoritative state no longer match safely.
- Platform
- Android, iOS
- Affected areas
- Tour resume
- Retry
- No
Likely causes
- •The tour was opened with a different account or from an outdated state.
- •The safe online check has not completed yet.
Steps
- •Use the same account and connect for verification.
- •Never start an old tour marked unsafe.
Start diagnosticGFL-MAP-001Notice
Map unavailable
The map module, location data or connection is unavailable for this view.
- Platform
- Android, iOS
- Affected areas
- Maps, Location
- Retry
- Yes
Likely causes
- •GPS or device sensors are not providing stable enough readings right now.
- •Metal, a magnetic case or the surroundings are affecting the compass heading.
Steps
- •Wait outdoors for GPS and calibrate heading.
- •Compare with real paths and stop if unsafe.
Start diagnosticGFL-MAP-002Notice
Compass not reliably available
The device is not providing sufficient or stable heading data.
- Platform
- Android, iOS
- Affected areas
- Compass, Accessibility
- Retry
- No
Likely causes
- •GPS or device sensors are not providing stable enough readings right now.
- •Metal, a magnetic case or the surroundings are affecting the compass heading.
Steps
- •Wait outdoors for GPS and calibrate heading.
- •Compare with real paths and stop if unsafe.
Start diagnosticGFL-PROGRESS-001Blocking
Media permission required
A selected photo, video or audio task needs camera or microphone access.
- Platform
- Android, iOS
- Affected areas
- Tasks, Media permissions
- Retry
- Yes
Likely causes
- •The selected task is missing camera, microphone or location permission.
- •The task has not finished confirming or syncing yet.
Steps
- •Check task type and required permission.
- •Submit once and wait for confirmation.
Start diagnosticGFL-NOTIFY-001Information
Push technically unavailable
Permission, device registration or the native notifications module is missing.
- Platform
- Android, iOS
- Affected areas
- Notifications
- Retry
- Yes
Likely causes
- •Notifications are disabled in GFL or the device settings.
- •The current test build or device does not fully support push notifications.
Steps
- •Check app switch, category and system permission.
- •Open GFL online and re-register by switching Push off/on once.
Start diagnosticGFL-STORE-001Information
Real-money purchases disabled
This is intentional; only the earned-Coin economy is active.
- Platform
- Android, iOS
- Affected areas
- real-money purchases, earned Coins
- Retry
- No
Likely causes
- •Real-money purchases are intentionally not enabled.
- •The confirmed Coin balance has not refreshed for this account yet.
Steps
- •Open Store online with the same account.
- •Do not purchase twice; real-money IAP remains disabled.
Start diagnosticGFL-GALLERY-001Information
Public Gallery disabled
Feed, publishing and public report/block functions are not released.
- Platform
- All platforms, Android, iOS
- Affected areas
- public Gallery
- Retry
- No
Likely causes
- •The public release or feature has not been enabled yet.
- •The download or feature claim did not come from a confirmed GFL channel.
Steps
- •Check getfreelost.app instead of a third-party download link.
- •Treat missing public store links as current status, not a technical error.
Start diagnosticGFL-ACCOUNT-001Blocking
Sign in again to delete
The deletion request has no valid session for the affected account.
- Platform
- Android, iOS
- Affected areas
- Account deletion, Sign-in
- Retry
- Yes
Likely causes
- •The session expired or no longer belongs to the account being deleted.
- •A deletion is already running, needs a waiting period or has not been fully confirmed.
Steps
- •Take the action matching the public deletion code.
- •For a persistent failure use only the official deletion route.
Start diagnosticGFL-ACCOUNT-002Notice
Account deletion already running
An existing deletion job is active and must not be duplicated.
- Platform
- Android, iOS
- Affected areas
- Account deletion
- Retry
- Yes
Likely causes
- •The session expired or no longer belongs to the account being deleted.
- •A deletion is already running, needs a waiting period or has not been fully confirmed.
Steps
- •Take the action matching the public deletion code.
- •For a persistent failure use only the official deletion route.
Start diagnosticGFL-ACCOUNT-003Notice
Resume deletion later
The existing job is waiting for a safe retry time.
- Platform
- Android, iOS
- Affected areas
- Account deletion
- Retry
- Yes
Likely causes
- •The session expired or no longer belongs to the account being deleted.
- •A deletion is already running, needs a waiting period or has not been fully confirmed.
Steps
- •Take the action matching the public deletion code.
- •For a persistent failure use only the official deletion route.
Start diagnosticGFL-ACCOUNT-004Blocking
Deletion cannot retry automatically
After self-service, the request needs the official legal deletion route.
- Platform
- Android, iOS
- Affected areas
- Account deletion
- Retry
- No
Likely causes
- •The session expired or no longer belongs to the account being deleted.
- •A deletion is already running, needs a waiting period or has not been fully confirmed.
Steps
- •Take the action matching the public deletion code.
- •For a persistent failure use only the official deletion route.
Start diagnosticGFL-ACCOUNT-005Blocking
Account deletion incomplete
At least one protected deletion phase was not confirmed safely.
- Platform
- Android, iOS
- Affected areas
- Account deletion
- Retry
- Yes
Likely causes
- •The session expired or no longer belongs to the account being deleted.
- •A deletion is already running, needs a waiting period or has not been fully confirmed.
Steps
- •Take the action matching the public deletion code.
- •For a persistent failure use only the official deletion route.
Start diagnostic