Hi, I'm testing with the project you provided on ticket 2141 to see if I can reproduce the problem. I'll let you know what I find.

Thank you Sergio! The fix for me was to reimport everything at the top level directory. I honestly don't know why this was needed but it worked.

We need to understand what happened. Doing a "Reimport All" shouldn't be necessary and restarting Unity can probably show errors again.

I tried the project you attached in issue 2141, installed 3.1.3 version and after fixing a few compiler issues (you are calling NoesisUnity.UpdateCursor private method), some xamls that were using x:Name as keys in dictionaries, and changing Resources.xaml to use the NoesisTheme in our package, the installation finished and got no more errors. I want to remark one thing, in the upgrade steps you specified, you are removing 3.1.2 from Unity Package Manager and then installing 3.1.3, probably without closing Unity in between. This is problematic because Noesis 3.1.2 native library is yet in memory, and the new version library cannot be loaded.

Could you please try with that project too to see if you can upgrade it correctly?

Thanks for jumping on this quickly. I can confirm that in my project the update cursor behavior and Resources.xaml behavior was fixed a few months prior. These changes occurred in the migration to 3.1.2 and the resources.xaml file present is included in this ticket.

What was not fixed in my code on upgrade to 3.1.2 are the missing key properties for inline resource dictionaries on two XAML screens. I can confirm that I did not restart Unity after removing the prior package version.

I'm not sure what my next step is to help.

I feel like the challenge here is that I am not an expert XAML user and I introduce ignorant or unexpected XAML. The XAML might work in prior versions of Noesis but then on upgrade things fail. When this happens I enter into an unexpected "no mans land" in which features that normally work very well fail with unexpected behavior (e.g. missing XAML for separate unrelated files).

Could you share with us an updated version of the project with all the compiler/xaml issues fixed?
And try to reproduce your upgrade problems with that project, so we both have the same project to compare and find what is happening.

Hi!

We have plan to release 3.1.4 next week (before our travel to GDC), so I think this is a great opportunity to quickly solve this.

If you could give us access to a project (working in 3.1.X) and the steps to be performed to upgrade to 3.1.3 that reproduces this issue we will give this max priority.

Congratulations on the trip to GDC. I believe you have an amazing product.

The game is large and it takes considerable effort to create a package that I can share. In this scenario I would be pulling down a version from a few days prior. The only change I would apply is the addition of resource dictionary keys for two XAML screens that were missing this. Is it possible the missing keys cause import to fail on project upgrades?

I'll work to provide a zip file of the project prior to the upgrade. I'll include the missing keys so that you have everything identical to what I encountered on upgrade.

Thank you!

I'm still working on this. There is complexity in downloading a prior build due to the size of the pull (100GB+), and then making sure it compiles and runs for you.

Hi, thank you!

This build that you are preparing is reproducing the issue following a list of steps?

I haven't been able to pull down a build of my project that is a copy of the day the behavior manifest. GitHub + Git LFS is having issues when I pull a fresh copy of source + assets. I was just going to send over source without game assets but apparently my dlls are in LFS and so I need to pull down everything. It's slow going until I figure out how to better structure things in GitHub and LFS on my end. My GitHub LFS transfer speed is about 2MB/s out of 100,000 MB. This issue crept on me and it is now very apparent when I need a fresh copy of everything.