Fiori Approve All app rendering issue

Question

Hi,
I have a strange issue with the the Fiori Approve All app (ui5_ca_all_apv) when rendering in any desktop browser. I have tried IE9, Chrome and Firefox. What happens is it doesn't seem to load the css properly. The UI5 runtime on the system is 1.22.2
On first load I usually get the following:
Then after refreshing any number of times, sometimes once sometimes 10 times or more, I eventually get it to load.
However when running it through Ripple, a mobile emulator plugin for chrome, it always works first time.
I have looked at the console logs in all browsers, and there are no errors reported in any browser.
I have tried a few other Fiori apps, most work but there are a few others which behave the same.
This is also not specific to my desktop as this is also happening for other users.
Anyone using this app already and had similar issues?
Any help would be appreciated.
Thanks,
Brad
Tags edited by: Michael Appleby

Answer 1

Hi Masa,
I'm not using a custom theme, just the default theme, which is supposed to be blue crystal however on failed attempts to load, it appears to try and load gold reflection.
See this screenshot when it fails to load:
And after refreshing a few times it successfully loads and shows the blue crystal theme. see below:
Which made me think about passing the theme in as part of the url using this parameter: &sap-theme=sap_bluecrystal
This seems to fix the problem and it loads perfectly first time everytime now.
However, is this a proper solution? Should you need to pass the theme through the URL, is it not defined within application ui5_ca_all_apv?
I took a look at the code for the ui5_ca_all_apv where it supposedly sets the theme to sap_bluecrystal:
// startup shell before UI5
  var oScript = sap.ca.common.uilib.bootstrap.createScriptTag("/sap/public/bc/ui2/shell-api/sap/ui2/shell/shell.js");
  oHead.appendChild(oScript);
  var bDebugMode = /sap-ui-debug=(true|x|X)/.test(window.location.search);
  //Check local storage (modified via UI5 technical info dialog)
try { //Necessary for FF when Cookies are deactivated
        bDebugMode = bDebugMode || (window.localStorage.getItem("sap-ui-debug") == "X");
} catch(e) {}
  var sUI5Url = "resources/sap-ui-core" + (bDebugMode ? "-dbg" : "") +  ".js";
  var oScript = sap.ca.common.uilib.bootstrap.createScriptTag(sUI5Url);
  oScript.id="sap-ui-bootstrap";
  var sUilibs = "sap.m, ";
  if (!sap.ca.common.uilib.bootstrap.applicationSettings.bNoSapMe){
  sUilibs = sUilibs + "sap.me, "
  sUilibs = sUilibs + "sap.ui.commons, sap.ca.common.uilib";
  oScript.setAttribute("data-sap-ui-libs", sUilibs);
  oScript.setAttribute("data-sap-ui-theme", "sap_bluecrystal");
  oScript.setAttribute("data-sap-ui-xx-bindingSyntax", "complex");
  oScript.setAttribute("data-sap-ui-oninit", "sap.ca.common.uilib.bootstrap.onUI5Init();");
  oHead.appendChild(oScript);
Do you think this is a bug? Or should I just go with setting the theme as a URL parameter?
Thanks for your help!
Cheers,
Brad