[Fix incoming] Game crashes when looking at guild activity

Bug Reports
22

This bug is back, pretend its shiny keys.
Get it fixed, within 12 hour’s.

2 Likes
23

Works OK for me (Xbox Series X). Can see log entries showing guild members setting defence in various parts of the keep.

Edit: It was working. Not any more.

2 Likes
24

Is everyone in your Guild on 8.5?
For anyone getting this issue agin.

25

Has this guild activity crash thing been resolved? I’m on PS and still getting it.

26

On xbox. Crashed for me today. After pressing guild activity.

27

The same problem Xbox.

28

Guild Wars is over…why is this still happening???

1 Like
29

Same as last Guild Wars, for me the activity log still worked after several members had set defence, and the log showed it. Not long afterwards, it started crashing again. I’m guessing it’ll start working again once the log fills up enough to push whatever broke it out of the last 100 messages.

2 Likes
30

@Raistlin whats your invite code?

Anyone else still getting a crash when trying to view Guild Activity, despite the event ending?

Also, did anyone have crashing during GW on the last day?

31

I did earlier today, but it’s stopped now.
I’ve seen someone mention that it’s a glitch with some activity notification and it stops crashing once that gets pushed down off the list, but I can see four days on the list, and it’s not crashing, so that seems unlikely.
It’s not letting me hit square to get more entries, though. I have 98 logs listed. Not sure if that’s normal?
Just adding info, in case any of that helps.

1 Like
32

It’s no longer crashing for me now, but if I get more entries, the game freezes. Monday tends to add a lot of task completion entries to the log, so I think there is a specific GW related activity log entry that nukes everything that got pushed out by task logs, which is brought back in when I get more entries.

The log entry that records a member setting defence doesn’t cause a problem in itself, as it was still working for me with a few of these in the log.

It was still crashing on Monday morning, after GW ending. This would fit with the hypothesis there is a killer log entry from GW, that was still there before task completions pushed it out of the last 100.

1 Like
33

cross sharing

1 Like