Updating the taxi app: what it does by itself, and what needs the store

Does the app update itself?
Most of it does, and this is the part nobody is told: when you open the app it asks our site for the newest copy of its screens, downloads it quietly in the background, and puts it in place the next time you open the app.
- You open the appIt asks our site for the newest copy of the screens
- It downloads quietlyNothing is interrupted, nothing is asked
- You open it againThe new copy is in place
- If it will not startIt goes back to the one that worked
The app installed from a store carries a frozen copy of the screens, so without this it could be running code much older than our website. Instead, every time we publish the website we also publish that copy for the app to collect. It then waits. The swap happens at the app’s next start and never in the middle of what you are doing, so a change you collect on one opening is in place the next time you open the app.
Three safety measures sit around it, and they matter more than they sound. The app marks the copy it has just started as good, so a copy that cannot start is dropped and the last one that worked comes back — you are never left with a dead screen. A real update from the store always wins: installing one clears the collected copies, so nothing older is ever stitched over something newer. And a download that fails leaves you exactly where you were, on the copy that works.
Two honest limits. The collected copy is the screens only — the videos, the large pictures and several whole folders that belong to the website rather than to the app stay out of it deliberately, so the download is small, and they load from the website when they are needed. And a version that fails to download is not fetched again: the app waits for the next one newer still. So a store update is sometimes the only way to catch up, which is what the rest of this page is about.
Which update messages can the app show you?
Four, and the only thing you really need to know is that the first is a request and the other three stop you where you are.
| What you see | What it means | Can you carry on? |
|---|---|---|
| A yellow bar across the top: “A newer version of the app is available.” with an Update button and a cross | A request. There is a newer version in the store than the one in your hands | Yes. Book a taxi as normal, or close the bar with the cross |
| A card over the whole screen: “Update required” and under it “This version of the app is no longer supported. Please update to continue.” | A requirement. The version you are running is below the oldest one we still serve | Not in the app. Update in the store, or book on our website |
| At the sign-in screen, before any code is sent: “Please update the Hello Taxi app to the newest version” | The same requirement, met earlier: no code is sent at all, so none is on its way | Not in the app. The same two ways on |
| After you type the code: “App update required — update Hello Taxi in the store” | Your code was accepted, but the sign-in could not be completed | Not from here. In the app: sign in on our website with the same number. In a browser: load the site again and type your number afresh |
The first three exist only in the app you installed from a store: the bar and the card both check whether they are running inside an app before they draw anything, and our server lets a browser straight through. The website you load is the current version by definition, so it is never turned away for being out of date — which is why it is the answer at the foot of this page. The fourth message is different: it is raised when the app cannot open a signed-in session after a correct code, so it can appear in a browser too, and it is worded for the commonest cause, an app too old to finish the job. Do you need the app at all? sets out the difference between the two ways in.
What is the yellow bar at the top of the screen?
A request, not a demand. The bar reads “A newer version of the app is available.” and carries an Update button and a cross to close it.
When the app starts it asks our server whether the version in your hands is behind the current one, and draws the bar if it is. It stops nothing: you can book a taxi, watch the car coming and pay with the bar still sitting there. It does sit over the top strip of the app while it is up, so the menu button — and the back arrow, on the screens that have one — are behind it until you close it with the cross, which is the one practical reason to close it rather than leave it.
Closing it is remembered against that version. You will not meet the same bar at every launch: the app stores the version you closed it on and does not raise it again until a newer one comes out. The one catch is that the remembering needs a second word with our server at the moment you tap the cross, so if that does not get through, the bar can come back next time.
The Update button opens our page in the store your telephone uses — Apple’s on an iPhone, Google’s on an Android telephone — and the update itself happens there.
And the card that says āUpdate requiredā?
That one is a requirement. It reads “This version of the app is no longer supported. Please update to continue.” and carries a single button to the store, with no cross.
If you ever meet it, it means the version you are running is below the oldest one we still serve. It covers the whole screen and is drawn over the app’s own screens, so no part of the app can hide it, and it carries no way to dismiss it on purpose — a rider who closed it would be left tapping a Book button that cannot work. It leaves two ways on: update in the store, or open hellotaxi.co.il in your telephone’s browser and book there with the same telephone number and the same account.
It is worth saying what it does not mean. It is not a problem with your account, your card or your rides — all of those are held on our side and are waiting for you whichever way you come back in. Your details in the app covers what the account itself holds. And if anyone ever asks which version you have, tap the menu button at the top right of the app and read the last line of the menu: “Hello Taxi · build” and a number.
Can an old version stop you signing in?
Yes, and at either of two moments — before the code is sent, or after you have typed it.
At the first step, where you type your telephone number, a version too old to be served is turned away before any code goes out, with the words “Please update the Hello Taxi app to the newest version”. Nothing is sent, so there is no point waiting for a message that is not coming. At the second step, a correct code can still fail to become a signed-in session, and the app then says “App update required — update Hello Taxi in the store”. Both messages carry Hebrew and English together on purpose: they are written out in full rather than looked up, so they read the same whichever language the app is set to.
The first of those two can only happen in the app from a store — a browser is never turned away for being out of date. The second is about finishing the sign-in rather than about the store, so it can appear in a browser as well; if it does, close the page, open hellotaxi.co.il again and type your number afresh. Either way the code itself behaves as it does anywhere else, and signing in to the app explains it, including what happens when your telephone number is not an Israeli one.
You need a taxi now and the app is blocked. What then?
Do not stand in the store queue with a case in your hand: book the ride first, by one of the three doors that need no app at all, and update afterwards.
Our website, hellotaxi.co.il, is the same service in your telephone’s browser — the same account, the same telephone number, the same rides — and it is never out of date. For a ride where every minute counts, the telephone line on 02-376-7000 takes a booking from any telephone at all, a kosher one with no internet included. The WhatsApp assistant on +972 53-900-0023 takes an ordinary ride in town, and a long trip between towns or a large car for a time you name. For a ride at a set hour, the telephone line and our website are the two doors to lean on. Booking by telephone describes the call, and if this happens on your way to or from the airport, the Haifa airport run is written around those same doors.
Then update when you are sitting down rather than standing at the roadside. It changes nothing about your account: your name, your saved cards and your past rides are held on our side, which is why the website knows you the moment you sign in with the same number. Afterwards, open the app once and check that alerts about your ride still reach you — what the app sends you lists what each alert is for.
A notice is covering the whole screen ā is that an update?
Not necessarily. The full-screen notice that has nothing to do with updating is the one that says we are closed for Shabbat or a festival.
Hello Taxi stops from candle-lighting on Friday until Shabbat goes out on Saturday night, and on every holy day of rest — both days of Rosh Hashana, Yom Kippur, the first day of Sukkot, Shemini Atzeret and Simchat Torah, the first and the seventh day of Passover, and Shavuot — each from candle-lighting until nightfall. The middle days of Sukkot and Passover are ordinary working days. During a closure the app lays a notice over every screen a rider can open, in Hebrew with English beneath it, saying that we are closed — for Shabbat, for a festival, or for both — and the hour we reopen. Like the update card it cannot be dismissed, and for the same reason: closing it would leave somebody believing a taxi was on the way. Unlike the update card it clears itself, within half a minute of the closure ending, so there is nothing to reinstall and nothing to update. It also sits above the update card, so during a closure it is the notice you will see.
The quick way to tell them apart is the words. An update notice talks about a version and offers a button to a store; the closure notice talks about Shabbat or a festival and gives the hour we are back. Neither is a fault, and neither is fixed by deleting the app.
The bottom line
Most of what we change reaches the app without the store: when you open it, the app asks our site for the newest copy of its screens, collects it in the background and puts it in place the next time you open the app ā which is why a change often appears the following time you open it. If a collected copy cannot start, the app falls back to the last one that worked; a real store update always replaces the collected ones; and the videos, the large pictures and several whole folders that belong to the website rather than to the app are deliberately left out of the download and load from the website instead. A version that fails to download is not fetched again, so the store is sometimes the only way to catch up. When the store is needed, the app has three messages and the first is nothing like the other two. The yellow bar saying a newer version is available is a request: it stops nothing, though it does sit over the appās top strip until you close it with the cross, and closing it is remembered until a newer version comes out. The card that covers the screen, saying this version is no longer supported, is a requirement with one button and no cross, and the refusal at the sign-in screen is the same requirement met before any code is sent. Each leaves two ways on: update in the store, or book on our website with the same telephone number. A fourth message, āApp update requiredā, is raised when the app cannot open a signed-in session after a correct code ā that one can appear in a browser as well, and the answer there is to open the site again and type your number afresh. The first three can only appear in the installed app, never in a browser: the website is current every time you load it, so it is never turned away for being old. If you are blocked and need a taxi now, book first and update afterwards: the website is the same service with the same account, the telephone line on 02-376-7000 takes a booking from any telephone at all, a kosher one with no internet included, and WhatsApp on +972 53-900-0023 takes an ordinary ride in town, or a long trip between towns for a time you name. And if a notice is covering the screen that names Shabbat or a festival and an hour rather than a version, that is not an update at all: we are closed, and it clears itself.
Frequently asked questions
Does the Hello Taxi app update itself?
Do you have to update the app when it asks?
What does āThis version of the app is no longer supportedā mean?
Why will the app not send a sign-in code?
Where can you see which version of the app you have?
The app is showing a notice I cannot close. Is it broken?
Sources
- A check in our own code, 15 November 2026, of the update messages. There are four. The first is a yellow bar at the top of the screen reading "A newer version of the app is available." with an Update button and a cross; it is asked of our server when the app opens, blocks nothing, and sits over the appās own top strip until it is closed. Dismissing it is remembered against the version dismissed, so a newer version shows it again ā but the remembering itself needs a second word with the server at the moment of closing, and if that does not get through the bar can come back. The second is a card covering the whole screen: "Update required", and under it "This version of the app is no longer supported. Please update to continue.", with one button to the store and no way to dismiss it. It is drawn over the appās own screens, though the Shabbat and festival closure notice sits above it. The third is at the sign-in screen before the code is sent: a version below the minimum is refused in Hebrew and English together and no code goes out at all. The fourth is a failure to finish signing in after a correct code, also in both languages. The first three belong to the installed app only, never to a browser: the first two sit behind a check that returns false in a browser, and the server explicitly exempts the browser, which always runs the live version. The fourth is behind no such check and can appear in a browser too. Both sign-in messages carry the two languages because they are written out in full rather than looked up in the translation table. The Update button opens our page in Appleās store on an iPhone and Googleās on an Android handset. The first three messages depend on a setting kept in Cloudflare rather than in this repository, so the page never says a rider will meet them ā only what each means and what to do. The version number is visible to a rider: at the foot of the menu that opens from the name, the app prints "Hello Taxi Ā· build" and a number.
- A check in our own code, 15 November 2026, of the update that arrives without the store. The app carries a frozen copy of the screens, so on opening it asks the live site what the newest copy is and, if there is one newer than its own, downloads it in the background. The swap happens at the appās next start and never in the middle of what the rider is doing. The copy is built on every build of the website and served from our own site. Three safety layers: the copy the app started in is marked good, so a new copy that fails to start is rolled back by itself to the last good one; a fresh install from the store discards the quiet copies, so a real store update always wins; and a download that fails does not touch the running copy. But the version that failed was already marked as tried before the download began, so it is not fetched again ā the app waits for one newer than it, and the comment in the code saying it is retried at the next launch is wrong. The copy is code only: videos, large pictures and whole website-only folders ā the Hebrew guides, the telephone lineās recordings and the posters ā are left out on purpose and load from the website instead. The English guides are inside the copy. All of it is switched off in a browser, and it exists only from the first store build that carried the machinery onwards.
- A check in our own code, 15 November 2026, of the Shabbat and festival closing as a rider meets it. The notice is laid over every screen a rider can open, in Hebrew with English beneath it, and says what we are closed for and when we are back. There is no way at all to dismiss it: the comment in the code says that dismissing it would leave somebody tapping "Book" against a service that cannot answer. It re-checks itself every thirty seconds and clears itself without anyone having to close and reopen the app. The only screen not covered is the driverās own ride screen, so that no passenger is left mid-journey.
- The facts checked on 16 and 17 September 2026 and kept on file here, the part these pages rest on: that the meter sets the final amount and the driver enters it at the end of the ride; that in the app the rider sees the available drivers, each with a star rating, the kind of car and one estimated price ā on the driver list the booking page opens, that is one figure rather than a range, and carries no licence plate, both checked again in the code today; the older booking screenās own list still shows a range, and the plate reaches the rider with the driver, on the tracking screen; that a ride is booked in the app, on WhatsApp on 053-900-0023 or on the telephone line 02-376-7000 from any telephone, a kosher one with no internet included; that only approved drivers are listed; that payment is cash to the driver or by card in the app; that a lawyer has not yet confirmed how a price set by the driver sits with the rule that an agreed price may not exceed the meter; and that the service is closed on Shabbat from candle-lighting until Shabbat goes out and on every holy day of rest ā both days of Rosh Hashana, Yom Kippur, the first day of Sukkot, Shemini Atzeret and Simchat Torah, the first and the seventh day of Passover, and Shavuot ā with the middle days of Sukkot and Passover open.