files missing from deployed project
28 July 2017 22:30
Hi all,
I've created a 'starter files' JSON project, built it and deployed it.
After I'd FTP'd it up to my server, the screen was just black.
The console showed that a few files were missing, and on closer inspection the deployed project looks pretty lightweight.
Here's the file structure that deployed:
Top level
-Project Assets Directory
-b4w.simple.min.js
-images (custom folder for the UI)
-Project.html
-Project.min.CSS
-uranium.js
-uranium.js.mem
Second level
-all of my textures (Project Assets Directory)
-Project.JSON (Project Assets Directory)
-Project.bin (Project Assets Directory)
And that's it!
No 'project.js' and there's probably other stuff missing too, considering the amount of dependencies in the project manager framework.
Am I doing something wrong?
Best regards
Charlie
I've created a 'starter files' JSON project, built it and deployed it.
After I'd FTP'd it up to my server, the screen was just black.
The console showed that a few files were missing, and on closer inspection the deployed project looks pretty lightweight.
Here's the file structure that deployed:
Top level
-Project Assets Directory
-b4w.simple.min.js
-images (custom folder for the UI)
-Project.html
-Project.min.CSS
-uranium.js
-uranium.js.mem
Second level
-all of my textures (Project Assets Directory)
-Project.JSON (Project Assets Directory)
-Project.bin (Project Assets Directory)
And that's it!
No 'project.js' and there's probably other stuff missing too, considering the amount of dependencies in the project manager framework.
Am I doing something wrong?
Best regards
Charlie
29 July 2017 01:23
Once deployed, you unzip the folder and upload it without changing the file structure. When you try to view it, your browser console should throw an error to tell you what files are missing and where it was looking for them to be.
It should look like this when deployed:
It should look like this when deployed:
29 July 2017 14:01
30 July 2017 02:55
Can you copy/past your project info? Click the info link for your project.
30 July 2017 22:17
Project Name
OFFICE_DEMO
Project Title
Office Demo
Project Author / Company
Project Icon
Applications
[detected automatically]
Application Type
Copy
Size
97 Mb
Project Path (Development Directory)
projects/OFFICE_DEMO
Project Config
projects/OFFICE_DEMO/.b4w_project
Build Directory
projects/OFFICE_DEMO/build
Blend Directory(s)
projects/OFFICE_DEMO/blender
Assets Directory(s)
projects/OFFICE_DEMO/assets
URL Params
JavaScript Obfuscation Level
simple
JS Compilation Pass-Through List
CSS Compilation Pass-Through List
Build Ignore List
Deployment Assets Directory
assets
Deployment Assets URL Prefix
assets
Deployment Ignore List
OFFICE_DEMO
Project Title
Office Demo
Project Author / Company
Project Icon
Applications
[detected automatically]
Application Type
Copy
Size
97 Mb
Project Path (Development Directory)
projects/OFFICE_DEMO
Project Config
projects/OFFICE_DEMO/.b4w_project
Build Directory
projects/OFFICE_DEMO/build
Blend Directory(s)
projects/OFFICE_DEMO/blender
Assets Directory(s)
projects/OFFICE_DEMO/assets
URL Params
JavaScript Obfuscation Level
simple
JS Compilation Pass-Through List
CSS Compilation Pass-Through List
Build Ignore List
Deployment Assets Directory
assets
Deployment Assets URL Prefix
assets
Deployment Ignore List
31 July 2017 01:05
After you have used the 'Build' function, you should be able to open the build version of your app.
Does your app work when you open the build version?
I if does, all your files are there.
Another thing you might try is create a new project, leave all options default. Build it, then deploy it and see if you get the same results.
Does your app work when you open the build version?
I if does, all your files are there.
Another thing you might try is create a new project, leave all options default. Build it, then deploy it and see if you get the same results.
31 July 2017 17:22
Hey Will, the build does not work.
The console reports the same; a 404 of the main js file.
I ran it again and noticed this exception in the build process:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/google/javascript/jscomp/CommandLineRunner : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
The console reports the same; a 404 of the main js file.
I ran it again and noticed this exception in the build process:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/google/javascript/jscomp/CommandLineRunner : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
01 August 2017 12:49
Hi Charlie, what java version is installed on your Mac? There already was a problem with Java in other topic: link.
09 August 2017 15:48
Thanks Ivan / Will
I've looked into this a little deeper, and it's got something to do with the JRE compiler.
I'm using a Mac running Sierra, with Java 8 - Update 144 ( build 1.8.0_144-b01 )
I'm not even sure I can run 6 or 7 any more, I don't seem to be able to get them via Oracle or Sun.
This is a pretty big issue, I could really use a hand.
Thanks
C
I've looked into this a little deeper, and it's got something to do with the JRE compiler.
I'm using a Mac running Sierra, with Java 8 - Update 144 ( build 1.8.0_144-b01 )
I'm not even sure I can run 6 or 7 any more, I don't seem to be able to get them via Oracle or Sun.
This is a pretty big issue, I could really use a hand.
Thanks
C
09 August 2017 18:15
I'm using a Mac running Sierra, with Java 8 - Update 144 ( build 1.8.0_144-b01 )This is strange, because Java 8 should work fine. Actually, the error "Unsupported major.minor version 51.0" means that you're trying to use a jar-package, which is compiled with Java 7 (that's true for google closure compiler used in building), but you're running it with an older Java version.
Is it possible, that you have several Java versions installed or outdated JDK? In that case the older version can be used instead of Java 8 that you also have. What version does the terminal show for "java -version" command?
You can also find helpful the corresponding question on StackOverflow: https://stackoverflow.com/questions/12757558/installed-java-7-on-mac-os-x-but-terminal-is-still-using-version-6