I've picked up the discover meteor ebook earlier today and have been following the steps. It's been a great experience and I hope I can contribute to this community once I have a more thorough understanding of the technology. All is going well and I was using firefox as my browser. I decided to install chrome since that is the browser I use on my host machine on a day to day basis. However when I load the project up in chrome its a blank screen. The console reports the following(pastebin)
http://pastebin.com/wvEaVNPv
Has anyone else experienced this issue?
YES! It comes and goes with time or development, and you will get different results in different browsers (ubuntu). I currently am getting
Uncaught ReferenceError: Package is not defined meteor.js:21
Uncaught ReferenceError: Package is not defined standard-app-packages.js:21
Uncaught ReferenceError: Package is not defined random.js:21
etc
A few weeks ago, chrome canary was bad but release chrome not. It may be some subtle code issue triggers things because as I developed madly but checked intermittently that problem came and went maybe three times, and once another browser gave me a clue on something it didn't like, which also cured chrome.
I don't have any tools/concepts to debug this further. I initially got through Discover Meteor using chrome about 2 months ago.
Check your accounts-ui-bootstrap-dropdown. If you are using bootstrap-3 you'll need accounts-ui-bootstrap-3. I found this as one possible cause when I went back.
Related
I just downloaded libgdx and every time I tried to build an application it said build failed giving me the reason "A problem occured evaluating root project". But when I switched back to jdk-8 build was successful. I was just curious that if it was just something I did wrong or libgdx does not support jdk-9.I tried searching on internet but couldn't find anything.
I've got a project that I am working on that works fine when debugging from IntelliJ but when I do a release build (still in IntelliJ) and install the .air fil to my computer none of the FastInject tags seem to work.
I thought that this might be due to the include-as3-metadata issue but that does not seem to be the case. I have included all the metadata tags that I think I have used.
I have spent some time investigating this and have not made much progress other than getting frustrated!
I created a view that displays the logs created by spicefactory - but this seemed to fix the issue!
I tested to see if I could inject and of classes that are expected to be FastInjected, this also fixed the issue.
It seems that if I add any logging related code to the application the FastInject tags start working.
In fact, I have created a release air file here. If I install this on a computer with Flash debugging turned on the application doesn't work. If I follow the steps here to debug an installed Air application - it starts to work!
If anyone else can confirm this behavior I would appreciate it.
It turns out that this was simply a race condition causing an error in context creation that was not displayed in a non-debug player.
This exception never happened while I was developing the application and any changes to the application to add logging changed the initialisation order of the context and caused the issue.
I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.
I just setup my libgdx game with the gdx-setup-ui.jar today and I have everything setup in eclipse. I thought I would run each application (i.e. desktop, android, and html) to make sure everything is working ok. Unfortunately, I ran into problems with my html application. I am getting this error with a tablelayout.gwt.xml:
I have no idea how to solve this problem. Is there a fix for this problem and if anybody knows it could they share? Thanks!
EDIT
So even though i fixed the problem by restarting my project, my problem has come back. This time, however, I am too far along in development to just restart my project, or re-setup my project.
I deleted my old project and created it again using the gdx-setup-ui.jar application and made sure that all the necessary libraries were included.
I have a web server running Windows Server R2 Standard, and am experiencing the issue described in this blog post: http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
In short, .Net is failing to recognise IE10 and is treating it as a downlevel browser without javascript support - if I understand the issue correctly.
I tried the following popular solutions:
Installed both hotfixes for .Net 2 and 4.
Manually updated the browser definition files in the .Net framework config folder and ran aspnet_regbrowsers.exe.
Put the new browser definition files in the App_Browsers directory.
Finally I upgraded to .Net 4.5 which solved the issue for .Net 4 sites running on the server, however .Net 2 sites are still experiencing the issue.
Because this is a live web server it has a lot of windows updates that have not been installed. I thought maybe there was an update that would address the issue. So I've taken a look at the updates but none of the descriptions seem to address the issue, so I cannot justify installing them and potentially causing more problems.
Does anyone have any other solutions or possible reasons why this issue just won't go away?
I have the same problem, and I haven't been able to figure out why none of the fixes work. However, I did find a workaround that might work for you: Setting the Page.ClientTarget attribute to "uplevel" overrides .NET's browser capability detection. Have a look at http://msdn.microsoft.com/en-us/library/system.web.ui.page.clienttarget.aspx for more information.
Have come through many microsoft hot fixes, they were working in local environment, but in the live server there was no result.
Setting up Page.ClientTarget = "uplevel" (preferably in a header or footer page) has really solved the issue. I think this the best solution, as your .net application may not detect any other browser in future. But then we may have to wait and see, if this fix has any side effects.