View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007451 | Taler | merchant-pos-terminal (Android App) | public | 2022-11-13 17:07 | 2023-01-26 21:53 |
| Reporter | Christian Grothoff | Assigned To | grote | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.9.1 | Fixed in Version | 0.9.1 | ||
| Summary | 0007451: PoS app does not work 'out of the box' | ||||
| Description | The app has a hard-coded link to a configuration resource which right now 404s. Not sure why it's gone (or where it went, for that matter), but we should modify something (web page or the App) so that when the user uses the 'default' configuration link, it works with some kind of simplistic shop content (as it used to, years ago...). | ||||
| Tags | No tags attached. | ||||
| What are the configuration URL and format? | |
| modify the demo/sandbox setup to ensure that the backend instance in the Android Point-of-Sale app exists? The file is https://docs.taler.net/_static/sample-pos-config.json and it requires an instance 'pos' with api_key 'secret-token:sandbox'. | |
| 'pos' instance added on demo. | |
| https://docs.taler.net/_static/sample-pos-config.json is correct now, as far as I can tell. I checked with the Kotlin code, and all fields seem to be fine. jq also thinks it is well-formed JSON, and the server returns the correct Mime-type. However, the POS app tells me "Error: The configuration JSON is malformed". :-( Torsten, any ideas? (Might be good to show the position of the syntax error if the JSON failed to parse, and/or to give details about the broken/malformed field/path if the issue is deeper down in the configuration...). Syntax issues might need to be debugged by people other than us in the future, so good error messages here would seem important ;-). | |
| When using this now with current POS app, it actually tells me App too old, please upgrade! I am getting version=3:0:1 while the POS app is at 1:0:0 | |
| When simply bumping the version, I do get that malformed error when trying to pay something. The hint is about the `refund_delay`, so I guess more than just authentication has changed in the last 2 versions. Is there an overview over all changes somewhere? Also strange, that there's no authentication error. I thought this had changed? | |
| There was a change in the encoding of time (absolute and relative). That is most likely the problem. See: https://docs.taler.net/core/api-common.html#timestamps As for the authentication change, if you are already using "Bearer", that's all, the secret-token: change is part of the configuration, which I already fixed in the docs.git. | |
| Resolved with https://git.taler.net/taler-android.git/commit/?id=02ad9bde3e671a3566d68a6b968efe288e67d910 and https://git.taler.net/taler-android.git/commit/?id=3a12b1cc53f832e943b4825e132db6fe8ee083d6 Also made a new release of the PoS app. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-11-13 17:07 | Christian Grothoff | New Issue | |
| 2022-11-13 17:07 | Christian Grothoff | Status | new => assigned |
| 2022-11-13 17:07 | Christian Grothoff | Assigned To | => grote |
| 2022-11-14 05:58 | Christian Grothoff | Assigned To | grote => MS |
| 2022-11-14 12:52 | MS | Note Added: 0019418 | |
| 2022-11-14 13:19 | grote | Note Added: 0019419 | |
| 2022-11-15 14:18 | MS | Note Added: 0019422 | |
| 2022-11-15 14:18 | MS | Assigned To | MS => Christian Grothoff |
| 2022-11-15 15:19 | Christian Grothoff | Note Added: 0019423 | |
| 2022-11-15 15:20 | Christian Grothoff | Note Edited: 0019423 | |
| 2022-11-15 15:20 | Christian Grothoff | Assigned To | Christian Grothoff => grote |
| 2022-11-16 19:12 | grote | Note Added: 0019431 | |
| 2022-11-16 19:14 | grote | Note Added: 0019432 | |
| 2022-11-16 19:15 | grote | Assigned To | grote => Christian Grothoff |
| 2022-11-16 19:15 | grote | Status | assigned => feedback |
| 2022-11-16 19:52 | Christian Grothoff | Assigned To | Christian Grothoff => grote |
| 2022-11-16 19:53 | Christian Grothoff | Note Added: 0019433 | |
| 2022-11-16 19:53 | Christian Grothoff | Status | feedback => assigned |
| 2022-11-16 19:54 | Christian Grothoff | Note Edited: 0019433 | |
| 2022-12-20 17:26 | Christian Grothoff | Target Version | 0.9.1 => 0.9.2 |
| 2022-12-20 18:28 | Christian Grothoff | Target Version | 0.9.2 => 0.9.4 |
| 2023-01-03 13:48 | grote | Status | assigned => informing |
| 2023-01-03 13:48 | grote | Resolution | open => fixed |
| 2023-01-03 13:48 | grote | Note Added: 0019555 | |
| 2023-01-06 14:52 | Christian Grothoff | Fixed in Version | => 0.9.1 |
| 2023-01-06 14:52 | Christian Grothoff | Target Version | 0.9.4 => 0.9.1 |
| 2023-01-26 21:53 | Christian Grothoff | Status | informing => closed |