Meteor 0.9.4 Release Candidate

[Oleksandr Stubailo]

Hi everyone,

We have put together a whole lot of cool new features and improvements into a release candidate for 0.9.4, the next version of Meteor. Thank you for trying out the preview releases in the last week - we have added some improvements based on your feedback. Please try the RC and give us feedback for the release! Run it with the following command:

meteor --release 0.9.4-rc.1

0.9.4 includes a new “Todos” example app built by our friends at Percolate Studio, which is replacing the old todos app. It looks great on desktop and mobile, so try running it on iOS and Android! You can create the app with this RC by typing the usual command: meteor --release 0.9.4-rc.1 create --example todos. We will keep improving this example app over time, but we think it’s already an awesome example of a useful and polished cross-platform app.

Here’s a list of some of the things that are new since 0.9.3:

New Features

1. You can debug your server-side code with a new meteor debug command that launches node-inspector for you.
2. You can now run Velocity tests from the command line using meteor run --test.
3. There is a convenient new API to specify your mobile app’s metadata, icons, splash screens, and PhoneGap/Cordova plugin settings with a new special file: /mobile-config.js. This should significantly reduce the situations that require a cordova build override directory. See the docs here: http://0.9.4-pre.11-docs.meteor.com/#mobileconfigjs
4. The new Todos example app.

Improvements

1. A rework of how app code is run in PhoneGap, substantially improving the startup time and overall speed of Android apps. There are also several other improvements and bug fixes to Meteor PhoneGap/Cordova integration.
2. Improved hot code push on iOS and Android, including fixing a bug where the mobile-server setting wouldn’t be saved across hot code pushes.
3. Reduced memory usage from mobile hot code push.
4. Huge speed improvements to the package system constraint solver, making adding and publishing packages much faster.
5. Some other small bug fixes, improvements and pull requests.

Backwards-Compatible API Changes

1. Improvements to the API for the password reset, email verification, and account enrollment flows, making it easier for developers to build their own version of accounts-ui. The new methods allow you to register callbacks to be fired when users visit the links in emails generated by accounts-password:

   1. Accounts.onPasswordResetLink
   2. Accounts.onEmailVerificationLink

   3. Accounts.onEnrollmentLink

      Check out the docs at: http://0.9.4-preview-docs.meteor.com/#Accounts-onResetPasswordLink

2. Package.registerBuildPlugin has been added to the public API, with some small backwards-compatible improvements. Check out the docs at: http://0.9.4-preview-docs.meteor.com/#Package-registerBuildPlugin
3. Improvements to the templating API, including:
   1. Deprecation of the Template.name.helperName = function () {...} syntax in favor of Template.name.helpers({ ... }) syntax.
   2. Renaming UI.dynamic, UI.contentBlock, and UI.elseBlock to Template.dynamic, Template.contentBlock, and Template.elseBlock. See the docs for more details: http://0.9.4-preview-docs.meteor.com/#template_dynamic
4. The unipackage.json file inside built packages has changed to isopack.json, and the file format has been updated to be more forward-compatible.
5. Moved .meteor/cordova-platforms to .meteor/platforms in anticipation of platforms other than ios and android in the future. The old file will be automatically migrated when you run your app with the new release.
6. To complement the Velocity test runner, we have added a new debugOnly flag to Package.describe. When you use this flag, your package will only be bundled and used in development mode, and will not be shipped to the client in production. Use it like this: Package.describe({ debugOnly: true });

Good luck, have fun!
Sashko

​

[Lauricio Su]

Hi,

Was not able to update a 0.9.4-pre.11 project by running meteor update —release 0.9.4-rc.1, got Your packages are at their latest compatible versions. But manually changing the release  to 0.9.4-rc.1 in release file and running meteor upgraded all the packages as usual:

  upgraded facts from version 1.0.2-pre.2 to version 1.0.2-rc.0

  upgraded accounts-password from version 1.0.3-pre.2 to version 1.0.3-rc.0

  upgraded livedata from version 1.0.11-pre.2 to version 1.0.11-rc.0

  upgraded session from version 1.0.3-pre.2 to version 1.0.3-rc.0

  upgraded facebook from version 1.1.1-pre.2 to version 1.1.1-rc.0

  upgraded spacebars-compiler from version 1.0.3-pre.2 to version 1.0.3-rc.0

  upgraded blaze from version 2.0.2-pre.2 to version 2.0.2-rc.0

  upgraded ordered-dict from version 1.0.1-pre.2 to version 1.0.1-rc.0

  etc...

[Jonathan Perl]

