Closed nicokaiser closed 8 years ago
It is possible to inspect REPORTs in Chrome DevTools:
BTW: thanks for reporting all the detailed issues
@nicokaiser can I ask you for a example vcard to reproduce this issue? THX
For two of the three requests to "contacts/" Chrome says "Failed to load response data" in the Inspector -> Response section, and the third request seems to only contain loads of metadata. I'll attach my vCard, which is displayed with a broken image.
THX @nicokaiser
I see the image on the latest master of contacts app
@DeepDiver1975 This is strange. Maybe the base64 gets corrupted on the way, I'll try to figure out what is actually transferred to the client.
@DeepDiver1975 In the DAV response that is transferred to the frontend, the photo seems to be prefixed with cropping settings, see screenshot. Maybe this leads to problems when creating the URL version?
How does the vcard look like in the database?
@DeepDiver1975: Like above, but of course without encoding:
PHOTO;X-ABCROP-RECTANGLE=ABClipRect_1&0&0&671&671&Nh68TCRv7GErj8P8mk8qCA==;
ENCODING=b;TYPE=JPEG:/9j/4AAQSkZJRgABAQEASABIAAD/4QBARXhpZgAATU0AKgAAAAgAA
YdpAAQAAAABAAAAGgAAAAAAAqACAAQAAAABAAACnqADAAQAAAABAAACngAAAAD/7QA4UGhvdG9
zaG9wIDMuMAA4QklNBAQAAAAAAAA4QklNBCUAAAAAABDUHYzZjwCyBOmACZjs+EJ+/+ICHElDQ
19QUk9GSUxFAAEBAAACDGxjbXMCEAAAbW50clJHQiBYWVogB9wAAQAZAAMAKQA5YWNzcEFQUEw
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPbWAAEAAAAA0y1sY21zAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKZGVzYwAAAPwAAABeY3BydAAAAVwAAAA
Ld3RwdAAAAWgAAAAUYmtwdAAAAXwAAAAUclhZWgAAAZAAAAAUZ1hZWgAAAaQAAAAUYlhZWgAAA
bgAAAAUclRSQwAAAcwAAABAZ1RSQwAAAcwAAABAYlRSQwAAAcwAAABAZGVzYwAAAAAAAAADYzI
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAdGV4dAAAAABGQgAAWFlaIAAAAAAAAPbWAAEAAAA
A0y1YWVogAAAAAAAAAxYAAAMzAAACpFhZWiAAAAAAAABvogAAOPUAAAOQWFlaIAAAAAAAAGKZA
AC3hQAAGNpYWVogAAAAAAAAJKAAAA+EAAC2z2N1cnYAAAAAAAAAGgAAAMsByQNjBZIIawv2ED8
VURs0IfEpkDIYO5JGBVF3Xe1rcHoFibGafKxpv33Tw+kw////wAARCAKeAp4DASIAAhEBAxEB/
8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQI
DAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q
0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6i
...
Let me test the app with this data ....
@nicokaiser can I ask you to share the vcard with me? THX
@DeepDiver1975 I sent it to you via E-mail
Got it. Thx
This is a parsing issue in the vcard library we use on client side.
fixed with https://github.com/Heymdall/vcard/pull/2
Steps to reproduce
Expected behaviour
Contact images should display correctly
Actual behaviour
Some contact images are broken.
Some of the {{data:image/...;base64}} URLs that seem to be generated by the frontend are broken, there seems to be garbage before the actual image content, e.g.:
This is a complete URL (with some different garbage):
Please tell me how I can provide any additional information, I cannot access the CadDAV XHR result, as it is transferred via "REPORT" (which the Chrome developer console refuses to display). But in the database, the images are stored correctly, and also the other clients can display them without problems.
Server configuration
Operating system: Debian 8
Web server: nginx
Database: MySQL 5.5
PHP version: PHP 5.6
ownCloud version: 9.0.0
Contacts version: 1.0.0.0
Updated from an older ownCloud or fresh install: Updated from 8.x
Signing status (ownCloud 9.0 and above):
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Chrome 48
Operating system: OS X 10.11
CardDAV-clients: iOS 9.2, OS X 10.11