Cannot create package anymore after upgrading to 5.16

0
I have converted a project to 5.16 and now am unable to create a package anymore. Not from the server where I only get to see a red sign instead indicating it has failed. And not from the modeler where I get the following error. Any clues what is wrong? System.NullReferenceException: De objectverwijzing is niet op een exemplaar van een object ingesteld. at Mendix.Modeler.JavaActions.CodeGeneration.CodeGenerationUtil.JavaQualifiedName(IEnumeration enumeration) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\CodeGenerationUtil.cs:line 91 at Mendix.Modeler.JavaActions.CodeGeneration.CodeGenerationUtil.GetJavaDataType(IHasContext context, DataType type, Boolean elementType, Boolean castType) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\CodeGenerationUtil.cs:line 71 at Mendix.Modeler.JavaActions.CodeGeneration.MicroflowProxyGenerator.BuildMicroflowModuleData(IModule module) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\MicroflowProxyGenerator.cs:line 78 at Mendix.Modeler.JavaActions.CodeGeneration.MicroflowProxyGenerator.BuildModuleData(IModule module) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\MicroflowProxyGenerator.cs:line 42 at Mendix.Modeler.JavaActions.CodeGeneration.MicroflowProxyGenerator.Generate(IModule module, String proxiesDir, List`1 generatedFiles) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\MicroflowProxyGenerator.cs:line 30 at Mendix.Modeler.JavaActions.CodeGeneration.ProxyGenerator.Generate(IModule module) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\ProxyGenerator.cs:line 51 at Mendix.Modeler.JavaActions.CodeGeneration.ProxyGenerator.GenerateJava() in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\CodeGeneration\ProxyGenerator.cs:line 39 at Mendix.Modeler.JavaActions.JavaFilesProviderFactoryRegistry.WriteJavaFiles(IProject project) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\JavaActions\JavaFilesProviderFactoryRegistry.cs:line 24 at Mendix.Modeler.Deployment.CoreDeploymentWork.GenerateFiles(IProject project, DeploymentSettings settings, Boolean generateForLocalDeployment) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\CoreDeploymentWork.cs:line 100 at Mendix.Modeler.Deployment.CoreDeploymentWork.WriteFiles(IProject project, DeploymentSettings settings, IProgressInfo info, Boolean generateForLocalDeployment) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\CoreDeploymentWork.cs:line 87 at Mendix.Modeler.Deployment.Build.CoreDeploymentWorker.DoWork(DeploymentPhase phase, IProject project, DeploymentSettings settings, IProgressInfo info) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Deployment\Build\CoreDeploymentWorker.cs:line 49 at Mendix.Modeler.Deployment.DeploymentProcessBuilder.<>cDisplayClass7.<addbuildstepsforphase>b6(IProgressInfo info) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\DeploymentProcessBuilder.cs:line 117 at Mendix.Modeler.Deployment.FileIOExceptionHandlingProcess.CatchDiskException(Action action) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\FileIOExceptionHandlingProcess.cs:line 28 at Mendix.Modeler.Deployment.FileIOExceptionHandlingProcess.<>cDisplayClass2.<addstep>b0(IProgressInfo info) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\FileIOExceptionHandlingProcess.cs:line 19 at Mendix.Modeler.Utility.Progress.ProcessRunner.worker_DoWork(Object sender, DoWorkEventArgs e) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 66 at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
asked
2 answers
1

Frans:

This looks to be very much the same problem that was reported recently in this forum:

Deployment problem in BM 5.16.0

Apparently, there will very soon be a new release of the Business Modeler (newer that 5.16.0) that should address this if it is, in fact, the same problem that was reported earlier.

Good luck,

John

answered
1

Update 2: Mendix 5.16.1 has been released and it fixes this bug.

Update 1: found and fixed this bug and the fix will be part of 5.16.1 which will appear very soon, I hope.

This is another error than the one reported in the other forum post (Crash when creating deployment package). The other one I already fixed and will appear in a patch update.

I have not seen this error before. The Modeler is trying to generate a proxy for a microflow and that microflow seems to point to a non-existing enumeration... Does that mean anything to you, Frans? Did you change something after converting to 5.16?

Can you submit a ticket with a test project? If you do it quickly, we might be able to sneak it into the next patch.

answered