OpenUI5 version: 1.65.1
Browser/version (+device/version):
Google Chrome | 74.0.3729.108
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
https://openui5.hana.ondemand.com/test-resources/sap/m/demokit/orderbrowser/webapp/test/mockServer.html
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
What is the expected result?
That UI5 still works
What happens instead?
Uncaught (in promise) TypeError: i.parentChange is not a function
at f.m.setParent (ManagedObject-dbg.js:2647)
at f.m.setAggregation (ManagedObject-dbg.js:1959)
at f.setTitle (ManagedObjectMetadata-dbg.js:310)
at f.m.applySettings (ManagedObject-dbg.js:1171)
at ManagedObject-dbg.js:541
at f.constructor (ManagedObject-dbg.js:556)
at f.constructor (Element-dbg.js:143)
at f.constructor (Control-dbg.js:168)
at new f (Metadata-dbg.js:463)
at f.h._initDynamicPage (SemanticControl-dbg.js:97)
Any other information? (attach screenshot if possible)
It happens in the entire 1.65.1 Version of ui5
I don't get this error when I open the link, neither in Safari nor in Chrome 74. Looks like an inconsistency to me (because parentChange was introduced only recently).
Can you please check whether the issue still occurs after clearing the browser cache?
If cleaned the cache before. Ok now the Error doesn't occure anymore. Maybe some Issues with the new Version not correctly updated on the server.
I met with this issue too, probably not because the CACHE, but because U clear the CACHE, then the UI5 upgrade with some flaws(from 1.65.1 to higher) .
RESOLUTION should be:
find your app entry html such as index.html or app.html
then try to fix the version you are using like following...
<script id="sap-ui-bootstrap"
src="https://sapui5.hana.ondemand.com/1.65.1/resources/sap-ui-core.js"
data-sap-ui-theme="XXXX"
data-sap-ui-resourceroots='{"XXXX": "./"}'
data-sap-ui-compatVersion="XXX"
data-sap-ui-oninit="XXXXXX"
data-sap-ui-async="true"
data-sap-ui-frameOptions="trusted">
</script>
@bobowwb I can confirm that the i.parentChange is not a function problem occurred today on https://sapui5.hana.ondemand.com (only when not using a specific version).
This has now been resolved. You might again need to clear your browser cache.
Actually this problem caused us failure in our production environment because any page was not rendering correctly. Please ensure this never happens again.
@zygimantus more than sorry for that. But please don't use the unversioned URL for productive usage. This is explicitly mentioned and warned about in the version overview for SAPUI5:
Make sure that you always refer to a specific SAPUI5 version instead of using
the generic reference to the latest released version.
Use the generic reference for testing purposes only.
The same applies for openui5.hana.ondemand.com.
Alternatively, you can use the UI5 cache buster as documented here, but that results in less optimal caching.
@petermuessig anything to add?
@codeworrior, not sure why then WebIDE uses that link in SAPUI5 Project Wizzard if it is not stable, anyways thank you for your information!
Good question :(
Most likely the idea was to have _timeless templates_. But a simple inline comment ("please change this to a fixed version before productive usage") could save a lot of trouble.
At least, the "Walkthrough" tutorial contains the same warning, but only in the text, not in the source.
I'll suggest to add some comment to the sample code as well.
@bobowwb I can confirm that the i.parentChange is not a function problem occurred today on https://sapui5.hana.ondemand.com (only when not using a specific version).
This has now been resolved. You might again need to clear your browser cache.
Yes, I have tested that this fix is done.
Most helpful comment
@zygimantus more than sorry for that. But please don't use the unversioned URL for productive usage. This is explicitly mentioned and warned about in the version overview for SAPUI5:
The same applies for openui5.hana.ondemand.com.
Alternatively, you can use the UI5 cache buster as documented here, but that results in less optimal caching.
@petermuessig anything to add?