is your question: “why is it necessary to be signed in to my expo account in eas-cli when doing a local build while offline? is there any way to get around this?”
One of the reasons for the expo is to ensure that the the project does exist, but if it is doing an EAS build it doesn’t publish anyway so why would the need to check the existence of the project still be needed?
I did a search on your writing of the question but I didn’t see it either.
There is no technical reason why it shouldn’t be possible, but
It’s a lot of work to implement. Local builds are not on par with cloud builds, but they still integrate with a lot of cloud functionalities e.g. credentials management, that we would need to handle for anonymous user.
There is no real use case for that, even if you do not use any cloud functionality eas provides, then you still wouldn’t be able to run actual build without internet even with cache there are parts of the build process that would still need to download sth.
offline no, behind corporate firewall there shouldn’t be any problem on eas-cli side, it respects proxy configuration.
I’m not sure how configuration looks like for gradle/npm/cocoapods behind VPN, but at this point it’s the same class of problem as you would have when building a react-native app.