Found this post in another thread. Looks like a bug related to the 5.2 update and the team is aware of it.
1 Like
Found this post in another thread. Looks like a bug related to the 5.2 update and the team is aware of it.