Out of curiosity, why are the icon keys "iphone-2x", "iphone-3x", "ipad-2x" using dashes where everything else uses underscores including the ios splash keys "iphone_2x"?

[Jonathan Perl]

audit-argument-checks is causing Error: Did not check() all arguments during publisher 'meteor_autoupdate_clientVersions'

[Randell S. Hynes]

Update to 0.9.4-rc.1

Cordova build now outputs *-release-unsigned.apk (that doesn't install) instead of previous *-debug-unaligned.apk (which installed). 

[Jan-Hendrik Mangold]

Since meteor 0.9.4-pre I am having a weird issue having todo with ROOT_URL and “Client Modified refresh” where ROOT_URL is dropped in the refresh and replaced with http://localhost:port 

TL;DR:

I am developing several Meteor apps on my Mac Pro that need to be accessible for outside testers, so I installed Phusion Passenger to nicely proxy to my Meteor devel apps. It works GREAT

Since the apps are run with SetEnv PASSENGER_APP_ENV development code edits are handled just as if I were to start my app with the meteor command. I also pass in a ROOT_URL of course, so my accounts-google is working, etc

When the app first starts all is fine, but as soon as I change some client code, and the server log shows “Client modified — refreshing”, what ever gets pushed to the client suddenly replaces the ROOT_URL with the internal localhost:port 

<script type="text/javascript">__meteor_runtime_config__ = {"meteorRelease":"MET...@0.9.4-rc.1","ROOT_URL":"http://localhost:7515","ROOT_URL_PATH_PREFIX":"","appId":"292hsh1elk3t7ijggj7","autoupdateVersion":"1f6536446f08961fd27ffdc1289d696db9718b33","autoupdateVersionRefreshable":"8db3ba58457a28b5c1ecb94b52e12423dbef32a1","autoupdateVersionCordova":"457aa300bf86ef490d0db4f861ad0713b8bdde2b","DDP_DEFAULT_CONNECTION_URL":"http://localhost:7515"};</script>

which of course does not work. When I restart the app on the server it looks like this, which makes more sense (I replaced the real ROOT_URL with http://my.example.com)

<script type=“text/javascript”>__meteor_runtime_config__ = {“meteorRelease”:”MET...@0.9.4-rc.1”,”ROOT_URL”:”http://my.example.com”,"ROOT_URL_PATH_PREFIX":"","appId":"292hsh1elk3t7ijggj7","autoupdateVersion":"a916b8ec96eab909c9d3b1615cdfaaac178d4a30","autoupdateVersionRefreshable":"633767789135ced4bd80afa3374a51e1d08b5ab8","autoupdateVersionCordova":"457aa300bf86ef490d0db4f861ad0713b8bdde2b"};</script>

This is 100% reproducible. If I change code on the server, and meteor detects the code change and restarts the server portion, this does not happen.

I have other Meteor apps pre-0.9.4 deployed the same way, and they DO NOT exhibit this problem, therefore I believe this is a regression with 0.9.4

Should I open a GitHub issue for this?

Jan

[Slava Kim]

Thanks Jon, made the keys consistently use underscores everywhere on devel.

[Jan-Hendrik Mangold]

On Oct 8, 2014, at 8:57, Jan-Hendrik Mangold <jam...@gmail.com> wrote:

This is 100% reproducible. If I change code on the server, and meteor detects the code change and restarts the server portion, this does not happen.

I have other Meteor apps pre-0.9.4 deployed the same way, and they DO NOT exhibit this problem, therefore I believe this is a regression with 0.9.4

Should I open a GitHub issue for this

Unfortunately this can not be reproduced with 0.9.4-rc1 running in standalone mode, so it has to be a combination of Phusion Passenger and the Meteor 0.9.4-rc1 and how it signals “Client modified — refreshing”

The only workaround I found is to add the ROOT_URL environment var to 

.meteor/local/build/programs/ctl/start.sh

Even though this is admittedly Passenger specific, I will still add a GitHub issue because it is also 0.9.4-rc1 specific, because this does not happen with Passenger and 0.9.3

[Emily Stark]

Hi Jan,

Thanks for the report! This has been fixed on the release branch; we'll have the fix out in the next RC.

Emily

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

[Jan-Hendrik Mangold]

On Oct 8, 2014, at 15:22, Emily Stark <em...@meteor.com> wrote:

Thanks for the report! This has been fixed on the release branch; we'll have the fix out in the next RC.

Phew :)

[Randell S. Hynes]

Slava pointed me in the right direction. Now need to add --debug switch to meteor build command.

[Ekaterina Kuznetsova]

Lauricio Su: I can't reproduce your issue -- just creating an app with 0.9.4-pre.11 and updating it works fine; added a bunch of packages that you might be using (ex: accounts-facebook) and that works too. Can you run 'meteor list' and tell me the output? I need a bit more information to reproduce this. (Feel free to email me privately at ekate@meteor if you don't feel comfortable sharing with the list).

Thanks!

- Ekate

[Lauricio Su]

Hi Ekate,

I downgraded the project to pre.11, but was not able to reproduce it, project updated normally, but then i went through my terminal history and found that one of the hyphen characters in --release somehow (perhaps when i copied it form google groups) got converted to em dash  0x2014 instead of  hyphen-minus 0x2D and thats what caused it. Sorry about that, was a bit tired at the time :/

[Sashko Stubailo]

Hi again,

Thanks for the replies about the first RC! We have fixed many of the bugs you reported in the last few days and built a new RC. Special thanks to everyone who tried the release and reported issues!

Try the new release candidate with meteor --release 0.9.4-rc.5.

Here are some of the fixes in the new release:

1. Made mobile-config.js icon/splashscreen key names consistent by changing all dashes to underscores. See the new key names here: http://0.9.4-rc.5-docs.meteor.com/#App-icons
2. Fixed bug where meteor_autoupdate_clientVersions didn’t pass audit-argument-checks
3. Fixed issue where ROOT_URL was not maintained across hot code push when running Meteor with Phusion Passenger
4. Made the todos example app faster on the default Android browser

There’s a new docs page for this RC at http://0.9.4-rc.5-docs.meteor.com/.

Thanks,
Sashko

[Nick Martin]

Hey all,

Just pushed another RC for your testing pleasure. Run it with:

  meteor --release 0.9.4-rc.6

Notable change since since -rc.5:

- Add support for running behind firewalls. The meteor tool now uses the standard `HTTPS_PROXY` environment variable when making connections to the package server.

- Fix crash when trying to search or show packages with wrapped version numbers (versions with `_`).

- Fix regression in `meteor bundle` where it would output a directory instead of a plain tarball.

- Allow any number of spaces in || constraints in package versions.

Give it a whirl this weekend, and let us know if you notice any issues.

Thanks!

-- Nick

--

[Jan Hendrik Mangold]

can it be that 0.9.4 defines a global UI/Template helper called url?

I have a collection with images in it, and every document has a url field. 

After upgrading to 0.9.4-rc.6 my site would not longer display the images

{{#each images}}
<img src="{{url}}">
{{/each}}

The above would assign the web sites ROOT_URL to every image src. I had to change it to 

{{#each  images}}
 <img  src={{this.url}}>
{{/each}}

for it to work again.

[Paul Cuciureanu]

I was stumbled by {{this.url}} vs {{url}} issue as well. Seems like some default overriding behaviours - are these documented somewhere?

Paul Cuciureanu

--

[David Greenspan]

Weird, I don't recognize "url" as any sort of reserved or built-in helper.

[Randell S. Hynes]

iron packages use url and this.url, although I can't imagine how it would be available outside that scope.

I did have an issue with the Iron Progress package when I tried rc.6 this AM. It was like it picked up the old Meteorite version of the package. Had to go back to 0.9.3.1 and up rc.5 to continue work.

I was thinking that I may had the same issue as Lauricio with the em dash for the --release switch. Dunno.

[Jan-Hendrik Mangold]

On Oct 11, 2014, at 16:07, David Greenspan <da...@meteor.com> wrote:

> Weird, I don’t recognize "url" as any sort of reserved or built-in helper.

it is part of the new iron:router. I just created a new project with 0.9.4-rc.6 and as soon as I added iron:router

added iron:location at version 1.0.0-pre3
added iron:dynamic-template at version 1.0.0-pre3
added iron:router at version 1.0.0-pre3
added iron:layout at version 1.0.0-pre3
added iron:middleware-stack at version 1.0.0-pre3
added iron:url at version 1.0.0-pre3
added iron:controller at version 1.0.0-pre3
added iron:core at version 1.0.0-pre3

the global {{url}} helper showed up. Except that I can’t seem to find it in the iron:router source

[Slava Kim]

Perhaps it is in iron:url?

--
You received this message because you are subscribed to a topic in the Google Groups "meteor-talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-talk/9yYAwy23d3M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-talk...@googlegroups.com.

[Jan-Hendrik Mangold]

On Oct 11, 2014, at 16:44, Jan-Hendrik Mangold <jam...@gmail.com> wrote:

it is part of the new iron:router. I just created a new project with 0.9.4-rc.6 and as soon as I added iron:router

 added iron:location at version 1.0.0-pre3
 added iron:dynamic-template at version 1.0.0-pre3
 added iron:router at version 1.0.0-pre3
 added iron:layout at version 1.0.0-pre3
 added iron:middleware-stack at version 1.0.0-pre3
 added iron:url at version 1.0.0-pre3
 added iron:controller at version 1.0.0-pre3
 added iron:core at version 1.0.0-pre3

the global {{url}} helper showed up. Except that I can’t seem to find it in the iron:router source

it is not a helper, but part of the page context in a Route. Of course I don’t believe that simply deleting it is a good idea.

Router.route('/', function () {

delete(this.url);

this.render('hello');

});

[Nick Martin]

Thanks for the report, Serge!

I think I see the error and how to fix it, but I'm not quite sure how it managed to be triggered. Can you send me your __meteor_runtime__config__ (curl http://yoursite and look in the <head> block)? Are you manually setting the APP_ID environment variable? What version of Meteor did you use to build the app that installed on the phone? (ie, is this a 0.9.2 or 0.9.3 client trying to update to 0.9.4-rc.6, or from -rc.6 to -rc.6?)

Thanks,

-- Nick

On Sun, Oct 12, 2014 at 10:23 AM, Serge Ovchinnikov <sovc...@gmail.com> wrote:

Running meteor rc.6, mobile hotcode push is not working for me anymore. A validation match of some kind appears to be failing.

When mobile client is started on the device I see the below on the server - the updates that went to the server are not pushed down to the client. Same issue both with iOS and Android. 

[xx.xx.xx.xx] Exception from sub sZe9lDMupHv8hhXRP Error: Match error: Failed Match.OneOf or Match.Optional validation

    at checkSubtree (packages/check/match.js:240)

    at check (packages/check/match.js:32)

[xx.xx.xx.xx]     at Meteor.publish.is_auto [as _handler] (packages/autoupdate/autoupdate_server.js:140)

    at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1594)

    at _.extend._runHandler (packages/ddp/livedata_server.js:943)

    at _.extend._startSubscription (packages/ddp/livedata_server.js:769)

    at _.extend.protocol_handlers.sub (packages/ddp/livedata_server.js:582)

    at packages/ddp/livedata_server.js:546

Sanitized and reported to the client as: Match failed [400]

On Tuesday, October 7, 2014 11:23:24 PM UTC-7, Oleksandr Stubailo wrote:

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[Nick Martin]

Hi Serge,

Can you please try 0.9.4-rc.7? It contains what I hope is the fix to the issue you're seeing.

Thanks,

-- Nick

[Slava Kim]

Jordan,

Here is what going on: when the Meteor server is starting, it loads all the server scripts one-by-one. It should be sufficient to step through the code a little bit to load all the scripts. As an alternative workaround, you can put a `debugger;` statement on any line of your code and expect the debugger to stop there when you "unpause" the execution.

On Saturday, October 11, 2014 8:03:21 PM UTC-7, Jordan Baker wrote:

Debugger Feedback:  I see the message "Your application is now paused and ready for debugging!" but when I check in the debugger I can't see any of my source files in the Sources tab.  Only if I unpause does it load them.  Unfortunately the bug I'm trying to solve is happening during initialization and I don't ever get a chance to set a breakpoint.

On Tuesday, October 7, 2014 11:23:24 PM UTC-7, Oleksandr Stubailo wrote:

[ega radiegtya]

I have an Issue.

The generated .apk file cannot be installed in my android phone. It's not showing error too, my android just said "Application not installed".

Any idea about this?

[Randell S. Hynes]

If you're using meteor build add the --debug switch. That will build an unaligned.apk that should install. I had the same problem and Slava pointed me in the right direction. If you're not using meteor build, I dunno.

[Jan-Hendrik Mangold]

This is/was an iron:router issue and will be fixed in the next update

See https://github.com/EventedMind/iron-router/issues/906

[ega radiegtya]

Hi Randell,

Thanks for the answer. But why should using --debug mode? It means that our code is not minified and I think the app will be slow.

Any idea?

[ega radiegtya]

Btw now my android file can be installed, but in unminified or debug version which is still not good I think. 
The other bad news is loading time in Android still too long I think. It's about 5 second loading with very simple crudss app. (in meteor 0.9.3 the loading screen time is about 10-17 sec)

And the good news is, this Meteor 0.9.4-rc now able to use localstorage (ground:db from Raix) in Android perfectly when offline (0.9.3 cannot do this).

Thanks for meteor team for the hard work. We will looking forward for the good news.

[Randell S. Hynes]

It seems to be all or none with the --debug switch on meteor build. Creates unminified web and unaligned APK.

You can use meteor run until you're ready to deploy.

[Slava Kim]

Yes, we reworked the way the content is served on the mobile devices.

On my android phone the startup takes maybe a second, on my emulator it is 2 seconds. What device are you testing on that you get 5 seconds delay?

[Caio Pinna]

Slava,

Same issue here, about 4 seconds to start on Galaxy Note 8.

Tks 

[ega radiegtya]

Hi Slava,

It's LG Optimus.

Btw how about the --debug problem? I am still doesn't get it why need debug mode to build android apps.

Is this still reworked? THanks

Regards

[Slava Kim]

The --debug option is implemented by design. When building an apk in a `debug` mode, the apk is expected to be debugged (thus `debuggable` attribute is set to true) and so is JS - it would be hard to debug the JS on device if it was minified (when you connect to it from Google Chrome debugger for example).

Running debug apks in production is obviously not recommended and in fact, Google Play Store doesn't allow anyone to upload debuggable apks to production.

--
You received this message because you are subscribed to a topic in the Google Groups "meteor-core" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-core/9yYAwy23d3M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-core...@googlegroups.com.

To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

[ega radiegtya]

@Slava 

I know that already, the question here is why I can't build my app using this command:

meteor build .build --server 192.168.1.168:3007

when using above command, my apk file cannot be installed. It said that "Application not installed".

 

it was only able to be build using this debug command which is not recommended and of course I don't wanna use this

meteor build .build --server 192.168.1.168:3007 --debug

but using this command, my apk file able to be installed

Thanks

[Slava Kim]

The "production" level APK cannot be installed on devices as-is, because it is not signed and requires more preparation before you can submit it to the Play Store. You can read more about it in Google documentation and a short set of instructions on our wiki: https://github.com/meteor/meteor/wiki/How-to-submit-your-Android-app-to-Play-Store

[ega radiegtya]

@Slava

Oh I see, Thanks for the kind answer.

It means that the previous meteor version (0.9.3) build is a debug mode too although without using --debug?

Because I can build in 0.9.3 without debug mode, and able to install it directly without app store.

Thanks

[Nick Martin]

Great! Glad to hear it.

Thanks for your clear report, helpful debugging info, and quick response!

Cheers,

-- Nick

On Sun, Oct 12, 2014 at 2:43 PM, Serge Ovchinnikov <sovc...@gmail.com> wrote:

0.9.4 - rc.7 resolved the issue. Magic. Thank you!  

Steps performed - as a fyi: 

Updated local build - pushed to server - started mobile client on device (0.9.4-rc6 build on android & 0.9.4-rc5 build on iOS) - both clients updated to new app version with no errors on server. 

Serge

[Charles Holbrow]

Is there any way to get the client's console.log output when with '$ meteor run android-device'? It's really easy with '$ meteor run android', and its hard to debug without even console.log available.

Also, hot code push seems to work inconsistently on my android device - It's hard to tell why this is the case, because I don't have any access to the debug output, but I think that sometimes when my app throws an exception it then it looses contact with the server.  When this happens, the only way to get the app to reload is to ctrl^c the server, and run '$ meteor run android-device' again. The back button on my android device will trigger a re-load, but it never includes the most recent changed I made to the client code. Is this the expected behavior? It's hard to tell when a change I made to the client code is working, because I'm can't be sure if the code push was successful.

It would be great to have some way to force the app to reload from an android device.

[Kelly Copley]

console.log messages will be dumped into your devices logcat

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.

To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

[Randell S. Hynes]

@Ega, I just noticed after upgrading to the 0.9.4 release that the ant-build folder contains a debug APK without using the meteor build --debug switch. It installs fine on my Android tablet.

[Slava Kim]

Hey Charles. If your device is connected to the computer with a usb cable (with which you installed the test app in the first place), Meteor will print all logs from the device to the same terminal window (logs are stored in logcat, but Meteor tails them by default). Note that there is quirk of Cordova Android: only first argument of `console.log` will be printed. If it is not the case, then it is a bug.

[Charles Holbrow]

Thanks Slava - Sounds like there is a bug where client side console.log is not tail'd by Meteor when I'm using an android device. 

I have a Huawei Ascend with Android 4.4, and I'm running OSX 10.8.5. 

For other android newbs such as myself, you can access logcat with adb, installed at this location:

$ ~/.meteor/android_bundle/android-sdk/platform-tools/adb logcat