Help 8 min
Error messages, decoded
Every red message Uruvak can put in front of you, quoted exactly, with what it really means and what to do next.
When you finish this page
You can look up the exact wording of any error Uruvak showed you, and know what to do about it.
Every message below is quoted word for word from the product, so you can search this page for the sentence in front of you. Where a message contains a number or a name — a store count, a package name, an image size — the example uses realistic values and the text says which part changes. The messages are grouped by where they appear.
Signing in and creating an account#
These appear in red inside the form on app.uruvak.com.
| Message | What it means | What to do |
|---|---|---|
| “Passwords don't match” | The two password boxes on the Create account form differ. Nothing was sent to Uruvak. | Retype both. The second box turns red the moment it stops matching. |
| “An account with that email already exists” | That address already has a Uruvak account. | Switch to the Sign in tab. If the password is gone, use “Sign in with an email code instead”. |
| “Invalid email or password” | The address and password don't match an account. | Try again, or sign in with an email code. There is no password reset. |
| “This account signs in with Google or an email code” | The account has no password — it was created through Google, or only ever used codes. | Use “Continue with Google”, or “Sign in with an email code instead”. |
| “No Uruvak account uses that email” | You asked for a sign-in code for an address that has no account. | Check the spelling. If it is right, you need Create account instead. |
| “That code is invalid or has expired” | The 6-digit code is wrong, more than 10 minutes old, already used, or you have mistyped it five times. | Press “Resend code” and use the newest email. Each new code cancels the one before it. |
| “Please wait 47s before requesting another code.” | You asked for a second code within 60 seconds of the first. The number counts down. | Wait for it to reach zero, then press “Resend code”. |
| “Too many codes requested. Please try again later.” | Five codes were sent to that address within one hour. | Wait an hour, or sign in with your password instead. |
| “Validation failed” | Something in the form failed a format check — a 5-digit code, or a password under 8 characters. | Codes are exactly 6 digits; passwords are at least 8 characters. |
| “Could not verify the Google sign-in token” | Google's answer was not accepted, usually because the browser sat on the page too long. | Reload the page and press the Google button again, or use an email code. |
| “Google sign-in is not configured” | Google sign-in is switched off on Uruvak's side. | Sign in with a password or an email code, and tell us at support@uruvak.com. |
| “Could not send a code”, “Could not sign in”, “Could not create account”, “Google sign-in failed” | Your browser could not reach Uruvak's servers at all. | Check your connection and try again. |
Connecting your store#
In WordPress, on the Uruvak Bridge screen#
Every failure here starts with the same red line, “Could not connect.” The sentence after it is the real reason.
| Message | What it means | What to do |
|---|---|---|
| “Could not connect. Connection state mismatch — please try again.” | The connect was started twice — two tabs, a browser Back button, or a reloaded page. Only the newest attempt counts. | Close the extra tabs and click “Connect with Uruvak →” once, then finish without going back. |
| “Could not connect. Invalid or expired connect code” | More than five minutes passed between approving in Uruvak and landing back in WordPress. | Click “Connect with Uruvak →” again and approve straight away. |
| “Could not connect. Store not found” | The store you approved no longer exists in your Uruvak account. | Start again from wp-admin. If it repeats, email support@uruvak.com. |
| “Connect failed (HTTP 502)” | WordPress reached Uruvak but got an error back. The number varies. | Wait a minute and try again. |
| “Could not connect.” followed by a WordPress connection error — a timed-out request or a name-lookup failure | Your WordPress server cannot make outgoing calls to api.uruvak.com. | Ask your host to allow the site to make outgoing requests to api.uruvak.com, and to check whether a firewall or a security plugin is blocking them. |
| “Could not connect. Check the key and try again.” | The attempt failed and Uruvak sent nothing to explain it. | Try once more, then send us the time it happened. |
| “Forbidden” | You are signed into WordPress as someone who is not an administrator. | Sign in as an administrator. Only administrators can see or use this screen. |
| “A connect code is required”, “A connect token is required” | An empty key box was submitted. | Do not use the key boxes at all — see the note below. Use “Connect with Uruvak →”. |
On the approval screen at app.uruvak.com#
| Message | What it means | What to do |
|---|---|---|
| “Store limit reached (1/1). Upgrade your plan to add more stores.” | Your plan's stores are all in use. The numbers are your real counts. | Archive a store on the Billing page, or upgrade. See Plans and limits. |
| “Validation failed” | The web address WordPress reported for the shop is not a valid address. | In WordPress, check Settings → General — the Site Address must be a full address starting with https://. |
| “No store provided”, “Open this page from the “Connect with Uruvak” button in your store's wp-admin.” | You opened app.uruvak.com/connect directly. Connecting always starts in WordPress. | Go to wp-admin → Uruvak Bridge and press the button there. |
| “Could not connect this store” | Your browser could not reach Uruvak while approving. | Reload and approve again. |
“Signing key missing”#
If the Signing key (HMAC) row on the Uruvak Bridge screen reads “not set — re-link below to enable Save & Publish”, a card appears saying “This store is linked but has no HMAC signing key, so Save & Publish is blocked. Generate a connect key in the Builder and paste it here to repair the link.” Your store is half connected: Uruvak knows about it, but has no shared secret to write to it, so publishing fails.
Messages your store sends back to Uruvak#
You rarely see these in full. They are what makes the Studio show a grey Not connected chip, and what makes a publish fail.
| Message | What it means | What to do |
|---|---|---|
| “Store is not connected.” | The plugin has no key stored — the store was disconnected, or the key is missing. | Reconnect from wp-admin → Uruvak Bridge. |
| “Invalid request signature.” | Your store and Uruvak hold different keys, usually after a half-finished reconnect. | Press Disconnect, then Connect with Uruvak → again. |
| “The request signature has expired.” | Your server's clock is more than five minutes away from real time. | Ask your host to correct the server time. Nothing on the Uruvak side can work around it. |
| “A request signature is required.” | Something stripped the security headers off the request — a security plugin, a proxy, or a caching layer. | Exclude /wp-json/ from your cache and your security plugin. |
| “WooCommerce is not active” | The Uruvak Bridge plugin is active but WooCommerce is not, so there is no catalog to serve. | Activate WooCommerce. The app shows no products until you do. |
| “Missing or invalid token” | A shopper's sign-in inside the app has expired. | They sign in again on the Account tab. This also happens to everyone at once if you rotate your WordPress security keys. |
More on all of these in When the connection breaks.
Publishing#
These appear in the Studio, in a red banner under the top bar.
| Message | What it means | What to do |
|---|---|---|
| “Take your first app release to unlock Live Publish.” | Publish Live stays greyed out until one Android release has finished. | Take a release — see Take a release. The first one also freezes your current draft as what is live. |
| “You've used your 5 free Live Publishes. Your app keeps running exactly as last published — upgrade to keep updating it.” | The Free plan includes five Live Publishes for the lifetime of the account, not five a month. | Upgrade on the Billing page. Your app keeps working meanwhile. |
| “This store is over your plan's limit (Free includes 1 store). Resubscribe or archive another store to edit it.” | You have more stores than your plan allows, so the newest ones are Locked. The plan name and number are yours. | Archive a store on the Billing page, or upgrade. Locked stores keep running; they just cannot be published or released. |
| “Your subscription is inactive — a payment may have failed. Update billing to continue.” | The card on file failed, or the plan was canceled. | Open Billing and press “Manage billing” to fix the card. |
| “Could not publish to the store: Cannot publish: store is not connected (no API key)” | Uruvak has no key for your shop. | Reconnect from wp-admin → Uruvak Bridge, then publish again. |
| “Could not publish to the store: WP publish rejected: HTTP 403 from https://nordviksupply.com” | Your shop answered, but refused the write. The number and the address are yours. A 403 usually means a security plugin or firewall is blocking /wp-json/. | Exclude /wp-json/ from the blocking plugin, then publish again. |
| “Could not publish.” | The request never reached Uruvak. | Check your connection and press Publish Live again. |
| “Could not undo the publish.” | The rollback failed. The live app is unchanged. | Try Undo again from the same toast. Once the toast is gone, Undo is gone with it. |
| “Draft not saved — retrying on your next change” | The Studio's autosave could not reach Uruvak. Your last edit is only in the browser. | Keep the tab open, check your connection, and make one more small edit to trigger a retry. Do not close the tab until it reads “Draft saved”. |
A failed publish never costs one of your five free publishes — the count only moves after the change actually reaches your shop. Undo is always free too. See Publish live.
Releases, the app icon and the package name#
These appear on Settings › Releases and Settings › General.
| Message | What it means | What to do |
|---|---|---|
| “Nothing changed that needs a release. Publish live instead — it's instant.” | Nothing baked into the installed app has changed, so a new file would be identical. | Use Publish Live. Only the app name, app icon, package name, the Firebase file and the Google Sign-In iOS client id need a release. |
| “A android build for this app is already building. Wait for it to finish.” | One release at a time per app. The odd grammar is ours, and the word may read “queued” instead of “building”. | Wait. The list refreshes itself every few seconds while a build is running. |
| “The free plan includes everything you need to launch — you've used your included releases. Upgrade to keep releasing.” | The Free plan allows your first release plus a handful of rebuilds. No number is shown anywhere; the only warning is the line “Heads up — this is your last included release on the free plan.” in the confirmation box. | Upgrade to keep rebuilding. Everything already built stays downloadable. |
| “Couldn't start the release.” | The request did not reach Uruvak. | Press “Release Android app (APK)” again. |
| “Use a PNG or JPEG image.” | The icon file is another format — often a PDF, an SVG or a HEIC photo from a phone. | Export it as PNG. |
| “The icon must be square — this image is 1024×768.” | The icon has to be a perfect square. The size shown is your file's. | Crop it square before uploading. |
| “Needs at least 1024×1024 (App Store size) — this image is 512×512.” | Your icon is too small. | Upload a bigger version. The same problem worded by our servers reads “The icon must be at least 1024×1024 (App Store requirement) — this image is 512×512.” |
| “Couldn't read that image — try another file.” | The file is damaged, or is not really an image. | Open it, re-export it, and upload it again. |
| “Already used by another app” | The package name you typed belongs to someone else's app. It appears next to a ✕ under the field. | Pick another. It is permanent, so choose carefully. |
| “2–50 letters/numbers, starting with a letter” | The ending you typed is not a valid one. Our servers word the same rule as “Use 2–50 letters/numbers, starting with a letter (e.g. mystore).” | Use plain letters and numbers, no spaces, no dots, no dashes. |
| “"com.uruvak.nordvik" is already taken by another app.” | The full package name is taken. The name shown is the one you tried. | Pick another ending. |
| “The package name is locked — it can't change after the first build.” | Once any release exists, the package name is frozen forever — even a queued or failed one freezes it. | It cannot be changed. If you truly need a different one, you need a new store in Uruvak. Set the package name before your first release: App name, icon and package name. |
A release stuck on “Queued”, or “Failed” with nothing else#
Uruvak does not show you why a build failed — the row just turns red and offers ↻ Retry, which starts a completely new build rather than resuming the old one. Two things are worth knowing:
- A build that says Queued is waiting for a free build machine. There is no message when they are all busy, so a queue that lasts more than about half an hour usually means something is wrong on our side, not yours.
- A build that sticks on Building is marked Failed automatically after about 30 minutes, with no email and no explanation.
Press ↻ Retry once. If the second attempt fails as well, email support@uruvak.com with your store name and roughly when you started it — we can read the build log, and you cannot.
Push notification setup#
All of these appear in Settings › Notifications while you are uploading the two Firebase files. See Push notifications for the whole setup.
| Message | What it means | What to do |
|---|---|---|
| “That file is too large to be a google-services.json — pick the file downloaded from Firebase.” | The file is over 20,000 bytes, so it is not the one Firebase produces. | Download it again from Firebase, Project settings → Your apps → google-services.json. |
| “That doesn't look like a google-services.json — it has no Android client entries.” | The file has no Android app inside it. | In Firebase, add an Android app to the project first, then download the file again. |
| “This file has no client for this app's package name (com.uruvak.nordvik) — it covers com.example.other. In the Firebase console, add an Android app with the package name com.uruvak.nordvik, then download google-services.json again.” | The Firebase project has Android apps, but none with your package name. Both names shown are real. | Do exactly what the message says: add an Android app in Firebase with that package name, download the file again, upload it again. |
| “That file is too large to be a service-account key — pick the .json Firebase generated.” | The key file is over 16,000 bytes. | Generate a new key: Project settings → Service accounts → Generate new private key. |
| “That file isn't valid JSON — pick the key file Firebase generated.” | The file is damaged, or it is the wrong file. | Generate a new key and upload the file exactly as downloaded — do not open and re-save it. |
| “That's not a service-account key. In the Firebase console go to Project settings → Service accounts → Generate new private key.” | The file is valid but is not a service-account key — usually google-services.json uploaded into the wrong box. | Follow the path in the message. |
| “This key belongs to Firebase project "nordvik-push", but your google-services.json is from "nordvik-shop". Generate the key in that same project (Project settings → Service accounts).” | Your two files come from two different Firebase projects. The names shown are yours. | Generate the key inside the project the first file came from. Upload google-services.json first — the check only runs in that order. |
| “This file doesn't cover the current package name (com.uruvak.nordvik) — builds will skip push until you upload a matching one.” | You changed the package name after uploading the Firebase file, so it no longer matches. | Add an Android app with the new package name in Firebase, download the file again, upload it, and take a new release. Until then, new releases ship with push switched off and nothing says so afterwards. |
| “Couldn't save — try again.”, “Couldn't remove — try again.”, “Couldn't send — try again.” | The request did not reach Uruvak. | Try again. |
| “No categories found. Connect your store to load its catalog.”, “No products found. Connect your store to load its catalog.” | The notification's “opens on tap” picker could not read your catalog, because the store is not connected. | Fix the connection first. Until a category or product is picked, the Send button stays dead. |
| “Sent — but no devices are registered yet. Notifications reach devices once the app (with push support) is installed and opened.” | Not an error. The send worked and reached nobody, because no phone has the app with push in it yet. | Take a release after uploading the Firebase files, install that build, open it once, then send again. |
Plans and billing#
These appear on the Billing page.
| Message | What it means | What to do |
|---|---|---|
| “Your payment failed.” followed by “Update your card to keep your plan — paid actions (builds, publishing, campaigns) are paused until it's resolved.” | A charge was declined. In practice only Live Publish is actually stopped — releases still run — and there is no campaigns feature in Uruvak today. | Press “Manage billing” and update the card. |
| “Launch includes 1 store. You have 3 — archive or remove 2 to switch.” | You are moving to a plan with fewer stores than you have. All three numbers are yours. | Archive the extra stores on this page first, then switch. |
| “Store limit reached (1/1). Upgrade your plan to add more stores.” | You tried to restore an archived store, or connect a new one, with no room on the plan. | Archive a different store, or upgrade. |
| “Billing is not configured yet — please try again later.”, “Billing is not configured yet.” | Payments are temporarily unavailable on our side. Nothing was charged. | Try again later, and tell us at support@uruvak.com if it lasts. The Free plan keeps working. |
| “No billing account yet — choose a paid plan first.” | “Manage billing” only exists once you have had a paid plan. | Pick a plan on this page first. |
| “Could not change plan.”, “Could not update the store.” | The request did not reach Uruvak. | Reload the Billing page and check what it says before trying again — the change may already have gone through. |
The Analytics tab#
| Message | What it means | What to do |
|---|---|---|
| “Analytics isn't set up yet” | Analytics is not switched on for your account yet. | Email support@uruvak.com. |
| “Waiting for the first events” | Analytics is on, but no one has opened your app yet. | Install a release and open it. Numbers appear within a few minutes. |
| “Couldn't load analytics” | The numbers could not be fetched. | Reload the page. |
When the message is about us, not you#
| Message | What it means | What to do |
|---|---|---|
| “Couldn't reach the API. Is the backend on :3055?” | Developer wording that escaped onto the dashboard home page. It means the dashboard could not reach Uruvak's servers. | Reload. If it persists for more than a few minutes, email support@uruvak.com. |
| “Failed to fetch”, “Load failed”, “NetworkError when attempting to fetch resource.” | Your browser's own words for a lost connection. Which one you see depends on the browser. | Check your internet connection and reload. |
| “Internal server error”, “API 500” | Something broke on our side. Nothing you did caused it and nothing was charged. | Try once more, then email support@uruvak.com with the time and the page. |
| “Missing session token”, “Invalid or expired session”, “Account not found” | Your sign-in has expired or been invalidated. | You will be returned to the sign-in page. Sign in again; your work is saved. |
| “Sign in required” | The same thing, from a page that could not send your sign-in with the request. | Sign in again. |
| A page that sits on “Loading…” and never changes | The dashboard is waiting for an answer that is not coming. | Reload the page once. If it happens twice, it is ours to fix — email support@uruvak.com. |
If the message you are looking at is not on this page, send it to support@uruvak.com exactly as written, with the name of the screen you were on. The wording is how we find the cause. For the questions that come up when nothing is broken, read Questions we get asked.