pretixSCAN on Android gives us troubles
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 5
- Forks
- 8
- Avg merge
- 12d 16h
- Merged PRs (30d)
- 4
Description
Hey Pretix-Team,
thanks for your great software! We're using the Community edition it to sell tickets for our music festival and generally it's a great experience :-).
But recently we updated to the latest version and I tried to use pretixSCAN instead of pretixdroid. The iOS version works without problems, but on Android the app cannot seem to load all data from the backend. Registering the device works, but during sync when trying to "Download orders" the process breaks and shows the message "Unknown server response". (There's a really quick message like "Processed 50 orders…" which is barely noticable in between.) The app then states "noch nie synchronisiert" and repeating the process leads to the same result. The backend shows the following log entry twice: WARNING 2019-08-23 12:50:30,755 django.request log Unauthorized: /api/v1/organizers/[event]/events/2019/orders/ – but I cannot seem to find any more detailed error explanation.
(pretixdroid still works nicely, so we can fallback to this for now.)
We're running the latest pretix and pretixSCAN on Android.
Is this a bug? Do you have any suggestion of how I could further debug this issue?
Best and thanks,
Benjamin.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Android synchronization flow for the “Download orders” action in libpretixsync and reproduce the failure against the orders endpoint /api/v1/organizers/[event]/events/2019/orders/. Compare the sync response with the backend’s Unauthorized log entry; done means the Android app completes synchronization and no longer reports “Unknown server response”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, django, kotlin
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100