-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: swa start --data-api-location causing Bad CPU type in executable #1685
Comments
Hi @bianbianzhu, which version of SWA CLI are you using? There was a possible similar issue #1560 recently which required a bugfix to be deployed on SWA CLI: Azure/static-web-apps-cli#718 |
You can get additional logging by using the following SWA CLI option per https://azure.github.io/static-web-apps-cli/docs/cli/swa#options
|
Hi @seantleonard, thanks for the help.
I was affected by the Thanks! |
hi @bianbianzhu, in order to see the error, could you please reshare the verbose logs when Something like: Thanks! |
Hi @Aniruddh25, the following is the the complete log from OS: [macOS] SWA CLI 1.14 Welcome to Azure Static Web Apps CLI (1.1.4) Getting config file options from swa-cli.config.json...
Checking if localhost:4280 is accepting TCP connections...
Cheers! |
hmm, no body else has the same issue as me? I thought M2 Pro was not so different from M1 |
Close and waiting for future demand. |
What happened?
OS: [macOS]
Version [Ventura 13.4]
Architecture: [arm64 (Apple M2 Pro)]
When running the command to start the SWA using
The following error occurred - Bad CPU type in executable
--data-api-location
sets theswa-db-connections
and declares where to run DataApiBuilder.exe to connect to the database.If I change the
options
flag to--api-locaiton
without the db connections, it works fine and no error is shown.Is there any way to support the new Apple silicon chip plz?
Version
0.8.49
What database are you using?
Azure SQL
What hosting model are you using?
Static Web Apps (SWA)
Which API approach are you accessing DAB through?
REST
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: