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>
64 lines
1.8 KiB
TypeScript
64 lines
1.8 KiB
TypeScript
import type { ButtonProps } from "@/types/type";
|
|
import React from "react";
|
|
import { Text, TouchableOpacity } from "react-native";
|
|
|
|
const getBgVariantStyle = (variant: ButtonProps["bgVariant"]) => {
|
|
switch (variant) {
|
|
case "secondary":
|
|
return "bg-gray-500";
|
|
case "danger":
|
|
return "bg-rose-500";
|
|
case "success":
|
|
return "bg-emerald-500";
|
|
case "outline":
|
|
return "bg-transparent border-neutral-300 dark:border-neutral-700 border-[0.5px]";
|
|
default:
|
|
return "bg-[#0286ff]";
|
|
}
|
|
};
|
|
|
|
const getTextVariantStyle = (variant: ButtonProps["textVariant"]) => {
|
|
switch (variant) {
|
|
case "primary":
|
|
return "text-black dark:text-white";
|
|
case "secondary":
|
|
return "text-gray-100";
|
|
case "danger":
|
|
return "text-rose-100";
|
|
case "success":
|
|
return "text-emerald-100";
|
|
default:
|
|
return "text-white";
|
|
}
|
|
};
|
|
|
|
export const CustomButton = ({
|
|
onPress,
|
|
title,
|
|
bgVariant = "primary",
|
|
textVariant = "default",
|
|
iconLeft: IconLeft,
|
|
iconRight: IconRight,
|
|
className,
|
|
// Which touchable the button is built on. React Native's own works
|
|
// everywhere except inside a @gorhom/bottom-sheet on Android, where the
|
|
// sheet's gesture handler eats the first press — the button only fires on
|
|
// the second tap. Screens hosted in a sheet pass the sheet's touchable.
|
|
Touchable = TouchableOpacity,
|
|
...props
|
|
}: ButtonProps) => (
|
|
<Touchable
|
|
onPress={onPress}
|
|
className={`w-full rounded-full p-3 flex flex-row justify-center items-center shadow-md shadow-neutral-400/70 dark:shadow-neutral-950/70 ${getBgVariantStyle(bgVariant)} ${className}`}
|
|
{...props}
|
|
>
|
|
{IconLeft && <IconLeft />}
|
|
|
|
<Text className={`text-lg font-bold ${getTextVariantStyle(textVariant)}`}>
|
|
{title}
|
|
</Text>
|
|
|
|
{IconRight && <IconRight />}
|
|
</Touchable>
|
|
);
|