sap.f.ShellBar: Profile Button not visible after Rendering of ShellBar (1.71)

[uifivvy]

What is the issue and how can we reproduce it?

1. Open the sample https://plnkr.co/edit/KMxp2RSXI4GsZlf0?open=lib%2Fscript.js&preview
2. Click on "Preview"
3. Issue: The sap.f.Avatar Profile is not visible in the ShellBar

Error:

The sap.f.Avatar is not visible, after the ShellBar is rendered (after a timeout of 1000ms).
If you delete the timeout in the code, the Avatar is visible.

Expected behavior:

The sap.f.Avatar shoud be visible after the ShellBar is rendered.

Which OpenUI5 version is your project targeting?

1.71

Is the issue device- or browser-specific?

No response

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[NHristov-sap]

Hello @uifivvy ,
Thank you for sharing this finding. I've created an internal incident DINC0766961. The status of the issue will be updated here in GitHub.

Best Regards,
Nikolay hristov

[plamenivanov91]

Hello @uifivvy ,

Than you for the input.

I investigated the issue and unfortunately it's not as trivial as it looks. It involves aggregation forwarding and the fix will be sort of complex and volatile and definitely not a good idea to make it in our long term 1.71 code line.

From a 1.84 (the next longterm code line) we use sap.m.Avatar and the issue is no longer reproducible.

For your use case though, I prepared a workaround which uses some of our private APIs and it looks as follows.

onInit: function() {
	var oShellBar = this.getView().getContent()[0];

	setTimeout(function () {
		oShellBar.setProfile(new Avatar({initials: "UI"}));
		// Workaround: Trigger overflow toolbar update for dynamically set profile
		oShellBar._bOTBUpdateNeeded = true;
		oShellBar._assignControlsToOverflowToolbar();
	}, 1000);
},

Please let us know if this is sufficient workaround fix for you.

Regards,
Plamen Ivanov

[uifivvy]

Hello @plamenivanov91,

thanks for your feedback. Can we use this workaround for production use?

Background of this issue is that our customers use different UI5 versions, some are using 1.71, some are using newer versions.
So we load the Avatar control depending on the used version. We use the asynchronous call sap.ui.VersionInfo.load to determine the used version, if the version is 1.71, we use the control sap.f.Avatar, loading via asynchronous call sap.ui.require. Otherwise we use the sap.m.Avatar. So the workaround would only be necessary for the 1.71 case (and only if the customers don't use the Fiori Launchpad integration).

Kind Regards,
Julia

[plamenivanov91]

Hello @uifivvy ,

With the provided sample, the workaround is needed only for 1.71. From 1.84, you can use the sap.m.Avatar without the workaround.

You can deploy the workaround for the 1.71 apps and confirm if it works for you too.

Regards,
Plamen Ivanov