In this weekly development update VIII we will update you on the state of the next update and what we are further working on.
Last week, Jan 16th. - Jan. 22nd
We released a backend update to tackle some custom match and account migration issues on January 17th. After checking the extended logs, we can see that this resolved some of the related issues. Nevertheless, we will need to address others in another backend update as well as in the client update shortly.
The client update has made good progress, as we could mark several key issues with reconnection as resolved internally. However, we will need at least one additional internal test-build to fix remaining edge-cases before we can publish.
This week, Jan 23rd - Jan. 29th
We continue QA focus on the next internal version of the client update for internal testing.
While QA and the development team are working on this, we have identified several key issues that we will address next. As we cannot reproduce some of these issues here, we kindly ask those affected for additional info via our Discord channel:
- Game closing/freezing for some players after placing the first settlement of a game:
We cannot reproduce this here, but some players reported that clearing their cache (on PC) resolved the issue for them. If this is related to corrupt cached data, re-installing the app on mobile should resolve this as well. We would appreciate if affected users could let us know if this is the case.
- Custom Match Issue “Could not create lobby due to an error”
The backend updated resolved a custom match issue that caused players not being displayed in the custom match lobby properly. However, some accounts get the error message above immediately when selecting custom match mode. We are actively investigating this issue. As of now, we believe it is tied to account migration. You can tell us on discord, if your account is also affected by this problem.
- Some accounts still could not migrate to the new backend
We will add further logging in the next backend update to get to the root of this complex issue. We have several leads on this and will continue refining the migration process until this is resolved for all. In the meantime if you are affected, please contact our support team and we will try to find an alternative solution for you!