-
Notifications
You must be signed in to change notification settings - Fork 950
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
12.4.2 Flutter Web webframeworks experiment "Unable to detect the web framework in use" #6085
Comments
Hi @g-adorni-neting, thanks for reporting this issue. I was able to reproduce this. I encountered the same error when using v12.4.2 and v12.4.1 as you mentioned. After downgrading to v12.4.0, I was able to run Let me notify our team about this so that they can investigate. |
I experience the same issue in v12.4.3, but downgrading to v12.4.0 did not fix it for me. The weird thing is that note: the command worked for me until the latest update, maybe I miss a cache clearing step when downgrading? 🤔
|
Related: Easy to reproduce:
EDIT: Rolling back to Could this be related to 17eb321 ? This commit was added shortly after 12.4.0 was released, and, as far as I can see, is the only web-frameworks related commit since. |
For anyone still affected by this: |
I'm experiencing the same issue, but with Next.js framework. I can't resolve it with the latest version, and as mentioned in this discussion, version 12.4.0 works for me as well. For now, I can proceed, but I would like to see a solution to this problem. mac: 13.4.1 |
@andreasgrossmann yes, you are right. documentation is out dates and CLI also generates source by default. |
I have a Flutter Web project, up to version 12.4.0 by enabling web frameworks experiments I was able to deploy to Firebase hosting correctly.
By upgrading to 12.4.2 instead, the deploy or the firebase init with the same configuration gives me:
I also tried with version 12.4.1 and it gives the same problem. By downgrading to 12.4.0 everything goes back to working properly.
The text was updated successfully, but these errors were encountered: