Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9149763
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T11:31:16+00:00 2026-06-17T11:31:16+00:00

When upgrading to v1.0.0-pre.3, I get the following errors: Uncaught Error: assertion failed: Ember.Object.create

  • 0

When upgrading to v1.0.0-pre.3, I get the following errors:

Uncaught Error: assertion failed: Ember.Object.create no longer supports defining methods that call _super.

Which it appears that for performance reasons, the original create() functionality was preserved in createWithMixins()

Which is answered fairly clearly here:

https://github.com/emberjs/ember.js/commit/c1c720781c976f69fd4014ea50a1fee652286048

https://github.com/emberjs/ember.js/pull/1623#issuecomment-11699639

Ember.Application.create with mixin and parameters

But once I make that change, I now get this error:

Uncaught Error: assertion failed: Application initialize may only be called once  

A search of my codebase and I am only running an App.initialize() once.

(function(root){
  require(["config"], function(config){
    requirejs.config(config);
    require(["App", "domReady!", "ember"], function(App, doc, Ember){
        var app_name = config.app_name || "App";
        root[app_name] = App = Ember.Application.create(App);
        !App.isInitialized && App.initialize();
    });
  });
 })(this); 

Any ideas?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T11:31:17+00:00Added an answer on June 17, 2026 at 11:31 am

    I believe you don’t need to call initialize at all with the new version.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

After upgrading to the iPhone SDK 4.0, I get the following error when building
I want to create a so-called pre-signed URL for uploading a particular object (PUT)
After upgrading my Rails 3.0.9 app to 3.1.1, I'm getting the following bundler error
After upgrading node to v0.8.1, bundled Meteor apps now throw an error: node: symbol
In several previous projects (all pre-Spring 3.0), I had a single error handling jsp
I've been following reign design's guide to use a pre-constructed sqlite database in an
in upgrading rails app from 2.2.2 to 2.3.9 first error was: D:\web>ruby script/server -trace
I have the following html to upload files: <?php echo <pre>; var_dump($_FILES); echo <br
In the process of upgrading a pre-1.4 Magento site to version 1.4.1.2, I've run
After upgrading to Spring 3.1 I noticed that my custom SimpleMappingExceptionResolver is no longer

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.