Android/iOS App Settings¶

Menu Location: Settings > Mobile App > App Settings (app-settings.php). This page is no longer its own menu entry; open it from the App Settings button at the top right of the Mobile App page, or from its breadcrumb.

Last Updated: 2026-10-03

Overview¶

The Android/iOS App Settings page holds the values your mobile app uses to identify itself in the app stores and to send push notifications. The page carries the note "These settings will all be set by a Kiva Logic admin - do not change these by yourself."

Primary Functions:

Store listing identifiers for the iOS and Android apps
Firebase Cloud Messaging (FCM) credentials for push notifications
Android app purchase and access keys

Settings on This Page¶

Field	What it is
iTunes App ID	The numeric Apple App Store app id (for example `1127256404`)
iTunes App Argument	The URL the iOS app opens (for example `https://www.kivalogic.com/`)
Google Play App ID	The Android package name (for example `com.kivalogic.app`)
App Bundle ID / Package Name	The app's id on both iOS and Android (for example `com.kivalogic.yourstore`). Used by the deep-link association files
Apple Developer Team ID	The Apple team that signs your iOS app. Normally left blank to use the shared Kiva Logic team
Android SHA-256 Signing Certs	Your app's Google Play App Signing certificate fingerprint(s), one per line. Required for Android links to open the app
Deep-link Domains	Optional override. Normally left blank; defaults to your store's domain
FCM Project ID	Optional override. Normally left blank, the project is detected automatically and shown next to the field
FCM Service Account JSON	Optional override. Normally left blank, the service-account key is loaded automatically and the field reports whether a key was found
Push delivery	Which push service your app sends through: OneSignal (the apps customers already have), Both (rollover), or FCM only (the new apps)
Android Item Purchase Code	Purchase code for the Android app
Android App Access Key	Access key for the Android app

All fields save together when you submit the form.

The page also lists your app's Android theme colors (colorPrimary, colorAccent, and similar color resources). Those are set in the app build, not on this form.

Push Notifications¶

Push notifications can be delivered two ways, and this page controls which one your store uses:

OneSignal, the service the apps your customers already have installed use
Firebase Cloud Messaging (FCM), used by the new apps

Push delivery

Leave on OneSignal (the default) while your customers are still on the old apps
Choose Both during the rollover, so each device is reached by whichever service it registered with
Choose FCM only once all of your customers have moved to the new apps

FCM Project ID and FCM Service Account JSON are optional overrides, and are normally left blank. Both are filled in automatically:

FCM Project ID is detected from the tenant's app registration and shown under the field ("Auto-detected... currently project name"). Enter a value here only to point a store at a different project
FCM Service Account JSON is loaded from the environment file, where the key is stored once and shared across tenants in the same project. The field reports Key detected or No key found yet so you can tell at a glance whether the key is in place

FCM is only one of the two transports. Push is available as soon as either push service is configured (OneSignal, or FCM), so a store still on OneSignal keeps sending normally. When neither is configured, the Push Messages page redirects away and the "Send Push Message" buttons on the customer, order, and weekly cycle pages stay hidden.

FCM relays iOS notifications to Apple's APNs, so there is no push certificate to upload here or renew each year. The APNs key lives in the Firebase project instead.

Deep Links and Universal Links¶

Deep links let a link in an email, text, or push notification open your app directly on the right screen (edit this week's box, a product, past orders) instead of opening a web browser. The settings in the Deep Links & Universal Links section publish your app's identity so the phone knows the link belongs to your app.

App Bundle ID / Package Name is your app's id, the same on iOS and Android (for example com.kivalogic.yourstore). If left blank it falls back to your Google Play App ID, then to a name based on your store
Apple Developer Team ID is normally left blank, which uses the shared Kiva Logic Apple account. Set it only if your store ships under its own Apple account
Android SHA-256 Signing Certs is the one setting you usually have to fill in by hand. Paste your app's Google Play App Signing certificate fingerprint (from the Play Console, under App integrity, App signing), one per line. Without it, Android links will open the browser instead of your app. Use the Play App Signing certificate, not the upload key, because Google re-signs your app when you publish it
Deep-link Domains is normally left blank and defaults to your store's domain

After you set these, a new app build must be published for links to open the app. Links tapped on an older build will keep opening the browser.

Common Use Cases¶

Use Case 1: Check Whether FCM Is Ready for a Store¶

Goal: Confirm push can send for this store without touching any credentials

Steps:

Go to Settings > Android/iOS App Settings
Read the note under FCM Project ID: it shows the project detected for this store, or "none"
Read the note under FCM Service Account JSON: Key detected means the key is loaded and ready; No key found yet means the key has not been added for this store's project
If the key is missing, that is a Kiva Logic setup item, not something to paste on this page. Everything is configured once in the environment file and shared across all stores in the project

Use Case 2: Push Options Are Missing¶

Goal: The "Send Push Message" buttons are not showing on customer or order pages

Steps:

Check that push is configured: either a OneSignal key is in place, or FCM is set up (see Use Case 1). When neither is set, every push control is hidden
Check the push toggle is on
Confirm the customer has the app installed and has accepted the notification prompt

Troubleshooting¶

Push Messages Page Redirects Away¶

Symptoms:

Opening Tools > Push Messages bounces you to the apps configuration page

Cause:

Neither push service is configured: no OneSignal key and no FCM credentials

Solution:

Check that FCM Service Account JSON shows Key detected, or have a Kiva Logic admin confirm the OneSignal key is set for your store
Reload the Push Messages page

Customers Are Not Receiving Push¶

Check:

Push is configured and the Push delivery setting matches the app your customers have: a store set to FCM only will not reach customers still on the old OneSignal apps
The customer has an app device registered (visible on the customer's detail page)
Push has not been disabled in the customer's device settings
The send is inside the 9am-6pm sending window

Saved Service Account JSON Is Being Used Instead of the Automatic Key¶