Callbook docs
v1.0.0
Get help
● Ship

Troubleshooting
common problems and fixes.

Cases taken from the code, with what to check.

pricesco-signingpurchasesserverbuild

01Stocks and ETFs do not appear in the app

The Twelve Data provider is off or has no key. Console, Price providers: save your key, press Test, switch Twelve Data on. Also check that "Stocks and ETFs" is on under App config: features. The public demo has Twelve Data switched off on purpose, so it shows crypto only.

02A stock call stays open, or the console says the rate limit is used up

Your Twelve Data plan has a limit of requests per minute and per day. Lower the per-minute number in the console to match the plan, or choose a larger plan. Candles that were already fetched stay cached, so only new ranges are affected. Closed days are kept; recent days are refreshed about every 6 hours.

03Prices fail with provider_failed or provider_disabled

provider_disabled: that provider is switched off in the console. provider_failed: it could not be reached or refused the request, for example a wrong key or an unknown ticker; the Reference column under Supported assets must be the provider's own name (BTCUSDT, bitcoin, AAPL). Use Test on the provider page.

04Receipts say 'Sealed on this device only'

No signing key is saved (the server answers 501 cosign_off), the server cannot be reached, or the app was built without API_BASE_URL. Save a key under Signing (Signing), check the address, and note that receipts sealed before that stay local unless the app sends them again.

05'Co-signature does not check out'

The signing key was replaced after the receipt was signed, or the record does not match the receipt. Keep the old key if you must replace it.

06Settings says the chain is broken

Some stored receipt was changed or removed outside the app (for example the database file was edited). The message names the first receipt that fails. The app does not repair a chain.

07The paywall says purchases are not set up

No product id is set for this platform. Fill the ids in brand.dart or the console (Where to put the ids). Ids must match App Store Connect and Play Console exactly.

08Products are set but the store answers with nothing

iOS: the Paid Apps agreement and tax forms must be complete and the product ready to submit. Android: the app must be installed from a Play test track (not a sideloaded APK) by a licence tester, and the product and base plan must be active. Wait some hours after creating products.

09Purchase verification answers 501

501 verification_off means verification is not switched on in the console, so the app trusts the on-device result. Turn it on under Purchases and fill in the credentials.

10Google Play verification fails with a permission error

The service account must be invited in Play Console with View app information and View financial data, and the Android Publisher API must be enabled in the Google Cloud project. New permissions can take some time to apply.

11App Store lookup fails

Check the bundle id, Key ID, Issuer ID, and that the .p8 text was pasted whole including its BEGIN and END lines. The server tries Production, then Sandbox.

12I cannot find the console setup code

It is printed in the server log at start when ADMIN_SETUP_TOKEN is empty. In Docker run docker logs. Or set ADMIN_SETUP_TOKEN in .env and restart.

13npm ci fails or better-sqlite3 will not load

Use Node 22.12 or newer (node -v). better-sqlite3 is a native module: if no prebuilt file exists for your system, you need build tools (Python 3, make, a C++ compiler). Delete node_modules and run npm ci again after changing Node versions.

14429 errors, or everyone shares one address

/v1 routes allow 60 requests a minute per address. Behind a proxy set TRUST_PROXY_HOPS=1, otherwise all users look like the proxy's address.

15A console change does not appear in the app

The config is cached for 5 minutes and by ETag. Wait, then reopen the app. Check the app was built with API_BASE_URL and that the address is https and reachable from the phone.

16Play rejects the upload or says the app is debug-signed

As shipped, release builds use the debug key. Add your own signing config (Release).

17Xcode says signing failed or the bundle id is not available

The project ships with no team set. Choose your own team and a bundle id you own (Rename).

18iOS build fails on a pod deployment target

The Podfile platform is 16.0. Keep it at 16.0 or higher, then run pod install again.