sap.ui.core.Fragment.load is never rejected

[iljapostnovs]

OpenUI5 version: 1.85.0

Steps to reproduce the problem:

1. Load non-existent fragment using sap.ui.core.Fragment.load

This issue is relevant not only for non-existent fragments, but e.g. network issues. If Fragment is not loaded because of the network, error never appears and the app just stays hanging in the busy state (if setBusy was used).

2. Promise is returned, however it's never rejected if error appears

What is the expected result?
Promise should be rejected in case of errors

What happens instead?
Nothing, promise stays in "pending" status forever.

Any other information? (attach screenshot if possible)
I believe that the issue starts in the sap.ui.core.Fragment.load:

↑ .catch is not implemented, but even if it would:

↑ reject is not implemented, but even if it would:

↑ .catch is not implemented, but even if it would:

.catch is not implemented, and here finally we have reject implemented:

[flovogt]

Hi @iljapostnovs,

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

All the best,
Florian

[H4ze]

Hi @iljapostnovs,

Thank you for your analysis. We created a fix which will propagate the promise rejection properly to the outer promise with commit c98e22f, internal code review 5118797 by @Thodd. The change should be available with release 1.87.

Best regards,
Johannes