I can not publish my app.

I get this error:



Id:
374d68be-9c25-4689-98ec-78127467dffa
Time of Log:
2020-01-14 11:56:58
Request Key:
eSpace:

Tenant:

User:

Session Id:

Server:
S5IE7-LT72CO
Module:
CompilerService
Message:


Internal Error: An error occurred in task 'Loading eSpace with key 'd463790d-ead4-478b-bddb-b9a0f20ce5f6'':
Object not found: /AnonymousStructures.gZ67tnZGD0GVKPYOMFeNsw/Attributes.uP22jp+smkqlTL++OkxZJQ
Details : System.InvalidOperationException: Object not found: /AnonymousStructures.gZ67tnZGD0GVKPYOMFeNsw/Attributes.uP22jp+smkqlTL++OkxZJQ
   at OutSystems.HubEdition.Compiler.CompoundKeyResolver.GetObject(CompoundKey key, AbstractObject relativeTo)
   at OutSystems.HubEdition.Compiler.RecordLiteralField.get__attribute()
   at OutSystems.HubEdition.Compiler.Expressions.Visitors.ExpressionToStringVisitor.Visit(RecordLiteralExpression element)
   at OutSystems.HubEdition.Compiler.Expressions.AbstractExpression.Accept(AbstractExpressionVisitor visitor)
   at OutSystems.HubEdition.Compiler.Expressions.AbstractExpression.ToString()
   at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
   at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
   at System.String.Format(String format, Object[] args)
   at OutSystems.HubEdition.Compiler.Expressions.AbstractObjectExpression.get__expressionType()
   at OutSystems.HubEdition.Compiler.Expressions.AbstractObjectExpression.AfterLoad()
   at OutSystems.HubEdition.Compiler.Serialization.ESpaceReader.LoadObjectExpression(AbstractObject parent, CollectionIndex collectionIndex)
   at OutSystems.HubEdition.Compiler.Serialization.ESpaceReader.LoadExpression(AbstractObject parent, CollectionIndex collectionIndex)
   at OutSystems.HubEdition.Compiler.Argument.LoadChildren(ESpaceReader reader)
   at OutSystems.HubEdition.Compiler.Serialization.ESpaceReader.InnerLoadChildren[Type](AbstractObject parent, CollectionIndex collectionIndex, ICompilerCollection`1 collection)
   at OutSystems.HubEdition.Compiler.Serialization.ESpaceReader.LoadChildren[Type](AbstractObject parent, ICompilerSequence`1& collection, CollectionIndex collectionInd


Environment Information
Stack:
   at OutSystems.HubEdition.ServerCommon.MessageBrokers.ErrorLoggingMessageBroker.#XCb(IMessageObject message)
   at OutSystems.HubEdition.ServerCommon.MessageBrokers.ErrorLoggingMessageBroker.ReportMessage(IEnumerable`1 messages)
   at OutSystems.HubEdition.ServerCommon.MessageBrokers.MessageBrokerExtensions.ReportMessageArrayList(IMessageBroker messageBroker, HEMessageArrayList messages)
   at OutSystems.HubEdition.ServerCommon.Tasks.AbstractTask.Execute()
   at OutSystems.HubEdition.ServerCommon.Tasks.AbstractTask`3.Run(InputType context, IMessageBroker messageBroker, OutputType& result)
   at OutSystems.HubEdition.ServerCommon.Tasks.TaskRunner.Run()
   at OutSystems.HubEdition.ServerCommon.Tasks.AbstractTask.Execute()
   at #h2b.#h3b.#vo.#e9b()
   at OutSystems.HubEdition.ServerCommon.Tasks.TaskRunner.Run()
   at #h2b.#h3b.InnerExecute()
   at OutSystems.HubEdition.ServerCommon.Tasks.AbstractTask.Execute()
   at OutSystems.HubEdition.DeploymentController.Compiler.<>c__DisplayClass154_0.<PublishOml>b__0()
   at OutSystems.HubEdition.DeploymentController.Compiler.PublishOml(Object publishContext)
   at #DSb.#6wb.#VQ.#BFb(Object s)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Hi Miguel,

See if the provided workaround in this post, which describes a similar issue, can be of any help. 

Otherwise I'd contact OutSystems Support for this.

Regards,

Nordin

This is caused by something added to the code after the last successful publish. The error stack doesn't give much info, either. So removing the newly added stuff one by one and retrying the publish could be an approach.