Sdk: Dartium has expired

[xvrh]

Latest stable Dart version: 1.24
Dartium refuse to launch: "This version of Dartium has expired".

[sigi77]

Same here, I reinstalled Dart with Dartium, hoping a new Chromium binary will be installed, which was not the case

[pinnisi]

Same here

[sestegra]

As this version will stay the latest 1.x version, I suggest to remove this expiration.

[zoechi]

In TALK-general @dan-conachi mentioned

export DARTIUM_EXPIRATION_TIME=1577836800; ./chrome-wrapper

[passerbyflutter]

@sestegra Have any solutions on windows? Thanks you.

[sestegra]

@passerbyflutter See last comment, it should work on Window as well.

[passerbyflutter]

That works! Thanks!

[Stargator]

Someone on StackOverflow asked if there was a way to release a "final" version of Dartium that won't expire since Dart 2 doesn't use it and there will no longer be any updates to Dartium.

[johnpryan]

On a mac, you can use the launchctl command to set this as a system-wide environment variable:

launchctl setenv DARTIUM_EXPIRATION_TIME 1577836800

[rafikiadmin]

Dart is a superb development platform, but if Google is not going to support us... I would love to see someone from the Dart team respond here.

[zoechi]

@rafikiadmin there are easy workarounds. I don't see how this is a serious issue.

[rafikiadmin]

Ok. I guess that is true. I guess it is fine.

[kwalrath]

In dart-lang/site-www#962 @jooseplall reports being unable to use the workaround on Windows (windows 10). @passerbyflutter can you give us any tips?

[sigi77]

@kwalrath It works in my Windows 10. You need to set an Environment Variable in the system properties. After a reboot it should work.

[munkacsimark]

Solution on macOS:

1. Chromium app must be in /usr/local/Cellar/dart/1.24.3/
2. $ brew install libfaketime
3. Create a file /usr/local/bin/dartium-fake with following content:
   bash export DYLD_FORCE_FLAT_NAMESPACE=1 export DYLD_INSERT_LIBRARIES=/usr/local/Cellar/libfaketime/0.9.7_1/lib/faketime/libfaketime.1.dylib export FAKETIME="-15d" exec "/usr/local/Cellar/dart/1.24.3/Chromium.app/Contents/MacOS/Chromium" "$@"
4. $ chmod +x /usr/local/bin/dartium-fake
5. You can now run Dartium with dartium-fake command

[Stargator]

@rafikiadmin there are easy workarounds. I don't see how this is a serious issue.

Oh okay, so when we attract people to use Dart 1, right now. And Dartium doesn't work when they run tests, that's fine.

That's the kind of experience the Dart Team wants for newcomers.

No that's not the best experience for newcomers who hear about Dart 2 and want to try out the stable version of Dart. A fix should be released so that, at the very least, the first-time experience for potential users is the best it can be.

Otherwise, we can probably forget about growing this community and drop Dart, if we can't work to ensure the tools needed work as expected out of the box.

[tmst]

I was happy to overlook the missing Chrome VM. But this is just too much. I refuse to transpile and debug generated code. Looks like it's time for me and Dart, my last great hope for a decent web client development experience, to part ways.

[zoechi]

@tmst Have you even tried?
Works quite well already and they are still working on improvements.

[kwalrath]

Just to be clear, both www.dartlang.org and webdev.dartlang.org now feature the Dart 2 workflow, not the Dart 1.x workflow (which is the last time that Dartium was supported).

[Stargator]

@kwalrath But Dart 2.0 isn't released yet. So that's just plain confusing from a new developer experience, when they do to the download page and download the Stable version...it's Dart 1.24.3.

So....what good does having dartlang.org default to Dart 2.0 workflow when newcomers are downloading the only Stable version available which is Dart 1.0? That just makes it worst.

[kwalrath]

@Stargator You're right, Dart 2.0 isn't released on stable channel yet, but the Flutter SDK uses Dart 2, and of course Dart 2 is what's on dev channel releases of the Dart SDK. We strongly encourage everyone to switch to Dart 2 now, unless you have a really good reason for remaining on Dart 1.x.

I'll try to make the VM/web download pages more clearly feature downloading Dart 2.

[kwalrath]

I've created a PR to make the installation directions clearer (on both www.dartlang.org & webdev.dartlang.org): dart-lang/site-shared#23.

[kevmoo]

Closing now that Dart 2.0 is released.

[dnalbach]

This is a sad state of affairs for enterprise software projects that can't easily switch from Dart 1.x to Dart 2.x.

[zoechi]

@dnalbach do the workarounds not work for you?

[dnalbach]

No they do not, and having an expiration warning in a browser used primarily for development and testing that no end user would actually use seems unprofessional to me. Dart is a language, not a framework. This is being treated like a consumer product, but languages are business products, and this is tooling for a business product. We still use JVMs back to 6 for some of our enterprise projects, and Java has very strong legacy support.

Dart was promoted heavily and we bought into it for awhile, but it rapidly became a second-class citizen in Google's world and we have moved away from it as much as possible in new projects because of the way things like this have been handled.

[Stargator]

@dnalbach This is an effect of the mindset that people will quickly adopt the latest and greatest.

Sometimes organizations or projects are slow to adapt and it doesn't leave a good impression if one day the build no longer works because of something expired. Then that team/organization either have to upgrade their stuff or drop their use of the tool.

I can't blame you for the latter.

[dnalbach]

@Stargator I agree, my concern is that the timeframes for businesses and end consumers are dramatically different. If a new language is going to be treated like a consumer change/deprecation model, then it isn't going to be viable for most enterprises, who need years to adapt, not months.

[kevmoo]

I'm sorry for the pain this has caused. Maintaining Dartium had become literally impossible given the Chrome team's evolution of the browser. Dropping it (and moving to the dev compiler model) actually means it's easier for us to support customers long-term since we no longer have to coordinate with such a large dependency.

[rinick]

I'm sorry for the pain this has caused. Maintaining Dartium had become literally impossible given the Chrome team's evolution of the browser. Dropping it (and moving to the dev compiler model) actually means it's easier for us to support customers long-term since we no longer have to coordinate with such a large dependency.

not supporting it is one thing. but stopping people from using it unless they can find some workaround themselves , that's totally different.

[kevmoo]

Time limiting the browser was mandated by the Chrome team, I believe. We wanted to push folks away from running a Chrome browser that wasn't being actively patched

[dnalbach]

I understand, but that's consumer thinking. The only people using Dartium are developers, and it doesn't make sense for that audience.

[Stargator]

@kevmoo Thanks for the insight that the time limiting was mandated by the Chrome team. It's understandable that you could only work within the constraints given to you.

Does that mean that even if the version of Dartium was the same, you couldn't just reissue it with a new expiration for at least another year?

[kevmoo]

Does the suggestion at https://github.com/dart-lang/sdk/issues/33580#issuecomment-400978229 not work?

We don't have the ability to build Dartium any more, sadly...well, it'd take a heroic effort to get everything working so we COULD build Dartium again