Local Instance MIT App inventor Not connecting

[Abbas_Gasri]

Hello Guys I hope everything is alright with you I'm Using MIT App inventor local instance compiled using ant command as usual everything works just fine except Companion not connecting even though I checked the Legacy connection note that It is working just fine until I add some assets (extension or something ) I tried every possible that I'm aware of to fix it but No Success ...Thank you Very much Dears

[vknow360]

@Abbas_Gasri

It is working just fine until I add some assets (extension or something

Did you reset the connection after adding files and then reconnected?

[Abbas_Gasri]

Yeah It is the same Result if you have any suggestions please Help the problem occurs when I Upload anything to the server

[dora_paz]

Maybe caused by a firewall or antivirus ?

[Abbas_Gasri]

Neither antivirus nor firewall are ON and When I use the offline version of Rumiro AND original MIT (online) It is working normal

[dora_paz]

Maybe this might help

Has anyone else has had or does have the error that assets can not be loaded?

Did you watch the video here? Yes, you need to temporarily uninstall AI2 online Companion or use another test device/phone like I do. One for AI2Online and one for AI2Offline (if possible with the same Android version). In addition, all .AboutScreen blocks must be removed from all screens in your projects (before importing them to AI2Offline) and there must also be no text for "AboutScreen" in the designer (the fields must be empty). Note: The minSdKVersion is 19 for AI2Offline and not 7 a…

[ewpatton]

On master, assets are now loaded by the companion rather than being pushed to it from the web browser. You will need to use -a 0.0.0.0 when running the dev server to listen on all IP addresses and then point your browser at the network IP address of your computer to access App Inventor. The App Inventor service will send this IP to the companion, which will use it to retrieve the assets over the network. By specifying localhost:8888, the companion ends up trying to access a non-existent service on the phone/tablet running the companion, which is why you get the error you see in the screenshot.