new nectar cards can't be added immediately #11

Open
opened 2026-04-25 12:16:39 -04:00 by plate · 6 comments
Owner

before adding a freshly registered card to pollen, it must be used with smartshop normally. how to reproduce this:

  1. register an account
  2. try to add it to pollen, 401 and error 6017
  3. log into nectar app and retry, still fails
  4. log in with barcode (not aztec/qr) using a handset and retry, success
before adding a freshly registered card to pollen, it must be used with smartshop normally. how to reproduce this: 1. register an account 2. try to add it to pollen, 401 and error 6017 3. log into nectar app and retry, still fails 4. log in with barcode (not aztec/qr) using a handset and retry, success
Author
Owner

i suspect i'm just not calling the guest registration endpoint before trying to login. i'll take another look at things later

i suspect i'm just not calling the guest registration endpoint before trying to login. i'll take another look at things later
Author
Owner

this is the endpoint called before logging in with nectar

from libssa.client import Client
c = Client()
c.post(f"{c.base_url}/identity/api/v2/users", use_auth="basic", headers={"X-Guest-Account":"true"}, json={"nectar_card":"xxxx"})

<Response [503]>

it's actually just dead

this is the endpoint called before logging in with nectar ```python from libssa.client import Client c = Client() c.post(f"{c.base_url}/identity/api/v2/users", use_auth="basic", headers={"X-Guest-Account":"true"}, json={"nectar_card":"xxxx"}) <Response [503]> ``` it's actually just dead
Author
Owner

but the app's own logic says: if you get 6017, register as a guest with nectar

but the app's own logic says: if you get 6017, register as a guest with nectar
Author
Owner

i'll try doing it in store then see

i'll try doing it in store then see
Author
Owner

same 503 responses for guest reg (they have all been an empty json object by the way). activation via handset works just as described

same 503 responses for guest reg (they have all been an empty json object by the way). activation via handset works just as described
Author
Owner

next step is to try to match a handset request fully, then remove headers until it stops working

next step is to try to match a handset request fully, then remove headers until it stops working
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
plate/pollen#11
No description provided.