KrikoriosandClaude Opus 5
8807ff41c5
Driver onboarding now photographs the licence, ID card and vehicle
registration and reads the credential fields off them, plus a camera-only
profile selfie riders check the arriving driver against. Adds in-app chat
and WebRTC calls, push-backed ride offers, ratings, cancellation and
payment sheets, settlement, and the owner dashboard endpoints behind them.
Camera permission on Android:
- Declare CAMERA and READ_MEDIA_IMAGES in the manifest. expo-image-picker's
own plugin never declares CAMERA, and Android denies a request for an
undeclared permission instantly and silently — no dialog is ever shown,
which is indistinguishable from the app not asking at all.
- Handle canAskAgain: once Android stops showing the dialog, repeating why
we need it is a dead end, so offer Open Settings instead (lib/capture-
permission.ts), matching what the location flow already did.
Session: a 401 on a request that carried a token now ends the session
instead of being reinterpreted per-screen — driver-home had been reading it
as "this user has no driver profile" and showing an onboarding form to an
already-onboarded driver. Requests without a token are exempt so a failed
sign-in doesn't sign you out, and the notification is latched per token so
concurrent polls tear the session down once. (root) gains the auth guard
that turns that into the sign-in screen; app/index.tsx only guarded the way
in, leaving a session that ended mid-screen with nowhere to go.
Also ignore .uploads/ — it holds driver licence, ID and vehicle scans plus
profile photos, which are personal data and must not be committed.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
47 lines
1.6 KiB
TypeScript
47 lines
1.6 KiB
TypeScript
// Turning coordinates back into something a person recognises.
|
|
//
|
|
// Shared by the initial location fix and the map pin adjuster, so the address
|
|
// a rider sees while dragging the pin is formatted exactly like the one that
|
|
// was filled in for them automatically — two different shapes for the same
|
|
// place would read as a bug.
|
|
//
|
|
// Uses expo-location's on-device geocoder rather than the Places API: it costs
|
|
// nothing, works without the Google key, and this is a label, not a search.
|
|
|
|
import * as Location from "expo-location";
|
|
|
|
import { tr } from "@/lib/i18n";
|
|
|
|
/**
|
|
* A short, human address for a point — "Hamra, Beirut" — or the generic "your
|
|
* location" label when the geocoder has nothing useful. Never throws: a failed
|
|
* lookup costs the label, never the coordinates.
|
|
*/
|
|
export const addressForCoords = async (
|
|
latitude: number,
|
|
longitude: number,
|
|
): Promise<string> => {
|
|
try {
|
|
const [place] = await Location.reverseGeocodeAsync({ latitude, longitude });
|
|
if (!place) return tr("common.yourLocation");
|
|
|
|
// Street-level first, falling back through progressively coarser fields:
|
|
// a pin dropped in the middle of a field still deserves a name.
|
|
const line = [
|
|
place.name ?? place.street,
|
|
place.district ?? place.city ?? place.subregion,
|
|
place.region,
|
|
]
|
|
.filter(Boolean)
|
|
// The geocoder often repeats a value across fields ("Beirut, Beirut").
|
|
.filter((part, index, all) => all.indexOf(part) === index)
|
|
.slice(0, 2)
|
|
.join(", ");
|
|
|
|
return line || tr("common.yourLocation");
|
|
} catch (error) {
|
|
console.log("[REVERSE_GEOCODE]: ", error);
|
|
return tr("common.yourLocation");
|
|
}
|
|
};
|