Once you’re happy with your Web App you’ll want to deploy it to your device, Dreamweaver CS 5.5 integrates this feature nicely; however, there is an issue with one of the classes that will prevent your app from compiling, here’s how to fix it.
Dreamweaver CS 5.5 will happily create a skeleton jQuery web app for you, I’m using the four page sample app created by Dreamweaver to show the exact error, where to find it, and how to fix it, see this post for more info on creating a web app with Dreamweaver.
Once you have your site ready to deploy, you need to set up your development environment, go to Site – Mobile Applications – Configure Application Framework.
Set the “iOS Developer Tools Path” to where you installed xCode
The default is /Developer, then click save.
Now you need to configure your Application settings, go to Site – Mobile Applications – Application Settings.
Fill in your Bundle ID, App Name, Author Name, Version Number & Target Path (You should not set your Target Path the same location as your site root, it’s fine to leave it set to desktop as Dreamweaver will create a folder for you).
Icon and splash screen are optional, for this tutorial I have left them out, for more info on Web App icons and Splash screens see this post.
Once you have finished filling in you settings click Save, then go to Site – Mobile Applications – Build and Emulate – iPhone.
This is when the error appears, Oh Dear!
Not to fear Dreamweaver is telling us to go look in the buildlog.log, you can find this file under the folder Dreamweaver created when it tried to compile your app, which will be on your desktop (or wherever you set your Target Path).
Browse to the Buildlog.log file location Dreamweaver just informed us about and double click on it, the log file will open in Console, and if you check the log file you can see the error, what the error is and the file that’s causing the problem, as you can see from the log, Dreamweaver even points out the error with a ^, and also tells us the path to the offending file.
Browse to the Camera.h file specified in the log, which you will find in your Documents folder, again as you can see from the log, it’s in a Folder called DW_NAF, the default path is:
Documents, DW_NAF/PhoneGapLib/Classes/Camera.h
Double click the Camera.h file to open it with xCode or use a text editor, make the following changes and save the file.
Change the line that reads “enum DestinationType returnType”, and correct it so it reads as follows, don’t forget the semi-colon;
Now we can go back to build and emulate and your app will compile successfully.
If you run into any problems then make sure you have the latest version of Dreamweaver installed, and double check your Camera.h file.
[...] Read Shane’s Solution Here… [...]
Hi Justin, many thanks for the link back, it’s an honor to get traffic from your good self, check out some cool tutorials over at http://www.cartoonsmart.com
Thank you. Was tearing out what little hair I have left thinking this was a PhoneGap (Cordova) problem in conflict with iOS 5. Almost gave up on this whole method until your excellent fix!
No problem, glad to be of assistance, and thanks for letting me know, most appreciated, All the best with your App, Shane.
Nice. thanks.
My Pleasure
[...] Dreamweaver Site | TutorialMatrix.comDreamweaver CS5 Php | Dreamweaver CS5.5 php mysql video …Compiling your Web App with Dreamweaver & PhoneGap Fixing …Copyright © 2012 IT技术园地. All Rights [...]
The dreamweever you used is a dreamweaver version of mac
Hi Lein, that is correct you need to use the Mac version of Dreamweaver to compile for iOS devices, and the cheapest way to buy a Mac is to get a Mini-Mac, you can pick one up for around £500, and use your own monitor, USB keyboard & mouse, although you may want to check out these guys, http://www.macincloud.com/ Twitter @MacinCloud, where you can rent a Virtual Mac, which comes with xCode, Dreamweaver and lots more cool stuff, they also do a free trial, hope that helps.
As with so many, I had the same problems and the solution above was tried. Unfortunately, I’m getting new errors now after applying that solution. iOS buildlog provides the following:
/Users/Randy Rogers/Documents/DW_NAF/PhoneGapLib/Classes/Camera.h:26:5: error: type name requires a specifier or qualifier
returnType;
^
/Users/Randy Rogers/Documents/DW_NAF/PhoneGapLib/Classes/Camera.h:26:5: warning: type specifier missing, defaults to ‘int’ [-Wimplicit-int]
returnType;
^~~~~~~~~~
/Users/Randy Rogers/Documents/DW_NAF/PhoneGapLib/Classes/Camera.m:178:13: error: type of property ‘returnType’ (‘DestinationType’ (aka ‘unsigned int’)) does not match type of ivar ‘returnType’ (‘int’)
@synthesize returnType;
^
/Users/Randy Rogers/Documents/DW_NAF/PhoneGapLib/Classes/Camera.h:26:5: note: ivar is declared here
returnType;
^
Any ideas as to my next steps to repair?
Thanks, R2
Hi Randy Looks like a completely different error, are you using some kind of Variable?, looks to me like the log is telling you that you are trying to pass an signed integer type variable to an unsigned one, if you are using any JS vars in your code, try commenting them out and then compile, if that works then you can uncomment them one at a time until you find the issue. Although without being able to reproduce the error I cannot say for sure, hope that helps.
I have basically gone through the hole process explained above and got the message that the emulation of the appname completed successfully, files are in folder, well same message as above, and I do have the folder with the files, but the emulator doesn’t show. Restarted Dreamweaver and even the MacBook, but am still not getting the emulator.
Any Help is appreciated
Hello, here’s what I would do, start the emulator from your developer folder, if it works then that’s cool, you have no problems there, go through the steps again, but remember this post refers to xCode 4.2, things change, have you got the latest Dreamweaver, did you update xCode, if so, remember the latest version doesn’t install automatically, you need to go to you applications folder and double click on it to start the install, once installed try compiling one of the templates to see if this loads the emulator, check your logs for detailed info, these will help solve your issue.