|
|
Post by jontara on Jul 28, 2021 22:58:53 GMT
There seems to be a problem with iOS Barcode if there are binary QR code segments.
I have yet to look into this fully, I get:
I 07/28/2021 15:43:36:150 6c10f000 HttpServer| Process URI: '/app/Scan/scan_received'
I 07/28/2021 15:43:36:150 6c10f000 APP| RHO serve: /app/Scan/scan_received
I 07/28/2021 15:43:36:150 6c10f000 APP| Params: {"__rho_object"=>{"status"=>"1", "barcode"=>"0"}, "rho_callback"=>"1"}
Invalid or incomplete POST params
Some good test images can be found here:
These are EU Digital Green Certificate (for Covid immunization/test/recovery data). They have chosen to go with CBOR instead of JSON, and so they have binary segments in the QR.
Is this a known issue?
I have not tried Android yet.
|
|
|
|
Post by jontara on Aug 15, 2021 22:18:36 GMT
As it turns out, DGCs do not in fact have binary QR segments. However, if there ARE binary QR segments, they will I believe be omitted from AVMetaData objects. You need to use some CoreImage support, I think CIDetector.
My problem seems to be incorrect encoding into URL parameters. Sometimes the data contains strings that look like URL escapes, for example %96 and somehow the "%" is not being itself escaped. And, so, it creates an invalid UTF-8.
Update: There seems to be a problem passing parameters to controller methods and also with logging, when there are sequences in the string that look like url encoding. I haven't quite nailed it down, I will put in an Issue when I know more.
As for the request for handling binary QR segments - it's still a good idea, but I don't know how many practical applications there are, and ... I don't need it.
|
|
|
|
Post by Alex Epifanov on Aug 20, 2021 10:17:03 GMT
As it turns out, DGCs do not in fact have binary QR segments. However, if there ARE binary QR segments, they will I believe be omitted from AVMetaData objects. You need to use some CoreImage support, I think CIDetector.
My problem seems to be incorrect encoding into URL parameters. Sometimes the data contains strings that look like URL escapes, for example %96 and somehow the "%" is not being itself escaped. And, so, it creates an invalid UTF-8.
Update: There seems to be a problem passing parameters to controller methods and also with logging, when there are sequences in the string that look like url encoding. I haven't quite nailed it down, I will put in an Issue when I know more.
As for the request for handling binary QR segments - it's still a good idea, but I don't know how many practical applications there are, and ... I don't need it.
Thanks Jon! Dmitry Soldatenkov take a look please |
|
