Made a website with Ember, and deployed it to the server.
However, the page does not fully load on my desktop Chrome and Safari due to errors.
I'm getting...
Uncaught SyntaxError: Unexpected token . ember-1.0.0-rc.6.1.js:18872
Uncaught ReferenceError: Ember is not defined buyahome.js:3
It works fine on localhost.
Also works fine on mobile devices.
Also noticed that some users can load it on their desktop on either Chrome or Safari.
Tried jshint, but doesn't seem to be able to find what's wrong with it.
Does anyone seen this issue before?
Have you tried the javascript console with halt on errors? There may be an error preceding the loading of ember.js that isn't logging anything which is causing this error further down the line. Another error is usually what causes things not to get defined on the namespace later on.
Have you tried to update to lastest build of ember.js? I believe that you are using a release candidate version pre 1.0. Download the current starter kit from the Ember website which will have the current stable builds of ember.js and handlebars.js and see of that fixes your error. It is strange that you can not load it from your Browser but others can. I ran into a few issues with Chrome on my Linux machine but try to upgrade and see what happens.
Related
I am having trouble getting crash report in my Bugsnag dashboard. I followed Bugsnag doc and tried to fatalError() on one of my ViewController and it seems like it does not work. By the way, Bugsnag.notifyError(NSError(domain:"com.example", code:408, userInfo:nil)) seems working. There is not really meaningful code to provide to get the answer because what I tried is pretty trivial. Created an app, installed Bugsnag with cocoapod, disabled bitcode part as stated in the doc (installed the plugin that uploads dSYM file), and crashed the app on purpose.
Any help will be appreciated. I am frustrated to get crash report tool on my app. I have tried Firebase crash reporting tool and did not succeed too. T.,T
Do you have the debugger attached? a fatalError will not report if the debugger is attached.
Additionally, you'll need to restart your app after a crash in order to send it in.
Hope that helps!
I'm evaluating WSO2 identity server for a customer of mine and currently we ponder whether to write our own user dashboard or use WSO2's version of it.
According to WSO 5.3.0 it's as easy as opening /dashboard. I don't find anything about how to install or enable the user dashboard and I didn't find a module I could install. Therefore I think that this should work out of the box. Yet, when I open the URL I get an error:
HTTP Status 500 - org.mozilla.javascript.EcmaError: ReferenceError:
"readFile" is not defined. (/dashboard//login.jag#47)
type Status report
message org.mozilla.javascript.EcmaError: ReferenceError: "readFile"
is not defined. (/dashboard//login.jag#47)
description The server encountered an internal error that prevented it
from fulfilling this request. Apache Tomcat/7.0.73
I tried to find the cause of this issue but the log files are in no way more verbose and after looking at the includes of login.ja redFile seems to be defined.
Can anybody please point me towards something that helps me solve this issue?
Thanks in advance!
For some reason (that are still to explore) three modules that were in the installation archive were missing from the actual installation. The modules were: caramel, handlebar and markdown. After installing them from the archive the dashboard started working.
Installing caramel only didn't work and my guess is that markdown is not necessary to run the dashboard but I might be wrong.
I found that is does not work with Safari. Identity Manager does.
I originally tried it on MacBook pro.
When I tried it with Chrome all is well.
Here is the source code.
I'm running Ember-CLI from the master branch of the git repo (currently version 2.2.0-beta.1-master-e803ac7fa6) and linking via npm. This should be using versions 2.2.0 of Ember and Ember Data. In the middle of the basic tutorial, I hit an issue with Mirage and Ember Data. Without explicitly creating an application adapter, the app fails. There is a 404 error being thrown on the route that should be handled by Mirage, as well as numerous Adapter errors. No errors are shown during ember serve.
In trying to fix this, I ran into another issue. After running ember g adapter application, the app loaded in the browser but there was still an error because this generated a RESTAdapter instead of the preferred JSONAPIAdapter. After manually switching to the JSONAPIAdapter, everything is fine.
Is this an issue with Ember-CLI still using an old version of Ember Data somehow? Update: #Michael and #Gaurav found the issue with Ember-CLI. See his answer for the Github issue link.
The original question still stands, though. Should Ember be able to function without explicitly creating an adapter?
This is a bug with Ember CLI 2.2.0-beta.1 - it's using the wrong adapter type by default. Can you open an issue on Ember CLI? Thanks!
I am new to Ember.js and am working on an app with ember-cli-simple-auth-devise. It's working just fine in production, but when I deploy to production I get the following errors in console:
Uncaught TypeError: undefined is not a function vendor-dcea5bee9241c862bf2e30c2d2760f2e.js:15
Uncaught Error: Could not find module simple-auth-devise/initializer
This is a gist of my conf/environment.js
[https://gist.github.com/gordonbisnor/b65f192392029fe703a1]
Not sure what other code might be relevant to include for reference, but would be happy to create gists, etc.
Wondering if anybody has an idea what could cause this to be working in development but not production.
The solution turned out to be removing ember-cli-bootstrap, see this Githuib issue in ember-cli and this Github issue in bootstrap-for-ember.
I'm trying to understand if Ember.JS would work with chrome packaged apps, as I get these errors when I first run it.
http://pastebin.com/fV8V4fjw
Would these errors end up being a big issue? I can see the localstorage one being an issue, but I can always change that part of the api if needed I suppose.