bootrom | build : the boot rom code can only be

I've had the same exact error. It's caused by Android Emulator 30.7.4 in combination with macOS Catalina. You can track the issue here

• https://issuetracker.google.com/issues/191799887
• https://issuetracker.google.com/issues/191805460

The work around that worked for me was upgrading to Big Sur.

Okey, solution was erease the content from autogenerated file, save file and build again...,

After several builds error appear again, and same procedure was success :D

Thanks all that tried to helped me if knows about root issue will be great!

1. Something might be broken with my Virtual Environments

The easiest solution is using a venv - it's standard library and thus the best baseline for virtual enviorments. (For completness it's worth mentioning that historically there have been a number of solutions for this.) As an example creating a venv with the PyCharm GUI is easy, it creates a new interpreter from the base Python interpreter optionally sharing its site-packages. The GUI lets you interface with PyPI to install aditional packages.

Eventually, it's worth learning to do the same using the command line, see venv — Creation of virtual environments. This boils down to 3 commands

1. Create the venv (since you have Python on your PATH)

   c:\>python -m venv c:\path\to\myenv

2. Activate the venv (this is OS specific, see the documentation)

   /bin/activate

3. After activating use pip to install any libraries you want

   pip install library_name

After having the venv created and activated it's ready to use on the terminal (inside or outside PyCharm), or you can use it with run configurations in PyCharm.

Now, in your case you are also using Anaconda, which manages the packages and the environments for you. But it's important to realize that what Anaconda does for the most part are the above steps wrapped in it's own GUI, see the similarities with Finding your Anaconda Python interpreter path.

Besides this, there's a hard rule that venvs should not be copied or moved. They have hardcoded paths inside them that will break. So, when you create a venv use it in the directory where you created it. The whole point of venvs is that if you break something you simply create a new one on-the-fly. Eventually, you'll want to write your own shell script to automate creating venvs.

1. Something might be broken with my PATH

It appears that the 8badf00d error message was triggered by an update to xCode or my Mac's OS. The app did start even though the message appeared so I just went along and have build a release APK for android without problems. I won't be able to test it for iPhone as of yet but would assume its somewhat the same.

Will post a short update after I have tested it for iPhone so I can confirm that the issue is with my Mac and not the actual app.