1. CRITICAL: Double idempotency check silently discarded every notification. process_scheduled_notifications called try_mark_notification_pushed first, then send_fcm called it again and saw "already pushed" → skipped FCM send. Fix: Remove the check from process_scheduled_notifications; send_fcm's own check is sufficient (and needed for direct Flutter client calls). 2. SEND_FCM_URL env var crash: If not configured, edge function crashed on module load. Fix: Derive from SUPABASE_URL (always auto-set) as fallback. 3. Timing windows too narrow: ±30s windows with 60s cron intervals could miss events between runs. Fix: Widen to ±90s. ON CONFLICT DO NOTHING prevents duplicates, making wider windows safe. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github | ||
| .vscode | ||
| android | ||
| assets | ||
| ios | ||
| lib | ||
| linux | ||
| macos | ||
| supabase | ||
| test | ||
| web | ||
| windows | ||
| .gitignore | ||
| .metadata | ||
| analysis_options.yaml | ||
| CLAUDE.md | ||
| firebase.json | ||
| GEMINI.md | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| README.md | ||
| RELEASE_NOTES.md | ||
tasq
A new Flutter project.