Openbravo Issue Tracking System - Retail Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0045026 | Retail Modules | Web POS | public | 2020-09-10 11:10 | 2021-01-25 06:38 |
|
| Reporter | salvador_campanella | |
| Assigned To | jorge-garcia | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0045026: After updating to Chrome 85 on Android, it is not possible to scan UPC codes that contain letters |
| Description | After updating to Chrome 85 on Android, it is not possible to scan UPC codes that contain letters |
| Steps To Reproduce | 1 - Go to window Channel - Touchpoint Type and check Use External Input in VBS POS Terminal Type
2 - Go to window Product: Adhesive body warmers and change UPC/EAN to 006R01649
3 - In android mobile with chrome 85 go to web pos terminal VBS-1
4 - Scan product Adhesive body warmers
5- Its not possible to scan product with letters in upc
It's attached the upc code bar |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  EtiquetaProducto_20200907152059.pdf (31,436) 2020-09-10 11:10
https://issues.openbravo.com/file_download.php?file_id=14954&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2020-09-10 11:10 | salvador_campanella | New Issue | |
| 2020-09-10 11:10 | salvador_campanella | Assigned To | => Retail |
| 2020-09-10 11:10 | salvador_campanella | File Added: EtiquetaProducto_20200907152059.pdf | |
| 2020-09-10 11:10 | salvador_campanella | Resolution time | => 1601503200 |
| 2020-09-10 11:10 | salvador_campanella | Triggers an Emergency Pack | => No |
| 2020-09-10 12:05 | Practics | Issue Monitored: Practics | |
| 2020-09-16 11:13 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com |
| 2020-09-29 07:53 | ranjith_qualiantech_com | Assigned To | ranjith_qualiantech_com => Retail |
| 2020-10-06 14:13 | marvintm | Note Added: 0123572 | |
| 2020-10-06 14:13 | marvintm | Assigned To | Retail => salvador_campanella |
| 2020-10-06 14:13 | marvintm | Status | new => feedback |
| 2020-10-23 10:07 | egoitz | Note Added: 0123903 | |
| 2020-10-23 10:07 | egoitz | Status | feedback => new |
| 2020-11-11 12:37 | egoitz | Assigned To | salvador_campanella => jorge-garcia |
| 2021-01-25 06:38 | marvintm | Resolution time | 1601503200 => |
| 2021-01-25 06:38 | marvintm | Note Added: 0125740 | |
| 2021-01-25 06:38 | marvintm | Type | defect => design defect |
|
Notes |
|
|
|
|
Unfortunately after testing from our side with an Android device (vresion 8.1) with Google Chrome 85 (version 85.0.4183.127) and a bluetooth scanner, we have been unable to reproduce the problem. The example code is correctly scanned. |
|
|
|
(0123903)
|
|
egoitz
|
|
2020-10-23 10:07
|
|
The problem is reproducible only when the device is configured to use the keyboard "Microsoft swiftkey keyboard".
With that configuration the problem scanning does not happen in all the fields but only in the scan field |
|
|
|
|
|
We don't currently support scanning other than with actual physical scanners (and physical keyboards), so we are currently moving this issue to design defect |
|