Skip to content
This repository has been archived by the owner on Jun 14, 2023. It is now read-only.

Redundant info in Calendar Event Notification #559

Open
Liverpool4 opened this issue May 5, 2019 · 6 comments
Open

Redundant info in Calendar Event Notification #559

Liverpool4 opened this issue May 5, 2019 · 6 comments
Labels
evaluating Other considerations are needed to decide what to do

Comments

@Liverpool4
Copy link

Using the Amazfit Pace, f/w 2.8.4.0, and AmazMod 1893 on the watch. My phone is a Samsung Galaxy S9+ running Pie, holding calendars from Outlook and Google.

On the watch, with the calendar event notifications, I see the event description, "1:00" and the event start/finish time. I don't know where the "1:00" is coming from, it's not event duration. When I swipe down from the clockface and drill into the native notification, I see the middle line always states 01/01 1:00 - 1am on Jan 1st??. First line of the native notification states event description and last line states start/finish time as expected.

On the phone, and desktop, there are no fields which could populate that 1.00 01/01 data row. I saved an event created in Outlook as a text file, and there was nothing related to 1.00 01/01.

I created Google events in 3 different calendar apps (Google, DigiCal and Business Calendar), and used first only the default notification framework to push alerts to the watch. They all appeared on the watch with the 1.00 01/01 data row

Then I disabled the default notification framework and enabled AmazMod's - I created events again in the 3 apps, and watched for the notifications on the watch. Both Google Calendar and DigiCal inserted the 1.00 01/01 data row, but Business Calendar did not.

So, it appears to be a data field on the watch which is not used by mainstream calendar apps (something like event creation timestamp??), so it's redundant. And by default it's propagated to AmazMod.

Attaching 2 text files with the Outlook event and it's Accepted response; photo of the watch's AmazMod notification with the redundant 1.00; and photo of the watch's default notification with the redundant 1.00 01/01 row.

I can't see any use for it, especially since neither Outlook nor Google seem to make any use of it.

I propose removing this line of data, to clean up the Amazmod notification.

20190505_194604

2

test event - Paul Conyngham accepted.txt

test event.txt

@GreatApo GreatApo added the evaluating Other considerations are needed to decide what to do label May 5, 2019
@GreatApo GreatApo changed the title Redundant info in Calendar Event Alert Redundant info in Calendar Event Notification May 6, 2019
@1immortal
Copy link
Collaborator

@Liverpool4
Copy link
Author

Liverpool4 commented May 20, 2019

Redundant info in Calendar Event Notification

Can't get to see your comment, 1immortal, even after logging into Trello. I don't have permission to view it. Could you paste it as a reply here on GitHub?

Thanks

Paul

@GreatApo
Copy link
Collaborator

It is a link to a tracking system not a comment :) (just ignore it)

@Liverpool4
Copy link
Author

Thanks! Wasn't sure if an action was expected of me :)

@lfom
Copy link
Collaborator

lfom commented Jun 30, 2019

If the info appears on the standard/stock notification then obviously this info comes from the phone notification. We can create a app (Outlook?) specific filter to remove this info, but it's too much trouble for too little (it is harmless) and I don't use Outlook for testing...

@Liverpool4
Copy link
Author

OK, no problem, I understand it "doesn't affect functionality" so it's not a good use of your collective time - however all the testing rounds I did, indicate it's not just Outlook.

It also occurs with Google Calendar appointments, independently of the calendar app I use to create the appointment.

And thank you for developing and maintaining a really useful app!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
evaluating Other considerations are needed to decide what to do
Projects
None yet
Development

No branches or pull requests

4 participants