Repository navigation
Troubleshooting
- Is the delivery point set? The chip in the header says. Nothing runs without one.
- Are you signed in to Snapp Market? Its results need your session, and the search refuses to run without it. Digikala Jet appears either way.
- Is حداقل تخفیف set high? At 70% very little qualifies most days.
- Is فقط تخفیف کمپینی on in the search? With it on you only see today's campaign rather than the whole catalogue. It is off by default.
Almost always فقط تخفیف کمپینی. Jet marks very few rows شگفتانگیز, so with that filter on it contributes close to nothing. The status line under the results breaks the count down per platform, which makes this obvious.
That was a real bug, fixed in 1.0.1 and hardened since. Every 90-99% discount in the campaign feed belongs to the first-order shelf, which this app no longer reads at all. If you still see one:
- Look for ✓ قیمت از خود فروشگاه on the card. Search results carry it; feed rows do not, because confirming an endless list would cost a request per card.
- Check the size in the title — a 300ml can is not a 1.5-litre bottle.
- If neither explains it, that is worth an issue.
See Trust for the measurements.
The app holds its own refresh token, so this should be rare. It happens when the platform revokes a session. Sign out from حسابها and sign in again.
The browser extension this replaced had this constantly, because it could only borrow the website's token — which expires about an hour after it is minted, with no way to renew.
They are rate-limited on purpose: two minutes between codes, five per fifteen minutes, five attempts per code. The message says how long is left. If the platform itself pushes back, its wait is honoured rather than argued with.
Digikala Jet occasionally demands a captcha; the app says so, and signing in once
on digikalajet.com clears it.
Something changed shape upstream. Reload; if it persists, open an
"endpoint changed" issue
with the failing /api/... call from the network panel. Strip the
Authorization header before pasting anything — it is your account.
A PWA installs only from a secure context: HTTPS with a certificate the browser
trusts, or localhost for testing. On plain http://, or behind a CDN whose
certificate does not cover the domain, the service worker is refused and nothing
installs. تنظیمات → نصب برنامه says which case you are in and, on iPhone,
walks through Safari's «Add to Home Screen» — Safari has no install button of its
own for a site to call.
The installed app notices a new version the next time it comes to the front and
offers بارگذاری دوباره. If it never does, something in front of the app is
caching the HTML: the pages go out as no-store, and a CDN rule that caches them
anyway will keep serving a shell whose scripts the new deploy deleted. See
Behind a CDN in DEPLOY.md.
Expected. One request lists the nearby stores, then one per store reads its full campaign shelf — around 45 in central Tehran, six at a time — and then the leading results are each confirmed against their store. The feed is much cheaper, which is why it exists.
Independent open-source project · no affiliation with Snapp or Digikala · MIT