mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 19:36:00 +03:00
[GH-ISSUE #174] NPE after upgrade to 2.8.0 #636
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#636
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maybeec on GitHub (Oct 18, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/174
After upgrading to 2.8.0, I got several NullReferenceExceptions on Calendar sync of the following schema:
Configuration:
@aluxnimm commented on GitHub (Oct 18, 2016):
Can you check if it makes any difference when you open and save the sync profile in the options dialog?
@maybeec commented on GitHub (Oct 18, 2016):
Basically, after doing that and waiting some synchronizations, the issues seems to be gone.
However, I am a little bit afraid as I configured a calendar with Replicate Outlook -> Server and got the following three synchronizations:
what is happening here?
@aluxnimm commented on GitHub (Oct 18, 2016):
Nullreference Exception when options are not saved fixed in 2.8.1
@maybeec commented on GitHub (Oct 18, 2016):
Thanks. But can you explain, why my outlook data got updated regardless of the sync profile replicate?
As stated in the log above.
@aluxnimm commented on GitHub (Oct 18, 2016):
Nope, nothing got updated in Outlook. This info just shows the detected state before syncing (the delta). So we detected, that 3 items in Outlook have been changed since the last sync and nothing was changed on the server side since last sync.
@maybeec commented on GitHub (Oct 18, 2016):
👍 thanks. Thus, I miss interpreted the information.
Best support ever!
@aluxnimm commented on GitHub (Oct 18, 2016):
You are welcome :)