Troubleshooting

24. Troubleshooting

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

24.1. “Missing or insufficient permissions” (PERMISSION_DENIED)

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

  • Make sure you published the security rules from 13.9. Firestore Security Rules in Firestore Database → Rules → Publish.
  • Confirm you are pointing at the correct database — see FIRESTORE_DATABASE_NAME below.

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

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

  • Deploy the provided indexes — see 15. Firestore Database Indexing.
  • Alternatively, open the link shown in the browser console / error message; it opens the Firebase console with the required index pre-filled — click Create index and wait for it to finish building.

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

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

  • Ensure FIRESTORE_DATABASE_NAME is identical in both the Admin Panel and User Panel .env files ((default) for production, or the same named database such as staging).
  • Verify all FIREBASE_* credentials belong to the same Firebase project.

24.4. “auth/unauthorized-domain” on login

Firebase Authentication is rejecting sign-in because your domain is not whitelisted.

  • In the Firebase console go to Authentication → Settings → Authorized domains and add your website domain (e.g. yourdomain.com).
  • For Google login, also confirm the OAuth 2.0 client’s authorized origins and redirect URIs — see 21. User Panel Setup.

24.5. “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 — see 7. Firebase Authentication.

24.6. Push notifications are not received

  • Upload your Firebase service-account JSON and set the Sender ID in Settings → Notification Settings — see 16. Admin Panel Setup.
  • Confirm the service account file exists at storage/app/firebase/credentials.json.
  • On the mobile app, verify google-services.json / GoogleService-Info.plist are present and match the project.

24.7. Images fail to upload

  • Make sure Firebase Storage is enabled — see 13.7.
  • Publish the Storage security rules — see 13.10. Storage Security Rules.
  • Check the upload size/type: uploads are limited by the rules (e.g. images only, up to 10 MB for ads, 5 MB for profile images).

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

  • Enable Billing on your Google Cloud project and make sure the API key is set — see 22. Create Google Map API Key.
  • Enable the required APIs (Maps JavaScript API, Places API, Geocoding API) and remove overly strict key restrictions while testing.

24.9. “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