Im using smartGWT v2.1 with GWT 2 and Appengine SDK 1.3.0
On localhost, everything works fine!
When I deploy everything goes fine too, without any error!
The problem is, when i access the the app it returns an blank screen. Using the firebug i saw just nocache.js missing.
ErrorLog:
GET mika.nocache.js
http://perfworker.appspot.com/Mika/mika.nocache.js
404 Not Found
perfworker.appspot.com
Just to know, the last version of smartGWT should work on AppEngine out of the box?
Thanks in advance!
Cleber
I'm going to guess you're developing on Windows. NTFS, unlike nearly every other filesystem, is case-insensitive, so it'll work fine if your file or directory has one capitalization and you're accessing it with another. On every other platform, however, including the one App Engine runs on, capitalization matters: Check that you're using the same capitalization to access the file as is used to name the file.
Btw, this not only applies to SmartGwt, but to any GWT app. I would have voted on the answer above, but I don't have enough rep points yet [new user]. Changing the casing of the link in the base html page worked for me.
Related
I am attempting to create a react based web app. I got it working the way I wanted, and it behaved as a web app the way I expected -- for now, that means to me that on my phone, from chrome, if from the chrome menu I choose 'Add to Home screen' it shows up as if it were an app (showing up with its own icon & launching in a new window outside of chrome).
After getting that working, I decided to reorganize so that the path would be the way I wanted it - from mydomain.com -> apps.mydomain.com/appName. I moved the code to the proper directory, and when I browse there I see my "app".
I noticed an issue right away where the static assets were not loading, I fixed that by adding a symlink in www/mydomain.com pointing to www/mydomain.com/appName/static. At this point, I thought my app was properly reorganized.
Unfortunately, when I tried "add to Home screen" from chrome, it now makes a regular shortcut, which to me seems to indicate the manifest.json isn't being applied. This all adds up to me to be a fundamental issue I don't understand with code organization for sub-paths which gave me pause.
So my question is: What do I need to do to properly host my web app in a sub-path?
Notes:
I am using nginx - I am suspicious that my issue lies in configuration there, and if more info on my configuration there is needed, I can provide it.
Regarding the change to apps. - sorry if it obfuscates the problem somewhat, to note I just added an alias - thus apps.mydomain.com appears to be equivalent to mydomain.com - I only noted it in case that assumption was wrong and part of the problem.
Pardon my question language if it's wrong, I am new-ish to web, and may not be using the lingo properly - that also is why I am probably having difficulty just googling this.
Thanks!
I think I figured it out. My app was made with create-react-app, and in the package.json I edited the homepage to be my path.
Found this out from here:
https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#building-for-relative-paths
I'm currently using Google Appengine to host a website with Golang as the backend. I have a custom domain setup and (sometimes) it works perfectly fine. My website requires some css and js files from the server. These were served perfectly in the past but now it randomly stops working. Both on the "mydomain.de" and on the "myapp.appspot.com" domains. Sometimes it works on the normal domain and then it works on the other and sometimes even on both. But if I reload the site after a couple of minutes it just shows me an old index.html file (that I have removed days ago).
Did someone experience this problem in the past and does anyone know a fix for this?
Thanks in advance.
Have you ruled out your browser cache as the source of the problem? If after getting a stale version, shift-reload (assuming Chrome or Firefox) brings up the desired version, then look into how to do "cache busting" for css and js, and check the app.yaml doc for how to set expiration times on static assets (assuming your index.html is static).
I have created one ionic app it runs perfectly fine in browser but when I convert it into app it gives white screen.
I have already install white list plugin and allowed all url in config and also have kept meta tag. Am not able to find any other solution.
When kept simple html file am able to view it.
Any help will be grateful.May be good way to debug will be also good.
Connect your phone to PC with USB cable and remember to keep USB Debugging On. Now, navigate to chrome://inspect. You'll find the device name and click on "inspect". On Console tab, the error list will give you a hint about what is wrong there.
In my case, a custom service was Injected in controller which had been removed at some time as It was not used anywhere.
Ok just answering this question so it will be helpful to all.
Below blog was helpful for me that how I can debug
http://gonehybrid.com/how-to-debug-the-white-screen-of-death-in-your-ionic-app/
And guess what was issue, folder name in app is case sensitive. I was just need to change a folder name as per exact case sensitive path I provide in index file.
Mostly such thing occures because of a javascript error. You say it runs in your browser. Are there some exception in the console?
Not everythings is equal between browser and device, for example plugins. You have to be sure, that all used plugins are installed properly.
If you deploy on android, you can use android monitor to get console output. On ios xcode has already an integrated debugger.
I had this horrible issue because I compiled my Android application with Cordova 6.x and the project worked with CrossWalk plugin. In my case, the solution was uninstalling Crosswalk. If your project has installed that plugin, try to uninstall it and compile your project again.
I created an iphone app in IBM Worklight using Angularjs, generated by yeoman. Everything works fine in the simulator, but when I deploy to my physical device, the app will open only once. Using the iphone configuration utility, the error reported merely says Failed to load webpage at that url.
I do not understand why it would only work one time.
It don't think this has got anything to do with angularjs and/or yeoman.
It sounds like you've changed the HTML filename in the common folder and the mainFile value in application-descriptor.xml. Changing the mainFile value used to cause a bug after launching the app a second time - it wouldn't find the resource, the HTML file.
If you indeed did the above, try the following:
Rename the application folder name to match the renaming you've done above
update the ID attribute of the application element in application-descriptor.xml to match as well
Make sure to delete the native folder
Re-build and deploy the app
This should now make the app launch a second, third, ... time as well.
Fixed in the upcoming Worklight 6.1.0.
Over Christmas I implemented some code to open a channel to my App Engine application using the channel API and it was working fine.
I recently returned to the code and find that it is broken, and the problem seems to lie in talkgadget that the client code is trying to load into a frame.
I took a snapshot of the code returned by /_ah/channel/jsapi on December 21 and I am comparing it to today's code.
When the older version tried to get talkgadget.google.com/talkgadget/d?token=[my-token] it was hardcoded to use http. Sensibly enough, the code was later changed to check the page's protocol in document.location and adapt to cases where https is used. The problem now is that when running in a chrome extension it grabs chrome-extension: as the protocol and naturally the channel fails to open in the extension.
Setting the base of the background page to my appspot URL does not change document.location, although I had some vague notion that it should. (Not sure what the standards say.)
Is there a workaround for this? One thought was to create my own iframe loaded from my site, but then it will nest the actual channel iframe, complicating things.
I wonder if Moishe or someone else on the App Engine team could comment on this. It seems like the this is a bug and the code should take into chrome extensions either by testing for the protocol and searching for a base tag as an alternative, or provide some way to configure this through the javascript object.
Yep, this is a bug. There's a fix submitted, and it's in the process of rolling out to production; it'll probably be out in about a week.
In the meantime, your idea of an iframe embedded in the extension should work.