From: Krzysztof B. <kb...@un...> - 2023-06-07 11:17:14
|
Hi Sander, W dniu 7.06.2023 o 11:57, Sander Apweiler pisze: > Dear Krzysztof, > > On Tue, 2023-06-06 at 14:54 +0200, Krzysztof Benedyczak wrote: >> Dear Laura, >> >> W dniu 6.06.2023 o 13:19, Laura Hofer pisze: >>> Dear Krzysztof, Dear Roman, >>> >>> we were just about to install unity 3.13.0 and then start testing. >>> To >>> do this, we first switched from unity 3.11.2 to unity 3.12.0, then >>> to >>> 3.13.0. After that, we received an application error message when >>> logging in (see attached screenshot). Unfortunately we could not >>> find >>> any error message in the stack trace, so we switched back to >>> 3.12.0. >>> There we got the same error message at login, but then we could >>> also >>> find an error message in the stack trace. This is also attached as >>> a >>> txt file. >> >> Thank you for the report. Most likely a regression caused by one of >> recent big refactorings. >> >> Some questions: >> >> 1. The DB on which you run 3.12 (and got the attached stacktrace) was >> used (and possible modified) with 3.13 or not? > Yes the database was used also on 3.13. It looks like there was no > modification on 3.13 start up, but I'm not sure >> 2. If the answer to above is positive: can you restart your test >> scenario (i.e. start from 3.11, upgrade to 3.12) and test on 3.12 >> whether the issue is also present on that version? > Sadly we did not made a database backup before. By starting 3.11.2 > unity throws an error about the supported database version: > OK, we will try to find it on our side then, will take more time in such situation though. Will keep you posted. Best, Krzysztof |