BUG: having two instances of grape present makes the asset manager of the first "stop" working

Version: 0.16.44

What is the expected behavior?

I expect to have 2 separate instances of grape in one single page and being able to utilize the asset manager properly

Describe the bug detailed

I have initialized 2 instances of grape in a page with the config below

ar editor = grapesjs.init({
		fromElement: 1,
		container: "#{{varName}}",
		plugins: [...],
		styleManager: false,
	       noticeOnUnload: false,
	       storageManager: false,
               panels: {...},
               assetManager: {
			upload: '/api/handleEditorUpload',
			uploadName: 'files',
		},

what happens is that in the second instance of the editor, the asset manager is working fine. On the contrary on the first instance the asset manager seems to be kind of broken. In the image below, you can see what is shown when I try to use the asset manager on the first instance. Here I have uploaded an image but it is nowhere to be seen.

BUT the image seems to be handled on the asset manager of the other instance as well as all other images already uploaded...

there is no error to be seen either. Any idea why this could be happening?

UPDATE this seems to be an issue with setting the assetManager on the init config of the editor if I comment out the asseManager: {..} part, suddenly the editor behaves as expected. How can I config this property and have it working ? I need to do the image handling myself.