@Kabam Miike Though it’s not very consequential, you didn’t fix the “quit” button label I posted. I only mention because I’d rather iron out as much as possible now, than be surprised with further results of whatever caused these button issues. Thanks for reading this.
Does that MS ID QUIT one cause an actual crash, like the original synergy problem one (I’m guessing not).
If just similar to other instances in past where a Resource ID got out of sync between your device and the current update build. Then it is a far different minor problem than what was causing the crash to happen
We have a fix for this incoming. It is a hotfix which will require an update. Keep an eye out for v33.2.3 coming to your App Store soon. This should address the Synergy Screen error and crash.
Thank you all for your patience as we worked to address this issue.
We have a fix for this incoming. It is a hotfix which will require an update. Keep an eye out for v33.2.3 coming to your App Store soon. This should address the Synergy Screen error and crash.
Thank you all for your patience as we worked to address this issue.
@Kabam Miike Though it’s not very consequential, you didn’t fix the “quit” button label I posted. I only mention because I’d rather iron out as much as possible now, than be surprised with further results of whatever caused these button issues. Thanks for reading this.
Does that MS ID QUIT one cause an actual crash, like the original synergy problem one (I’m guessing not).
If just similar to other instances in past where a Resource ID got out of sync between your device and the current update build. Then it is a far different minor problem than what was causing the crash to happen
Comments
If just similar to other instances in past where a Resource ID got out of sync between your device and the current update build. Then it is a far different minor problem than what was causing the crash to happen
No problems other than the label. Just pointing it out.