{"id":313,"date":"2011-11-28T10:28:35","date_gmt":"2011-11-28T14:28:35","guid":{"rendered":"http:\/\/www.eqsim.com\/blog\/?p=313"},"modified":"2011-11-28T13:25:43","modified_gmt":"2011-11-28T17:25:43","slug":"fdt5-problem-solved-application-descriptor-not-found-compiling-mobile-project-on-desktop","status":"publish","type":"post","link":"http:\/\/www.eqsim.com\/blog\/fdt5-problem-solved-application-descriptor-not-found-compiling-mobile-project-on-desktop\/","title":{"rendered":"FDT5 Problem Solved &#8211; &#8216;application descriptor not found&#8217; &#8211; compiling mobile project on desktop"},"content":{"rendered":"<p>I really like working in FDT5 and was eager to try out mobile app development. The first test I did I had no problem, then all of a sudden, any new app was not launching, giving the error:<\/p>\n<p><span style=\"font-family: Consolas, Monaco, 'Courier New', Courier, monospace; line-height: 18px; white-space: pre;\">application descriptor not found<\/span><\/p>\n<div><!--more-->I thought it was a machine-to-machine problem, i.e., working on my desktop and not on my laptop, then I found I had an app on my desktop that would run but not a new project.  Hmm.  It looked like the arguments to the adl call was not handled properly.  In the correctly working version, the output was:<\/div>\n<p style=\"padding-left: 30px;\"><code>adl.exe<br \/>\n<\/code><span style=\"font-family: monospace;\">-nodebug<br \/>\n<\/span><span style=\"font-family: monospace;\">-profile<br \/>\n<\/span><span style=\"font-family: monospace;\">mobileDevice<br \/>\n<\/span><span style=\"font-family: monospace;\">-screensize<br \/>\n<\/span><span style=\"font-family: monospace;\">480&#215;816:480&#215;854<br \/>\n<\/span><span style=\"font-family: monospace;\">C:\\Users\\Jonathan\\workspace\\workingapp\\bin\/workingapp-app.xml<br \/>\n<\/span><span style=\"font-family: monospace;\">C:\\Users\\Jonathan\\workspace\\workingapp\\bin<\/span><\/p>\n<div>but in the non-working (new) app, the output was:<\/div>\n<p style=\"padding-left: 30px;\"><code>adl.exe<br \/>\n<\/code><span style=\"font-family: monospace;\">-nodebug<br \/>\n<\/span><span style=\"font-family: monospace;\">-profile<br \/>\n<\/span><span style=\"font-family: monospace;\">mobileDevice<br \/>\n<\/span><span style=\"font-family: monospace;\">-screensize<br \/>\n<\/span><span style=\"font-family: monospace;\">480&#215;816:480&#215;854<br \/>\n<\/span><span style=\"font-family: monospace;\">C:\\Users\\Jonathan\\workspace\\trycompile<br \/>\n<\/span><span style=\"font-family: monospace;\">C:\\Users\\Jonathan\\workspace\\trycompile\\bin<\/span><\/p>\n<div>so it seemed an adl argument issue.  This was not immediately obvious to me, even reaching this point took a couple of hours.  I had also found this <a href=\"http:\/\/bugs.powerflasher.com\/jira\/browse\/FDT-2407\" target=\"_blank\">recent FDT bug report on JIRA<\/a>.<\/div>\n<h2>Solution<\/h2>\n<div>I started mucking around with compiler settings, and eventually tracked it down into the <code>.settings &gt; launch<\/code> folder, for my app called &#8220;trycompile&#8221;, the file <code>.settings &gt; launch &gt; trycompile.launch<\/code>. In the working version, FDT had inserted the line:<\/div>\n<div>\n<p style=\"padding-left: 30px;\"><code>&lt;stringAttribute key=\"ADL_DESCRIPTOR_FILE\" value=\"bin\/workingapp-app.xml\"\/&gt;<\/code><\/p>\n<p>but this was absent in the non-working file. So I added the following line to that file:<\/p>\n<p style=\"padding-left: 30px;\"><code>&lt;stringAttribute key=\"ADL_DESCRIPTOR_FILE\" value=\"bin\/trycompile-app.xml\"\/&gt;<\/code><\/p>\n<p>When I added that line, the project worked (both desktop and laptop). Yay for me!<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>I really like working in FDT5 and was eager to try out mobile app development. The first test I did I had no problem, then all of a sudden, any new app was not launching, giving the error: application descriptor not found<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[17],"tags":[],"_links":{"self":[{"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/posts\/313"}],"collection":[{"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/comments?post=313"}],"version-history":[{"count":7,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/posts\/313\/revisions"}],"predecessor-version":[{"id":321,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/posts\/313\/revisions\/321"}],"wp:attachment":[{"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/media?parent=313"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/categories?post=313"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.eqsim.com\/blog\/wp-json\/wp\/v2\/tags?post=313"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}