-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contacts sync broken since NC 19upgrade #22439
Comments
cc @nextcloud/contacts @ChristophWurst It seems that z-push is confused by the contactsinteraction addressbook. |
does the client check which permissions are granted? this address book is read only. If any other operation than read is performed you get an "error" |
Wrong button --"
|
Though not sure what would be needed for REPROT |
is it possible to exclude contactsinteraction from being discovered? |
no, I don't think so |
@ChristophWurst then we need to make sure report is supported like any other addressbook :) |
Any news on this one? It's hard for me to find any real problems in the Log as it's spammed with messages... 😇 |
We also have the same situation connected with Z-Push. The address books should support REPORT. The same situation is with Deck generated calendars. All should support REPORT. It would be nice to have calendars and address books exposed via CalDAV/CardDAV to be connected with Z-Push (Exchange ActiveSync for Mobile). Any updates about one? |
we have the same behaviour with z-push and nextcloud sabre dav. But it looks like it depends on the device that is checking on calendar or contacts: the android gmail app and TBsync (thunderbird) seems not to produce the errors, but an iPhone with iOS 14.4 does. At least that's my observation so far. I'm not sure if REPORT needs to be supported according to any RFC... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr> Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
PostgreSQL returns data as resource when using IQueryBuilder::PARAM_LOB (which is used for QBMapper). Previously we just converted this resource using settype, which produced things like "Resource id #14" instead of the actual resource data. Now we read the stream correctly if the returned data is a resource See context at #22472 Fixes #22439 Signed-off-by: Thomas Citharel <tcit@tcit.fr>
How to use GitHub
Steps to reproduce
Expected behaviour
sync contacts should be working again
Actual behaviour
currently it is not possible to sync the contacts with my mobile phone anymore, z-push logs that the sync was aborted
Server configuration
Operating system:
Ubuntu 18.04.05
Web server:
Nginx
Database:
PostgreSql 12
PHP version:
7.4.9
Nextcloud version: (see Nextcloud admin page)
19.0.1.1
Updated from an older Nextcloud/ownCloud or fresh install:
updated from18
Where did you install Nextcloud from:
updater
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using encryption: no
Are you using an external user-backend, if yes which one: IMAP
Logs
Nextcloud log (data/nextcloud.log)
Nextcloud log
The text was updated successfully, but these errors were encountered: