Problem just after uploading the project

[ziedmahdi]

Hello,

I tried to deploy as usuall but the upload alwas freeze at 92 %

After visiting this github issue, I upgraded my cli and retried to deploy again.

Now, the upload is finished but I m getting other errors.

I tried changing my runtime to meteor but still get errors.

I noticed in logs

Using Meteor 1.3.2.4.

but my app is meteor 1.2.1

Welcome to Modulus
You are logged in as commitaction
Please choose which project to use:
  1)  Commit Action - Production  Meteor
  2)  Commit Action - Staging     Node.js
[?] project 1
Selecting Commit Action - Production

Compressing project...
3.5 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Meteor runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Now using node v0.10.41 (npm v3.8.6)
Initializing Meteor environment.
Using Meteor 1.3.2.4.
Installing root package.json dependencies.
npm WARN commit-action@1.0.0 No repository field.
npm WARN commit-action@1.0.0 No license field.
Demeteorizing application...
--server-only: unknown option.
Usage: meteor build <output path> [--debug] [--directory]
          [--mobile-settings settings.json] [--server http://example.com:3000]

Package this project up for deployment. The command outputs a directory with
builds for all platforms in this project.

By default, the output directory will contain just a tarball that includes
everything necessary to run the application server. (See README in the tarball
for details.)

If you have added mobile platforms to your project with the
'meteor add-platform' command, then the output directory will contain
subdirectories named 'android' (with the APK bundle and Android project
source) and/or 'ios' (with the Xcode project source).


Options:
  --debug             Build in debug mode (don't minify, etc).
  --directory         Output a directory (rather than a tarball) for the
                      application server bundle. If the output location exists,
                      it will be recursively deleted first.
  --mobile-settings   Set optional data for the initial value of Meteor.settings
                      in your mobile application. A new value for
                      Meteor.settings can be set later by the server as part of
                      hot code push.
  --server            Location where mobile builds connect to the Meteor server.
                      Defaults to localhost:3000. Can include a URL scheme
                      (for example, --server=https://example.com:443).
  --architecture      Builds the server for a different architecture than your
                      developer machine's architecture. Valid architectures
                      include os.osx.x86_64, os.linux.x86_64, and
                      os.linux.x86_32.
  --allow-incompatible-update   Allow packages in your project to be upgraded or
                      downgraded to versions that are potentially incompatible
                      with the current versions, if required to satisfy all
                      package version constraints.
Conversion failed.
Build attempt failed, attempting again.

[ziedmahdi]

solved by downgrading to modulus@5 and setting runtime to nodejs

[theworkflow]

@ziedmahdi Sorry for the confusion. The message Using Meteor <version> prints the Meteor version that's in the build image, not of your source. We currently have an updated build image that's going through testing that will clear that up. If you update your Meteor application to v1.3 then you will be able to build your application through the meteor runtime. The runtime requires your Meteor application to be v1.3 or greater.