Failure to delete exception to recurring event #1753
Comments
|
Same issue here. |
|
Likely a duplicate of #1653 and fixed long ago. |
|
WTF! According to OGCS, I am running the latest version. |
|
At the top of the issue template when raising a bug, as well as the guidance for reporting a bug, request issues are reproduced on the latest alpha release. If you can indeed reproduce the issue on the latest alpha, this issue can be reopened. |
|
Hi Paul. I'm using the latest alpha release (2.10.1) and the issue sadly remains. Tthe steps described by galexmay are perfect. I have several recurring events on Google which I have deleted singular ocurrences there, but my Outlook calendar still shows those appointments. |
|
I hope it helps |
|
@ghnogueira Thanks for the log, but can you give me a clue on the name and time of series that has the deleted occurrence and the date of that occurrence?
No, when you checked, it actually said "Failed to check for ZIP release." - which is because GitHub changed how they present their pages which broke the mechanism. ⏫ Please manually upgrade to the latest release, v2.10.2.0, though issue #1653 was resolved in v2.10.1 and that was for O->G also. |
|
Yep OK, I've traced the issue back to a hotfix in v2.9.6.4. 📦 This should now be resolved with hotfix v2.10.2.12.zip (see instructions for applying). Please let me know how it goes. |
phw198
added
recurring appointment
waiting fix confirmation
|
Windows claims the hotfix link above contains a virus. How can I be sure
that it doesn't?
…On Fri, Dec 22, 2023 at 11:04 PM Paul Woolcock ***@***.***> wrote:
Yep OK, I've traced the issue back to a hotfix
<#1593 (comment)>
in v2.9.6.4.
📦 This should now be resolved with hotfix v2.10.2.12.zip
<https://github.com/phw198/OutlookGoogleCalendarSync/files/13757228/v2.10.2.12.zip>
(see instructions for applying
<https://github.com/phw198/OutlookGoogleCalendarSync/wiki/Reporting-Problems#applying-a-hotfix>
).
Please let me know how it goes.
—
Reply to this email directly, view it on GitHub
<#1753 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD5DCMRMK45GOWTTEB5WYADYKYGWDAVCNFSM6AAAAABATIC6HCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGEZDAMRUGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Well the entire code base is open source and It would be rather self defeating to openly publish infected software. But there's no accounting for antivirus false positives. Code signing it may help - I'll see if I can do that in a bit... 📦 Now signed v2.10.2.12.zip - see if that helps at all. |
|
How do we know that it is a false positive?
I'm not suggesting you would have deliberately published infected software,
but how do we know that it hasn't become infected?
…On Sat, Dec 23, 2023 at 7:58 PM Paul Woolcock ***@***.***> wrote:
Well the entire code base is open source and It would be rather self
defeating to openly publish infected software. But there's no accounting
for antivirus false positives.
Code signing it may help - I'll see if I can do that in a bit...
—
Reply to this email directly, view it on GitHub
<#1753 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD5DCMRJNKABJXYRKF4SMCLYK4ZVVAVCNFSM6AAAAABATIC6HCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGM3DANRTGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Well that's what code signing should prove - that it's not been tampered with since it was published. Are you saying the signed version of the hotfix is also being reported? If I didn't publish it infected, and your computer isn't infected, that would just leave GitHub servers as infected which is rather unlikely. Much more likely that your antivirus (MS Defender?) heuristics can't distinguish between genuine software programmatically connecting to Outlook mailbox accounts to sync calendar data and bad-actor software mining for email addresses and the like.... The executable CRC before I uploaded it is: |
|
As your post previously said "I'll see if I can do that in a bit", I didn't realise that you had already posted the signed code. I didn't get another notification of the edit. |
:)
I don't know if these were all within the timespan, but it seems it got solved. I'll keep monitoring. Thanks a lot as always, Paul! |
phw198
added
resolved
|
In case it helps anyone else, this fixed my issue when syncing O->G. Thanks @phw198! That reminds me, it's about time I clicked on that Donate button again. |
|
Thanks for confirming and the donation @jezzaaa 😊 |
Long due, but just dropped a small donation, @phw198... sadly not enough to hide splashscreen or to be the size of your contribution to my daily life with this app, but it was as much as the BRL->GBP exchange rate allows me. Thanks a lot as always! |
|
Any and all amounts are appreciated @ghnogueira - thanks so much! 🙂 |
|
Your work is unbelieavable! |
OGCS Version: v2.10.0.0
Edition: Installed
Sync Direction: O<->G
Bug Description
I have deleted an event as an exception to a recurring event. The deletion was carried out in Google calendar but is not replicating/deleting on my Outlook calendar.
Steps to Reproduce the Issue
Attached are my log file and the ics renamed in a zip as the ics raw would not upload.
Jazz Jam.zip
231213 OGcalsync.log
The text was updated successfully, but these errors were encountered: