Getting started

Jar not working: a calm checklist to find the cause

Jar not working? Work through app, phone, network and account causes in order, then check your bank statement so you know where your money really is.

Editorial illustration for Jar not working: a calm checklist to find the cause

If Jar is not working, start by finding out whether the problem is the app, your phone, your internet or your account. Most outages show up in one of those four places, and a two-minute test for each usually points to the answer. Before anything else, open your bank statement: it tells you whether any money actually moved.

Which kind of problem are you seeing?

The word broken covers very different faults. Match what you see to the row below and start there instead of trying everything at once.

What you seeMost likely areaFirst thing to try
App will not open or closes at onceApp or phoneForce close, restart the phone, check for an update
Spinner never endsNetworkSwitch between Wi-Fi and mobile data and retry
Login or verification failsAccount or SIMCheck the number is active and signal is steady
Balance looks wrongDisplay delay or a real transactionCompare with your bank statement
Only one feature failsService sideWait, then retry later in the day

The order to try fixes in

  1. Close the app completely and open it again.
  2. Restart the phone, which clears many half-stuck states.
  3. Install any pending update from your app store, since old versions often stop working after a service change.
  4. Test the same app on another network or another phone if you can borrow one. If it works there, the fault is on your device.
  5. Check storage: a phone with almost no free space can make apps freeze.
  6. Log out and back in only if you are sure you can complete the sign-in again.

Do not keep retrying a money action many times in a row. Each retry can create a separate attempt, and that is how people end up with doubles.

What if money left your bank but the app shows nothing?

Say you added ₹500 from your bank on the 14th, your bank shows the debit, and the app still shows ₹0. Treat the bank statement as the first record and the app as the second. Write down the date, the time, the amount and any reference number from your bank message.

  • Bank statement shows a debit of ₹500: the money left, so the app owes you a credit or an explanation.
  • Bank statement shows nothing: no debit happened, and the failed attempt is only a display issue.
  • Bank statement shows the debit and a later reversal: the attempt failed and the money came back.

In the first case, use the help or contact option inside the app and attach the reference. Read the company's own terms for how long a credit may take, because that differs from service to service and we cannot tell you the figure.

Should you reinstall the app?

Reinstalling is a late step, not an early one. Before you do it, check that you can log in again with the method you used originally, and that nothing in the app is stored only on this phone. If the app has a way to see or save your history, look at it first. If you are not sure, leave the reinstall for last.

Keep your own record while it is down

An outage is the perfect time to notice how much you depend on one app's screen as your only record. Whatever the app does, your spending still needs a home. You can add expenses by hand in SpendixAI, several at a time if you are catching up, and you can upload your bank or card statement later and review the rows before saving.

A short checklist before you contact support

  • The date and time the problem began.
  • The exact message or screen you saw, ideally a screenshot.
  • Amount, date and bank reference of any payment involved.
  • Your phone model and the app version.
  • What you already tried, in order.

A message that carries those five items gets a quicker, more useful answer than one that only says it is not working.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports