携帯端末情報(必須)/Mobile Device Information(Required)*
Samsung S23 Ultra, Android 15, One UI 7.0
アプリのバージョン(必須)/App Version(Required)*
v105.1-250822-1722
問題が発生する頻度/Frequency of the issue occurring
毎回/Every time
問題の詳細/Issue Details
Steps
- On the field map, find any Hunt-a-thon (HAT) or Elder Dragon Interception (EDI) and tap into it.
- Tap the notification button at the top right corner of the node screen to enable the notification for the said HAT/EDI. Also note the start time of the chosen HAT/EDI.
- Close the app (exit the app completely).
- Put your phone away (off the screen/lock the phone, but make sure it is not in power-saving mode so that all notifications are receive in a timely manner as dictated by the app) and wait for the HAT/EDI notification to appear.
- Observe that the HAT/EDI notification always appears very much later than the actual start time of the HAT/EDI. In the latest instance, I enabled the notification as soon as I saw the HAT appears in preliminary mode (i.e more than 19 minutes left to start), but the notification only appeared when it has 10 minutes left on the HAT timer. This means that the HAT notification was 15 minutes late.
Expected:
- The HAT/EDI timer must be more precise than the current variance. It should be no more than a minute late. Other notifications like Cheers and Friend Quest can be very timely, so why not the HAT/EDI timer notifications? The notification is also late even when the app is running in the foreground, so this feature doesn’t make sense.
その他の情報/Other Information
There’s no workaround.
@Stampeder
Thank you for your report that notifications for HAT and EDI are always delayed.
To help us investigate further, could you please let us know the following information?
- Do the delayed HAT/EDI notifications appear specifically when you launch or reopen the app, or do they also arrive late even while the app remains closed?
- Anything else you noticed about the issue
Thank you for your understanding.
I was working at the time, so I enabled the notification when I saw the target HAT node entered preliminary state.
I continued working until I received the notification on my phone that the HAT has begun. Then I quickly tapped the notification and the game started up (it was closed, so it went through the full boot flow).
When the field map loaded, I saw that the HAT had only 9+ minutes remaining on the timer. This means that the notification was sent to me when it had around 10 minutes remaining.
Since HAT/EDI nodes have a 25-minute duration, this means that the notification was 15 minutes late.
This was today’s experience.
In the past, in earlier app versions, since the introduction of the HAT/EDI notification feature, I have observed that the notification is always late, and I find that the earlier I enabled the notification during the preliminary state (i.e. the more time left on the preliminary state timer), the later the notification tends to be.
For example, If I enabled the notification when the node had about 5 minutes left in the preliminary state, I would usually receive the notification within 5 minutes after it started.
If I enabled the notification when the preliminary state had about 10-15 minutes left before starting, the notification would be about 5-10 minutes late.
It’s as if the notification timer logic is not getting the start time correctly and therefore it failed to set the notification time correctly, in relation to the remaining time of the preliminary state countdown timer. To put it very simply, it appears that the more time is left on the preliminary state timer when enabling the HAT/EDI notification, the later the notification tends to be.
Hope this helps.
@Stampeder
Thank you very much for your detailed report.
The information you have provided has been shared with the development team for further investigation. If there is any additional information we can share on this, we’ll do so on this Forum.
Do feel free to post on the Forum if you’ve noticed anything else.
1 Like