-
Notifications
You must be signed in to change notification settings - Fork 38
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
Please support Flutter 3.13 #160
Comments
along the same vein, dart 3 support would also be appreciated. great tool by the way, would love to see it stay up to date! |
Not from a lack of trying! Dart 3 has thrown some spanners in the works which were struggling to overcome at the moment |
Yes, thwre should be a beta version to test atleast... Its been silence
since march.. cant run new stuff
…On Mon, Oct 30, 2023, 3:01 AM Elliot Hesp ***@***.***> wrote:
Not from a lack of trying! Dart 3 has thrown some spanners in the works
which were struggling to overcome at the moment
—
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSHZH5G2S37U6R474FDYB272DAVCNFSM6AAAAAA6AHR3TGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGIZTOMZQGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Appreciate the effort! |
We can't ship a beta to test, since we can't get it working yet. There has been many, many hours pumped into this but still hitting some complicated brick walls. |
Ask majid hamdani for help. 😅
Atleast give a blog post about this... I thought you people abandoned the
project
…On Mon, Oct 30, 2023, 2:49 PM Elliot Hesp ***@***.***> wrote:
Yes, thwre should be a beta version to test atleast... Its been silence
since march.. cant run new stuff
We can't ship a beta to test, since we can't get it working yet. There has
been many, many hours pumped into this but still hitting some complicated
brick walls.
—
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSGVNGMAVSTPC47JSU3YB5Z3TAVCNFSM6AAAAAA6AHR3TGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUHAZTGMZTGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Any progress? you may contact VERY GOOD VENTURES |
Please see this issue: dart-lang/sdk#54468 |
Hey everyone, the issue mentioned by @Ehesp was closed 2 weeks ago. dart-lang/sdk#54468 |
Really? @invertase/zapp.run ***@***.***> ?
…On Tue, Jun 4, 2024 at 8:11 PM Marcelo da Silva ***@***.***> wrote:
Hey everyone, the issue mentioned by @Ehesp <https://github.com/Ehesp>
was closed 2 weeks ago. dart-lang/sdk#54468
<dart-lang/sdk#54468>
Maybe the blocker was solved and the editor can now move to the newer
dart/flutter versions? :)
—
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSEDCN5J7ZOQN7BQNKTZFXKIVAVCNFSM6AAAAAA6AHR3TGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXG44DIMJRHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi all, Although the fix landed upstream in the Dart SDK did fix that issue, it unfortunately then revealed another. We're actively working on ways to bring Zapp back to life via a different approach, using the latest Dart & Flutter SDK, in a way where there is much less risk of these breaking changes happening. |
Thanks for the update. kindly also mention in BLOG of the website, so
people stay connected.
…On Thu, Jun 6, 2024 at 4:58 PM Elliot Hesp ***@***.***> wrote:
Hi all,
Although the fix landed upstream in the Dart SDK did fix that issue, it
unfortunately then revealed another.
We're actively working on ways to bring Zapp back to life via a different
approach, using the latest Dart & Flutter SDK, in a way where there is much
less risk of these breaking changes happening.
—
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXJSCOVMPWTXGAB55KVELZGBFFJAVCNFSM6AAAAAA6AHR3TGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSGIYTSNJUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
it is too old
The text was updated successfully, but these errors were encountered: