Skip to content
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

Default notification settings getting reset? #78

Closed
silverbow25 opened this issue Oct 1, 2017 · 5 comments
Closed

Default notification settings getting reset? #78

silverbow25 opened this issue Oct 1, 2017 · 5 comments
Assignees
Labels
bug Related to a bug or a critical problem in the code. help request Issues raised by users who had problems running the script.

Comments

@silverbow25
Copy link

silverbow25 commented Oct 1, 2017

Steps to reproduce

What action or series of actions is the cause of the issue?

  1. action 1; Set default notifications, preferably more than one for calendar events on your main calendar.
  2. action 2; Create new event and your defaults will not be there.
  3. action 3; Go back to calendar settings and confirm that default notifications have been reset.

Expected behavior

What should happen?
Defaults should not get touched by this script

Current behavior

When I had this script enabled the default notification settings get wiped when I create a new calendar event.
What happens instead?

Context

  • Version of the script: x.x.x (look for a line in the code which reads var version = 'x.x.x';);
  • Any other details which might be related to the context;

Extended description

Try to describe the problem in the most complete way you can add images,
error messages, hypothesis and observations regarding the problem here.

Possible solution

If you think you know what causes the problem or if you know a solution for it
write it here.

@GioBonvi
Copy link
Owner

GioBonvi commented Oct 3, 2017

Hello @silverbow25, you are perfectly right in stating that the script should not change your default calendar notifcations: I can assure you this is not an expected result from running the script and if it really does it's a nasty bug we need to track down as soon as possible.
You can see for yourself by looking at the code that the script does not in fact access any calendar other than your birthdays/events one.

Unfortunately I was not able to replicate the bug in any way. This is what I tried:

  • first what you suggested:
    • opened calendar, set a new default notification for my main calendar (I alread had two), saved the settings
    • created a new event in the calendar: the default notifications are OK
    • opened calendar settings: default notifications are OK
  • then I checked if running the script caused the issue:
    • opened calendar, set a new default notification for my main calendar (I alread had two), saved the settings
    • manually run the script
    • created a new event in the calendar: the default notifications are OK
    • opened calendar settings: default notifications are OK
  • lastly I uninstalled the script completely (from here), reinstalled it, then run it again:
    • opened calendar, set a new default notification for my main calendar (I alread had two), saved the settings
    • uninstalled the script
    • reinstalled the script
    • manually run the script
    • created a new event in the calendar: the default notifications are OK
    • opened calendar settings: default notifications are OK

Can I ask you some questions to further examine this problem?

  • Did this happen suddenly at one time or have you eperienced the bug multiple times/for a long time?
  • What made you suspect it's this script that is modifying your default notifications?
  • Are you 100% sure you set the default notifications right in the first place (e.g. possibly you closed the notification settings page without clicking "Save")
  • Can you confirm the bug is still present if you do the following:
    • Open your calendar notification settings
    • Set a new default notification
    • Save and exit the notification settings page
    • Re-open the notification settings page (without creating an event or doing any thing else)

I hope we can solve this, thank you for your time and effort in reporting this.

@GioBonvi GioBonvi added bug Related to a bug or a critical problem in the code. help request Issues raised by users who had problems running the script. labels Oct 3, 2017
@GioBonvi
Copy link
Owner

GioBonvi commented Oct 11, 2017

Hi @silverbow25!

Are you still experiencing this problem?
This issue is a help request and has received no updates in the last three days, so it is being tagged "unresponsive".

In a month's time (on 11/11/2017) this issue will be closed in compliance with the rule about unresponsive help requests.
You can reply to this issue at any moment during this period of time to reactivate it.

Best regards

@GioBonvi GioBonvi added the unresponsive Issues/PRs left open without an answer from the creator. label Oct 11, 2017
@GioBonvi GioBonvi self-assigned this Oct 11, 2017
@silverbow25
Copy link
Author

So this is a little bit wierd. I installed the script. Then I added my own custom event notifications to my calendar (not related to birthday calendar). Then awhile later I went in and they were gone. I added them again, and they disappeared again. I deleted the script, and added them again and they stayed. Thing is, apparently deleting the script does not uninstall it, because it is actually running and giving me birthday alerts. So now I do not know why the custom notifications were getting wiped or if it was completely unrelated to the script. It appears to be more of a google bug than anything at this point.

@GioBonvi GioBonvi removed the unresponsive Issues/PRs left open without an answer from the creator. label Oct 18, 2017
@GioBonvi
Copy link
Owner

GioBonvi commented Oct 18, 2017

Yes, deleting the script does not remove it completely: if you had notifications running when you deleted it try will keep on running because deleting the script doesn't remove the triggers.

For a complete uninstall you have to stop the notifications (as explained here), delete the script and remove the authorizations you granted to try script (you can do it here).

I agree that the bug seems to be unrelated to this script: if you agree I'd close this issue.

Thank you for your cooperation.

@silverbow25
Copy link
Author

silverbow25 commented Oct 18, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Related to a bug or a critical problem in the code. help request Issues raised by users who had problems running the script.
Projects
None yet
Development

No branches or pull requests

2 participants