Hello
As i am facing this issue with some image elements and some image elements works fine…
Do you have any browsers extensions enabled? Eg adblockers etc?
Any errors/warnings in Dev Console?
Can you post a link to the project please and which entity is this on?
I doubt it is extension problem or what… Because some of them are working fine.
Here is console log…
In detail:
instrument.ts:129 Cannot find reference asset:texture:compress:compressionMode
(anonymous) @ instrument.ts:129
(anonymous) @ editor.js:60129
Editor.call @ editor.js:17074
addAttribute @ editor.js:67675
(anonymous) @ editor.js:67573
AttributesInspector @ editor.js:67572
DOM @ editor.js:82015
TextureAssetInspector @ editor.js:82305
(anonymous) @ editor.js:75569
AssetInspector @ editor.js:75565
(anonymous) @ editor.js:88370
(anonymous) @ events.js:37
Events.emit @ events.js:57
(anonymous) @ editor.js:17113
sentryWrapped @ helpers.ts:87
instrument.ts:129 Powered by PlayCanvas 1.39.4 5653326
instrument.ts:129 messenger connected
38instrument.ts:129 Elements will not get any input events because this.system.app.elementInput is not created
(anonymous) @ instrument.ts:129
set @ playcanvas-stable.js:52673
initializeComponentData @ playcanvas-stable.js:52956
addComponent @ playcanvas-stable.js:40719
processEntity @ editor.js:110384
createEntities @ editor.js:110442
(anonymous) @ editor.js:110458
(anonymous) @ events.js:37
Events.emit @ events.js:57
(anonymous) @ editor.js:41221
(anonymous) @ editor.js:41183
emitNone @ editor.js:19109
emit @ editor.js:19194
Doc.ingestSnapshot @ editor.js:22215
Doc._handleSubscribe @ editor.js:22279
Connection._handleBulkMessage @ editor.js:21686
Connection.handleMessage @ editor.js:21656
socket.onmessage @ editor.js:21556
connection.socket.onmessage @ editor.js:23278
instrument.ts:129 responseType: text being served with Content-Type: application/javascript
(anonymous) @ instrument.ts:129
_onSuccess @ playcanvas-stable.js:2051
_onReadyStateChange @ playcanvas-stable.js:2017
(anonymous) @ playcanvas-stable.js:1953
sentryWrapped @ helpers.ts:87
XMLHttpRequest.send (async)
(anonymous) @ trycatch.ts:281
(anonymous) @ instrument.ts:309
request @ playcanvas-stable.js:1963
get @ playcanvas-stable.js:1817
basisDownload @ playcanvas-stable.js:36233
basisDownloadFromConfig @ playcanvas-stable.js:36273
basisTranscode @ playcanvas-stable.js:36288
(anonymous) @ playcanvas-stable.js:36319
_onSuccess @ playcanvas-stable.js:2067
_onReadyStateChange @ playcanvas-stable.js:2017
(anonymous) @ playcanvas-stable.js:1953
sentryWrapped @ helpers.ts:87
XMLHttpRequest.send (async)
(anonymous) @ trycatch.ts:281
(anonymous) @ instrument.ts:309
request @ playcanvas-stable.js:1963
get @ playcanvas-stable.js:1817
load @ playcanvas-stable.js:36309
load @ playcanvas-stable.js:36843
handleLoad @ playcanvas-stable.js:34697
load @ playcanvas-stable.js:34731
load @ playcanvas-stable.js:37236
_bindAndAssignAssets @ playcanvas-stable.js:33609
patch @ playcanvas-stable.js:33488
patch @ playcanvas-stable.js:34797
_opened @ playcanvas-stable.js:37200
load @ playcanvas-stable.js:37242
_bindMaterialAsset @ playcanvas-stable.js:55161
onEnable @ playcanvas-stable.js:55087
_onHierarchyStateChanged @ playcanvas-stable.js:31556
_notifyHierarchyStateChanged @ playcanvas-stable.js:31523
_onInsertChild @ playcanvas-stable.js:17343
addChild @ playcanvas-stable.js:17312
insertChild @ editor.js:110360
processEntity @ editor.js:110411
createEntities @ editor.js:110442
(anonymous) @ editor.js:110458
(anonymous) @ events.js:37
Events.emit @ events.js:57
(anonymous) @ editor.js:41221
(anonymous) @ editor.js:41183
emitNone @ editor.js:19109
emit @ editor.js:19194
Doc.ingestSnapshot @ editor.js:22215
Doc._handleSubscribe @ editor.js:22279
Connection._handleBulkMessage @ editor.js:21686
Connection.handleMessage @ editor.js:21656
socket.onmessage @ editor.js:21556
connection.socket.onmessage @ editor.js:23278
Show 23 more frames
If i delete the element and add it then it works fine…
Should i do this?
EDIT:
I also come to know that… If i duplicate this then another element will will have same issue.
I already added you in the project.
Honestly not sure what is happening there 
Removing the image component and re-adding seems to ‘fix’ it. If you find a pattern or reproducible case for this, please let us know.
Side note: Please use checkpoints to keep a history of your work or offline backups. Accidentally deleting assets etc is not possible to recover.
Edit: Sorry, I may have screwed up the layout/data of the reverse and forward buttons 
I dont have any idea how this happen… When i come back to change ui at that time i realise that there is no image slot.
Ohh ok No worries… That was Duplicate project for forum purpose…
Here i copy pasted those components. And they are here without Image Slot
https://playcanvas.com/editor/scene/1114432
Maybe you can fork and test it out…
Just to check, does the workaround work for you?
Thanks @yaustar for taking look into main project…
Yes works this way
Yes this solution works!
But i am unable to reproduce that bug…
1 Like
Hello 
After long time i finally manage to recreate this issue.
Steps:
-
I created 2d screen and added 2 UI image entities.
-
Now in 1st image UI entity element I added “test tex.png” (texture) file.
-
Then i selected both UI image entities and added “test spr” (sprite file)
-
Now click on 1st ui element you will find there is no way to add remove or replace image from it.
Project URL: https://playcanvas.com/project/1157243/overview/image-sprite-issue
I hope it will help to resolve the issue…
1 Like
I also encountered this! Thanks for posting Ketan_ATA.
I found the same, it happened from duplicating image elements and switching to a sprite from a texture. Unfortunately mine was on a template and before I realized the issue had appeared, I’d applied it to all templates. Not a big deal, there were only 8 instances so I can update manually, but could be extremely frustrating in a case where someone had hundreds of instances and didn’t have a good checkpoint to return to.
1 Like
@kelsey Hello and Welcome!
I can understand it is really frustrating…
Letting you know about this @Albertos Maybe you can suggest some one from team…
Hopefully it will fix this in future… 
Yes I have seen the steps, thanks for that.
It’s easier for the team to track the issue on GitHub. They’re probably going to put it on the list to fix as well.
2 Likes
I found a GitHub issue that might be related to this, so I mentioned this topic.
1 Like