I'm trying to test my game on the site using the simulator page. however I'm running into a problem. no mater what it seems like my page updates are not changing on the simulator. I've tested locally on the pages, and they work fine.
anyone know? i haven't seen anything in documentation
At least for me when I'm testing the controllers for the Unity project, or another HTML / Javascript project I need to clear the cache once in a while to make it work.
For Firefox; Options (top right corner) - Privacy & Security (left menu) - Clear data (button on the right)
(I untick the "Cookies and Site Data" because it does not affect to this problem.)
And just to make it clear, it's not an AirConsole problem. If you have ever tried to create a local website and you are testing stuff this might happen as well. Also, you don't have to do this everytime something changes.
Just found out that if you add something a question mark after the address and put something random after it, it will refresh well again (a bit like what is done in web with images to avoid caching sometimes).
Example:
Original url: http://www.airconsole.com/#http://192.168.1.2/game
Url after 1st change: http://www.airconsole.com/#http://192.168.1.2/game?1
Url after 2nd change: Url after change: http://www.airconsole.com/#http://192.168.1.2/game?2
etc...
UPDATE
I've also found that the following works:
Original url: http://www.airconsole.com/#http://192.168.1.2/game
Open a tab with http://192.168.1.2/game/screen.html
Do CMD + Shift + R on OSX or Ctrl + F5 on Windows when using Chrome
Switch to the original airconsole URL tab and do the previous step
Your game is now refreshed
Related
I'm testing something in a personal tab (something related to SSO, if that's important in context), and the tab renders fine for about 30 seconds or so, then suddenly gets replaced with an error "There was a problem reaching this app" (the one with the image of a woman and a thought bubble). Does anyone know why this suddenly happens AFTER the tab has ALREADY rendered ok?
I finally found an answer to this, so posting in case someone else has the issue. Basically, Teams manifest recently added a capability to show a loading / progress indicator to show users that your tab is still loading. It shows up in the manifest as "showLoadingIndicator" and is boolean (true/false). It can also be set in App Studio of course, as the image below shows.
The problem comes in that the "SDK" link shown in App Studio is flat-out useless - it links to the Teams js Library on GitHub, of all places! It should rather go to this section of this page, which explains how to deal with it. I was originally only calling microsoftTeams.appInitialization.notifyAppLoaded();, but I needed to also call microsoftTeams.appInitialization.notifySuccess().
I'm not sure if this is a bug with Cloud9 or if it's the way it's supposed to work so I'm checking here first.
To keep things as simple as possible, let's say I create an index.html file which contains a link to go to inside.html
Then, I select "Run Project" and the index.html file displays inline with the URL in the address bar showing "https://php-userid.c9.io" as it should.
I then click on the link and am taken to inside.html but the problem is that the inline address bar does not update with the new URL.
On top of that, if I hit refresh, it refreshes index.html rather than inside.html as I would expect.
I realize that there may be a good reason for all of this but from my own personal perspective, I often need to know what the current URL is during development in order to properly debug my app.
I opened a ticket with C9 and they confirmed that although this is not how they want it to work, it's the only way that it can work for technical reasons.
This problem will hopefully be solved when C9 release their multi-platform desktop client in the future.
How do I get the back button from Windows phone to work with PhoneGap 1.2?
Now what the back button does is exit the app.
There is a good post I dont understand or get to work by one of the SO editors: http://www.scottlogic.co.uk/blog/colin/2011/11/handling-the-back-stack-in-windows-phone-7-phonegap-applications/
but I dont understand it and I cant get it to work. (even the sample .sln has an error for me)
My app is a very simple structure of index.html and many html does that come off that one page, so if all the back button did was goto index.html, that would probably work for me.
Is there a solution for idiots? For example - add this framework but only to specific pages. Put this code here, and that code there, and those pages dont need anything. Something like that?
I have recently published a more simple example for back-button handling in applications that contains simple HTML pages:
http://www.scottlogic.co.uk/blog/colin/2011/12/a-simple-multi-page-windows-phone-7-phonegap-example/
In essence, there is some C# code that keeps track of when the browser navigates from one page to another, handling the back-button event in an appropriate fashion. Just drop your code into the www directory and it should work fine.
As brilliant as Firebug is, I would consider switching my JavaScript debugging to Chrome if I could figure out how to get it to always re-download styles and images on every visit to the page?
When I'm testing a page in Firefox, it always gets the latest version.
But in Chrome I often end up scratching my head over something that turns out to be a simple issue of the browser caching some earlier styles or images.
Is there a way to configure Chrome to cache less while you're developing?
I often use private browsing mode for this - it prevents caching of the stylesheets or scripts.
EDIT:
Another really easy way to do this in Chrome now is to go into the Chrome Developer Tools, click the settings gear (bottom right), and then check "Disable cache." See https://stackoverflow.com/a/7000899/4570.
A bit late to the party, but just for people who may pick up this page on a search, new versions of Chrome have a developers tools setting to disable the cache. Show developer tools (spanner->tools->developer tools) and on the bottom right is a tiny little gear. click that and a few settings appear in the developer tools window, one of which is to disable the browser cache. If you can't see it you may have to upgrade to a newer version of chrome.
Ian
According to Chrome help pages, Ctrl+F5, Shift+F5, Ctrl+R and Shift+R should force refresh. I haven't had problems with javascript and css but refreshing frames is another story. The caching can also be on your web server. The server can obviously be configured to cache css and javascript files.
Your best bet is to clear the cache between each load. With the latest version of Chrome, the hotkey is the same as firefox (on Mac, it's Shift-Command-Del). However, they haven't focused the "Clear Browsing Data" button, so you have to use your mouse to click that button -- which is a total PIA when compared to Firefox (Shift-Command-Del + Return), or Safari (Option-Command-E + Return).
the 2.5 ways i do it are not "automatic" but they're very quick, and i don't have to remember to switch back from private browsing -
a) install Mouse Gestures and use (this is a great extension anyways, but even more so now that I know about) Up, Down, Up - this is a cacheless reload. You can get it here
b) ctrl+shift+r is [supposed to be] a cacheless reload. Even the help pages admit this isn't perfect
c) the .5 is a kind of a hack - but if you are working with CSS files, open a new tab and type in the address to the CSS file itself - you can see what changes are there, as well as make sure that you've gotten the latest one by refreshing this file before your other file. a bit of a pain, i know, but always works.
Not sure about your system but on this WinXP machine holding SHIFT while clicking refresh always forces a complete download.
That's what I do when doing CSS and image tweaks.
That Chrome needs to have must-revalidate in the Cache-Control` header in order to re-check files to see if they need to be re-fetched the way that the other browsers do by default.
Recommend the following response header:
Cache-Control: must-validate
This tells Chrome to check with the server, and see if there is a newer file. IF there is a newer file, it will receive it in the response. If not, it will receive a 304 response, and the assurance that the one in the cache is up to date.
If you do NOT set this header, then in the absence of any other setting that invalidates the file, Chrome will never check with the server to see if there is a newer version.
Here is a blog post that discusses the issue further.
When I debug locally in fire fox 2.0x many times my page won't have the styles added properly or the page will not completely render (the end is seemingly cut off). Sometimes it takes multiple refreshes or shift-refreshes to fix this. Is this a common issue or is it just me? Any solutions?
I want to add that this is happening in fire fox 3.x to me as well. I add my javascript to the pages dynamically and this might be part of the issue. This is when I am working locally with Visual Studio.
Update: This does happen in IE but it happens much more often in Fire Fox. The issue seems to be only javascript and CSS files not loading. For example I get jQuery is not defined, $ is not defined etc. I don't think I have local IIS to test this on but from the server it always works perfectly. Fire Bug shows all my css and javascript files to be requested and received.
This could be a problem with IPv6 and DNS of the Firefox browser. This issue is known to slow down Firefox on localhost:SOMEPORT. The effect would be that some external files won't load (css, js etc.) resulting in a partially rendered page.
You can solve this issue by simply deactivating IPv6 in Firefox:
Insert about:config in the Firefox address bar
Set network.dns.disableIPv6 to true or alternatively add localhost to network.dns.ipv4OnlyDomains
A different way to fix this issue, is to a remove the ipv6 address from your hosts file this way: open the file
C:\Windows\System32\drivers\etc\hosts
(with administrator privileges) and remove (or comment out #):
:: localhost
Make sure that you narrow the scope of the problem. Does the problem just happen when debugging from VS or does it also happen with local IIS? With server-based IIS? Does it happen to other developers in your company? Is it really just FireFox or does it happen to Chrome, Opera, IE, etc?
Assuming that you've already worked that all out, I would suggest installing a FireFox plug-in called "Tamper Data". Open that and refresh the page. You'll see a record of every connection from the browser to the server (for each html file, image, css file, etc). Look to see if any of the them are very slow or not completing (perhaps one of those files is taking a long time and FF is waiting for it to finish before loading other important files).
Assuming that all of the files correctly loads, you should consider checking that the syntax is valid (maybe there is some unclosed tag or quotation mark that is causing FF confusion). I use a plugin called "Web Developer", but there are a lot of other options out there.
You could also use a plugin called FireBug to view the HTML behind various parts of the page to see if there are any noticeable problems. You start FireBug, go to the HTML tab, click Inpsect, and move your mouse over something on the page, and it will show you the HTML behind it.
One thing to do would be to check the source of the page(s) in question. My guess would be that the local server that VS runs is not giving you the entire source of the page. One way to verify this would be to run exactly the same code in the debug environment, as well as from a "real" server like IIS 6. If the same behavior is seen on loading the page from both servers, as well as insuring that the full page source is being recieved by the browser(s), then it is a bug in Firefox and should be reported. This is especially true if other browsers, ie. IE, Chrome, Safari, Opera, render the page fully.
Are you comparing what you see in Firefox to what is displayed in the Visual Studio designer? If this is the case, then they are using 2 different methods to render the html and may not display the same.
Anything further on this folks?
I have examined the traffic using Firebug and it appears that when veiwing the response from the request for a style sheet, the response is just blank. After refreshing (sometimes multiple times) the age displays correctly and the response information contains the style sheet. I have not seen this in any other browser and it only occurs when viewing the app from Visual Studio.
2! Recently i had the same problem. Im using MVC 1.0 and I added a new stylesheet into Views/Share folder. And when i run the project, the page didnt render along with the css. If your web project is a MVC one so try put the css file into the Content folder.
Hope this help.
HaiVu.Doan.
In case anyone else finds this with newer versions of Visual Studio, I have to run VS as Administrator. This is something I keep forgetting to do, but once I right clicked on Run as Administrator when opening VS, the problem went away.
Initial problem, I could not get CSS to render when running a project from VS 2012 using Firefox as the browser. (IE worked just fine, btw.) The content would be there, but no CSS. This was the first post I found when I typed in my question.