The most common problems met with the LaraClassifier Mobile App and the JobClass Mobile App, and how to fix them. Most of them come from the connection between the app and your website: the API address, the API token, the certificate, or the /.env file of the website.
Remember: the values of .env.local are compiled into the app. After changing them, restart with npx expo start --clear and rebuild the app for the stores. After changing the website's /.env, clear its configuration cache (Admin panel → Clear cache or php artisan config:clear).
Connection
| Symptom | Cause and fix |
|---|
| "Setup required" screen | EXPO_PUBLIC_API_URL or EXPO_PUBLIC_API_TOKEN is missing from .env.local. Add it, then run npx expo start --clear. |
| "Can't reach the server" | Wrong address, no internet connection, or an invalid HTTPS certificate. Open your EXPO_PUBLIC_API_URL followed by /categories in the phone's browser to check. |
| "Can't reach the server" with a website on your computer | The website doesn't accept connections from the network (start it on 0.0.0.0), the app uses a local domain instead of the IP address, the IP address of the computer changed (it can change when you reconnect to Wi-Fi), the firewall blocks the port, the phone is on another network or a guest network, or Expo Go isn't allowed to use the local network (iPhone: Settings → Expo Go → Local Network). See the "Testing with a website on your computer" section of Publishing the Mobile App. |
| "You don't have access to this API" | The token doesn't match the APP_API_TOKEN of the website, or the website's configuration is cached: clear the cache. |
| "Bot access is not allowed" | A security layer (firewall, CDN, hosting WAF) changed or blocked the request. Allow the requests whose User-Agent starts with ClassifiedsMobile/ (LaraClassifier) or JobBoardMobile/ (JobClass). |
| "Request failed (404)" on some screens | The website is older than LaraClassifier or JobClass 19.1.13. Update it. |
Content and Languages
| Symptom | Cause and fix |
|---|
| Listings load but photos don't (LaraClassifier), or job ads load but company logos don't (JobClass) | APP_URL in the website's /.env doesn't match the address used by the app (for example http vs https, with or without www). |
| A resume or an attachment doesn't open (JobClass) | The file links are built from APP_URL (see above), and they are temporary: go back and open the screen again to get a fresh link. |
| Empty categories or cities in some languages | Set FALLBACK_LOCALE_FOR_DB to the language of your data (usually en) in the website's /.env. |
| No custom fields in the posting form | The chosen category has no custom fields in the admin panel, or the website is older than 19.1.13. |
| No Terms or Privacy link | Your website has no page of type Terms or Privacy. Create them in Admin panel → Pages. |
| Arabic or Hebrew layout not right-to-left | The direction changes once the app has been closed and reopened. |
Uploads
| Symptom | Cause and fix |
|---|
| Photo or logo upload refused | The app compresses images to the maximum picture size of your upload settings. If that size is very low (under 300 KB) or the format is refused, adjust the upload settings in the admin panel. |
| Image upload refused with "must be a file of type: ." | The website accepts no image format: its IMAGE_DRIVER is imagick but the PHP running it has no Imagick extension. Set IMAGE_DRIVER=gd in the website's /.env, or install Imagick. This often happens when testing with php artisan serve or PHP's built-in server, which use the command-line PHP of your computer. |
| Resume upload refused (JobClass) | The file type or size is not allowed by the upload settings of the admin panel (file types, maximum file size). |
Expo and Builds
| Symptom | Cause and fix |
|---|
| Expo Go: "You need to be signed in" | Sign in with the same Expo account in Expo Go and with npx expo login on your computer. |
| EAS build fails | Open the build log link printed by EAS. Most failures come from a brand.json value (invalid identifier, missing image file). |
| The store refuses the build | The build number was already used: increase ios.buildNumber and android.versionCode in brand.json, then build again. |
Push Notifications, Social Sign-In and App Links
| Symptom | Cause and fix |
|---|
| No push notifications | Push is off in the Mobile App settings of the website, the user refused notifications, eas.projectId is missing, or the Android FCM credentials are missing. Expo Go on Android can't receive push. |
| Google sign-in fails | The client IDs of brand.json are not listed in the Mobile App settings of the website, or the Android SHA-1 fingerprint doesn't match the build. |
| Links open the browser, not the app | The Mobile App settings (iOS app ID, Android fingerprints) are missing or wrong, or the app was built before they were set. |
The setup of these features is described in Mobile App: Push Notifications, Social Sign-In and App Links.
Still Stuck?
Contact us through the Help Center with your purchase code, your LaraClassifier or JobClass version, the app version, the platform (iOS or Android), the exact message shown and the steps to reproduce the issue. Support covers the app as delivered; customizations, store account setup, and store review issues caused by your content or your store listing are not covered.
