Launchpad: Assertion failed: ManagedObject.apply: encountered unknown setting 'inboundPermanentKey'

[omakinen]

Hi all!

The gateway system was upgraded from UI add-on 2 to FES 6.0. UI5 libraries are now of version 1.71.5.

Some custom apps started to produce this kind of error to browser console log upon startup:

abap.js:64 Assertion failed: ManagedObject.apply: encountered unknown setting
'inboundPermanentKey' for class
'sap.ushell.components.container.ApplicationContainer'
(value:'X-SAP-UI2-PAGE:X-SAP-UI2-CATALOGPAGE:SAP_HR_BC_MANAGER_T:8J4P99MBPQ3NPEOKDAQXMK6FX')

The apps work fine but I would like to get rid of this annoying error.

1. I have searched through the app source codes, there is no mention of "inboundPermanentKey" in them.
2. The catalog SAP_HR_BC_MANAGER_T contains both SAP standard apps and these custom apps but I can't see anything wrong in there. In the config of these apps (target mappings, tiles) there is no mention of setting called "inboundPermanentKey". Same goes for other catalogs/apps where this error comes up.
3. The catalog contains some apps which are configured "old style" in LPD_CUST and some newer apps which use simplified target mapping in Launchpad only.

Are there perhaps some new settings or configuration that needs to be done in the FES after upgrading to FES 6.0?

Thank you in advance for any advice!

br, Ossi

[DanielSchneider · Accepted solution]

Hi Ossi,

SAP assured that this error should not lead to functional errors or observable performance issues.

They are going to filter/remove this error from the console log in some upcoming patch/SAP note. Until then the error can get ignored.

BR Daniel

[omakinen · Accepted solution]

Thanks for the update Daniel!

Good to know that the issue is known and being worked on.

br,Ossi

[abhijeet_parihar]

Hi Experts,

I am getting this error for one of SAP GUI for HTML app. We have 1909 embedded deployment. The challenge is that this app in not rendering the screen. Where as there are other SAP GUI apps working fine. Any suggestions ?

Regards

Abhijeet

[sdfraga]

Hello,

Exactly same situation here. Just upgraded to FES 6.0 and now I have the same error in all applications.

Did someone manage to solve this?

Thank you

Sérgio

[DanielSchneider]

Hello Ossi,

we have exactly the same problem after upgrading from FES 4.0 to FES 6.0.

All our applications throw this error, regardles if it is a standard app or a custom app. Also regardless if it uses LPD_CUST in the target mapping or directly contains the path to the app.

Additionally to this issue we now need to run report /UI2/DELETE_CACHE_AFTER_IMP after we deploy some changes from WebIDE to our dev system. Otherwise the changes do not take effect (before the upgrade no report was needed on dev system). Therefore I think that we currently have problems with the cache buster mechanism.

I'm not sure though if the two issues are related. I'll let you know if we find a solution.

BR Daniel

[omakinen]

Hi Daniel!

Good to know that we are not alone. Now that some more testing has been done, we see that also standard apps throw this error. It's not limited to custom apps then.

Have you raised an incident to SAP? In any case, let's update this thread if a solution comes up!

br, Ossi

[DanielSchneider]

Hi Ossi,

yes I raised an incident to SAP. I'll update this thread if we have a solution.

BTW my other issue was solved: the cache buster does not work properly if LPD_CUST is used in the target mapping of tiles. Maintaining the path directly in the target mapping helps solving that issue.

BR Daniel