Typical Issues

The site shows a 500 error after install

Check that storage and bootstrap/cache are writable, that .env exists and has an app key, and read storage/logs/laravel.log for the real error. Then run php artisan optimize:clear.

CORS errors on the website or apps

The admin server must allow the website's domain. Check the CORS settings in config/cors.php and your web-server headers, then clear the config cache.

The Flutter app does not run

Usually the app version and the Flutter SDK version do not match. Run flutter doctor and use the SDK version listed for your release.

Map or location errors

If you restrict your Google Maps keys, use separate client and server keys, or use a single unrestricted key. Make sure billing is enabled and the required APIs are switched on.

Features missing in the admin panel or an app

The admin panel and the apps must be on matching versions. Update whichever one is behind.

Push notifications do not arrive

Test on a real device, because emulators do not receive push notifications. Confirm the package name matches the Firebase app, the service account JSON is saved in the admin, and the app was reinstalled after changing config files.

Emails are not sent

Check the SMTP settings, make sure the sender address belongs to your domain, run the queue worker, and check the spam folder. Errors are written to the Laravel log.

The website loads slowly the first time

A Flutter web app downloads its engine on the first visit, then caches it. Use a fast server with compression and caching enabled.

Note: Still stuck? Submit a support ticket with your admin URL, the version you are on and the exact error message.