Troubleshooting

31. Troubleshooting

This section lists the errors most often seen while setting up Foodie, with their causes and fixes. Also see the FAQ for the Flutter “Missing project_info object” error.

31.1. “Missing or insufficient permissions” (PERMISSION_DENIED)

Firestore reads/writes are being blocked by your security rules.

  • Confirm you published rules in Firestore Database → Rules → Publish — see Create Firebase Project.
  • Check the Storage → Rules tab too — image uploads use a separate ruleset from Firestore.
  • Confirm every panel points at the correct database — see FIREBASE_PROJECT_DB below.

31.2. “The query requires an index” (FAILED_PRECONDITION)

A Firestore composite index is missing for a filter/sort query.

  • Deploy the supplied indexes — see Deploy Firestore Indexes.
  • Or open the link in the error message: it opens the Firebase console with the required index pre-filled. Click Create index and wait for it to finish building.

31.3. Data loads on one panel but not the other / “client is offline”

This almost always means the panels point at different Firestore databases.

  • Ensure FIREBASE_PROJECT_DB is identical in the Admin, Restaurant and panels’ .env files — (default) in a normal installation.
  • Verify every FIREBASE_* credential belongs to the same Firebase project.

31.4. Panels open but every list is empty

The demo Firestore collections were never imported.

31.5. “auth/unauthorized-domain” on login

  • In the Firebase console go to Authentication → Settings → Authorized domains and add your website and restaurant-panel domains.
  • For Google login, also confirm the OAuth 2.0 client’s authorised origins and redirect URIs — see Restaurant Panel Setup.

31.6. “auth/operation-not-allowed”

The sign-in provider you are using is not enabled. Enable Email/Password, Phone, Google (and Apple if used) under Authentication → Sign-in method.

31.7. Push notifications are not received

  • Upload the Firebase service-account JSON and set the Sender ID under Settings → Notification Settings — see Admin Panel Setup.
  • Confirm the service-account file exists at storage/app/firebase/credentials.json.
  • On mobile, verify google-services.json / GoogleService-Info.plist are present and match the package name.
  • For iOS, upload the APNs authentication key under Project Settings → Cloud Messaging.

31.8. Orders are never auto-cancelled and scheduled reminders never arrive

  • The cron entry is missing — add it as described in Cron & Scheduled Tasks.
  • NODE_PATH in the Admin Panel’s .env is empty or wrong. Run which node and paste the absolute path.
  • npm install was never run in the Admin Panel root, so the scripts have no dependencies.

31.9. A payment starts but never completes

  • Re-check the gateway’s credentials under Payment Methods — a secret key pasted with a trailing space is the most common cause.
  • Confirm you are in the right mode: sandbox keys fail against the live endpoint and vice versa.
  • Check the gateway’s Return / Cancel / Notify URLs in both the admin panel and the provider’s dashboard. They must point at your live HTTPS domain and match on both sides.
  • Make sure the panel is served over HTTPS — most providers refuse to redirect back to a plain HTTP callback.
  • Read storage/logs/laravel.log in the panel that started the payment; the provider’s rejection reason is recorded there.

31.10. Images fail to upload

  • Make sure Firebase Storage is enabled and its rules are published.
  • Check the file size and type, and the PHP limits upload_max_filesize and post_max_size.

31.11. Google Maps shows a “For development purposes only” watermark or a grey map

  • Enable Billing on your Google Cloud project and make sure the key is set — see Create Google Map API Key.
  • Enable every required API (Maps JavaScript, Maps SDK for Android/iOS, Places, Geocoding, Directions) and relax overly strict key restrictions while testing.

31.12. No restaurants show for a customer address

  • No zone covers that address — draw one under Live Monitoring → Zone.
  • The search radius is too small — raise it under Settings → Radius Configuration.
  • The restaurants are not approved, or their address falls outside the zone polygon.

31.13. “Missing project_info object” (Flutter / Android build)

The google-services.json file is missing or in the wrong place. See the detailed fix in the FAQ.

Recent Posts

    Archives

    No archives to show.

    Categories

    • No categories

    Blog Categories

    • No categories

    Archives

      Categories

      • No categories