I have not received the trick or treat badge so I can not share it to get share the scare badge
Whatever, they should fix it, people see the Trick or Trick badge for ages and prepare themselves to get it. So the best would be if they fix it by awarding it to whoever made an activity in 2022 + make…
This year there is only one Halloween badge: Halloween 2022
The others are moved back to 2021. Garmin made a mistake when they moved back the dates and forgot to set an end date wich makes them visible…
I wrote this reply in another thread about the same issue:
This year there is only one Halloween badge: Halloween 2022
The others are moved back to 2021. Garmin made a mistake when they moved back the…
That is because of the badgeTypeIds. It got a 3 which is: {"badgeTypeId":3,"badgeTypeKey":"REPEATABLE"}
All badges with typeid 3 will have the label "REPEATABLE". Repeatable means that it is possible to be awarded with the badge multiple times.
The Halloween badges have always had an end date all previous years. The same with all the limited time and repeatable holiday and festival badges.
Badge data:
{"badgeId":1000018,"badgeKey":"activity_halloween_2019",
"badgeName":"Trick or Treat","badgeUuid":null,
"badgeCategoryId":1,"badgeDifficultyId":1,
"badgePoints":1,"badgeTypeIds":[3],"badgeSeriesId":null,
"badgeStartDate":"2021-10-31T00:00:00.0","badgeEndDate":null
This JSON data will handle how the badges are displayed. The data that handles if the badges are awarded or not is not available to us. It is odd that the data on the client and on the server are different, but we don't know the reasons for that.