Troubleshooting
Problems with Jikita tags have their own page: Jikita troubleshooting.
Tracking
Tracking stops when the screen goes off
The most common problem, and almost always one of two settings.
- Location is not set to Always.
- Android: Settings → Apps → myJikita → Permissions → Location → Allow all the time, with Use precise location on.
- iOS: Settings → myJikita → Location → Always, with Precise Location on.
- Battery optimisation is restricting the app. Set myJikita to Unrestricted on Android, and check your manufacturer's own power manager — Samsung, Xiaomi, Huawei, OPPO and Vivo all add a layer on top of stock Android. The table is in Permissions.
Then test it: start an outing, lock the phone, walk for ten minutes, and look at the track.
Tracking stopped completely
Did you swipe the app out of the recent-apps list? That stops tracking on every phone, and no application can prevent it. Leave it in the background.
My position does not appear on the map
The phone has not got a GPS fix yet. Under trees or against a cliff this can take a minute or two; indoors it may never arrive. Go outside with a view of the sky.
If it never appears outdoors, check that location permission is granted and that precise location is on.
My track has gaps
Two quite different causes, and they are easy to tell apart:
- Gaps that coincide with no coverage are normal. The positions were recorded and sent later. See Coverage and white areas.
- Gaps that start when the screen went off are a permissions or battery problem. See above.
My position is inaccurate
GPS accuracy depends on terrain: narrow valleys, cliffs and dense forest all degrade it. Make sure precise location is enabled — approximate location is not good enough for this app to be useful.
Sharing
My contacts cannot see me
Work down the list:
- Is the outing actually started, not just planned?
- Were those contacts selected for this outing?
- Have they accepted your contact invitation?
- Do you have coverage? With no signal, positions are queued — the outing card tells you how many are waiting.
- Is tracking working at all? Check your own track first.
I am not getting notifications
- Notification permission granted to myJikita?
- Does a Focus mode, Do Not Disturb, or a per-app mute apply?
- Android: is the app restricted in the background? Same settings as tracking.
- iOS: is Background App Refresh on?
A contact who does not get notifications is not watching anything, so this is worth fixing properly.
The pin for someone I am following has not moved
Usually coverage, not catastrophe. Look at when their last position was captured, which the app shows separately from when it arrived. Read Silence is not evidence of anything.
I cannot stop my outing
If you have no signal, stop it anyway — the app records the stop locally and tells the server when it can. Get back into coverage before you assume the alarm is cleared.
Maps
The map is blank
| Symptom | Cause |
|---|---|
| Blank where you are, no signal | You are outside every downloaded area. Download areas before you leave. |
| Base map fine, no pistes | Normal — the ski layer is not included in offline downloads. |
| Blank everywhere, with signal | Connection problem or the tile server is unreachable. Try a different connection. |
A download will not finish
Check free storage and connection quality. Large areas are large; do it on wifi.
I deleted one area and another looks wrong
Overlapping areas are handled — deleting one should not blind the other. If you see otherwise, please report it with a screenshot.
Routes
My GPX file will not import
The app reports why on the route entry. Common causes: the file is not actually GPX, it is empty, or it was truncated by whatever exported it. Try re-exporting from the source.
The off-route warning is firing when I am fine
It fires at about 200 m from the line, after two consecutive positions. If you have deliberately taken a different line, that is the warning doing its job — it reports a difference, it does not judge it.
The off-route warning never fires
Was a planned route attached to the outing? Having a route in your library is not the same as attaching it, and it can only be attached when the outing is created.
Account
I was signed out on my own
The app always says why. Either the device was revoked — from another phone, or by you — or the stored credential could not be renewed. Sign in again.
Sign-in opens a browser
That is correct and deliberate. myJikita never sees your password; you type it into Alpik's identity service in a real browser where you can check the address bar. See Create your account.
It says my account is active on another device
Only one device can track at a time. Take over on the phone you are holding, or revoke the other one in Settings.
It will not let me sign out
If an outing is running, stop it first. If positions have not been synced, the app warns you before it discards them — get some signal, let it sync, then sign out.
Upgrading from an older build
Testers who had the app when it was called ALPIK or myALPIK must uninstall it and install myJikita fresh. The two are different installations to the phone: the old one will not update itself and its local outings cannot be recovered. Let it sync before removing it.
Reporting a problem
contact@alpik.fr. Please include:
- Phone model and OS version.
- The app version.
- What you did, what you expected, what happened.
- Roughly when it happened, and whether you had signal.
- A screenshot if there is anything to see.