Mobile App: Push Notifications, Social Sign-In and App Links

These three features of the LaraClassifier Mobile App and the JobClass Mobile App need a few extra steps, on Expo, Google, Meta or Apple, and in the Mobile App settings of your website. They only work in builds made with EAS (test or store builds), not in Expo Go on Android. Rebuild the app after changing any of the values below.

This article follows Publishing the Mobile App on Google Play and the App Store: your brand.json must already be filled in and your Expo project created.

Push Notifications

Once set up, push notifications tell users about new messages, listings or job ads approved or expired, payments and account changes. On JobClass, employers are also told about new applications, and both sides about replies. Tapping a notification opens the conversation, the listing or the job ad.

1. Make sure eas.projectId is set in brand.json (step 6 of the publishing guide).
2. Android: create a Firebase project, add an Android app with your android.package, and upload its FCM V1 service account key with eas credentials (Android → Push Notifications), as described in the Expo guide.
3. iOS: EAS creates the push key during eas build when you accept it.
4. On your website, enable Admin panel → Settings → Mobile App → Push notifications.

Each notification type can be turned on or off in the notification settings of your admin panel, and users choose the types they receive in the notification preferences of their account on the website, as for emails.

Social Sign-In (Google and Facebook)

The Continue with Google and Continue with Facebook buttons appear when the provider is enabled on your website (Admin panel → Settings → Social Login) and its IDs are set in the social section of brand.json. Leave these IDs empty to hide the buttons.

Google

1. In the Google Cloud console, in the project used for your website's Google login, create three OAuth client IDs:
   • iOS, with your ios.bundleIdentifier;
   • Android, with your android.package and the SHA-1 fingerprint shown by eas credentials;
   • Web.
2. Put them in the social section of brand.json: googleIosClientId, googleAndroidClientId and googleWebClientId.
3. On your website, add the three client IDs, separated by commas, in Admin panel → Settings → Mobile App → Google client IDs, so the website accepts the tokens issued to the app.

Facebook

1. In Meta for Developers, open the app used by your website's Facebook login and add the iOS and Android platforms with your bundle identifier and package name.
2. Put the app ID in the social section of brand.json (facebookAppId).

App Links

With app links, a link to one of your listings or job ads (shared by email, chat or social networks) opens straight in the app when it is installed: universal links on iOS, app links on Android. The app side is configured automatically from EXPO_PUBLIC_API_URL, which must be the public HTTPS address of your website.

On your website, fill in Admin panel → Settings → Mobile App:

• iOS app ID: your Apple Team ID followed by your bundle identifier, for example AB12CD34EF.com.mycompany.classifieds or AB12CD34EF.com.mycompany.jobs.
• Android package and SHA-256 fingerprints: your android.package, and the SHA-256 certificate fingerprint shown by eas credentials (if you use Google Play App Signing, also add the one shown in Play Console → App integrity).

Your website then serves /.well-known/apple-app-site-association and /.well-known/assetlinks.json. Rebuild the app once the website is set up.

If Something Doesn't Work

For other issues, see Mobile App Troubleshooting.