Hi Jen,
Like you suggested, I tried building a sample project and install it using adb and it worked. I’m going to try and see what’s wrong my code or build settings then, but definitely it’s not the keystore.
I believe the solution is that you have a hidden “Icon” file in your project folder, I believe created by Glider (at least in my case). If you open terminal and navigate to your project folder and do an ls command, you should see it there. Do a rm to get rid of that file, rebuild and it should work.
I believe the solution is that you have a hidden “Icon” file in your project folder, I believe created by Glider (at least in my case). If you open terminal and navigate to your project folder and do an ls command, you should see it there. Do a rm to get rid of that file, rebuild and it should work.
I saw this same behavior. I use Glider on OS X Mavericks, though I used to see this problem on previous versions of OS X. I haven’t figured out when Glider makes these ‘Icon’ files (or if it’s really Glider that makes them), but they seem to creep up whenever I create a new project or copy a directory into an existing project.
Deleting the files (you have to go through every directory in the project to be sure) fixes the problem completely.
I wish adb would give a more useful error message, though I suspect the mismatch might be occurring somewhere earlier in the process. Perhaps Corona calculates the certificate erroneously due to the odd nature of these files (or strips them _after_ calculating a certificate)?
Glider comes up frequently with this issue. The other thing we found is on iOS you can change the icon on a folder (perhaps even coloring/tagging it might cause the issue) tends to drop an Icon file in the folder.
Rob
I saw this same behavior. I use Glider on OS X Mavericks, though I used to see this problem on previous versions of OS X. I haven’t figured out when Glider makes these ‘Icon’ files (or if it’s really Glider that makes them), but they seem to creep up whenever I create a new project or copy a directory into an existing project.
Deleting the files (you have to go through every directory in the project to be sure) fixes the problem completely.
I wish adb would give a more useful error message, though I suspect the mismatch might be occurring somewhere earlier in the process. Perhaps Corona calculates the certificate erroneously due to the odd nature of these files (or strips them _after_ calculating a certificate)?
Glider comes up frequently with this issue. The other thing we found is on iOS you can change the icon on a folder (perhaps even coloring/tagging it might cause the issue) tends to drop an Icon file in the folder.
Rob
I’ve been running into the same issue, and this thread was very helpful.
From what I can tell, the invisible Icon file (mine is always named “Icon?” in the Terminal) is created by Dropbox. Whenever I build I have to pause my Dropbox syncing and remove the file in order to get a clean build.
- David
On a Mac, anything you do to the folder, like give it a color, a custom icon, etc. generated that Icon? file. It can be pesky to get rid of because you can’t see it in the Finder.
Rob
I’ve been running into the same issue, and this thread was very helpful.
From what I can tell, the invisible Icon file (mine is always named “Icon?” in the Terminal) is created by Dropbox. Whenever I build I have to pause my Dropbox syncing and remove the file in order to get a clean build.
- David
On a Mac, anything you do to the folder, like give it a color, a custom icon, etc. generated that Icon? file. It can be pesky to get rid of because you can’t see it in the Finder.
Rob
Thank you guys!
That invisible icon generated by Glider was messing with all builds here (iOS & Android).
My android builds were not installing due to “Failure [INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING]”
My iOS builds were installing via Xcode but when I tried to install them via TestFlight they didn’t work (I was receiving an error message when finishing downloading: "“Unable to Download App. ‘[APP NAME]’ could not be installed at this time” and the device log would give me some strange errors like:
Aug 25 15:39:22 Renatos-iPhone installd[3802] \<Error\>: 0x283000 do\_preflight\_verification: Could not verify executable at /var/tmp/install\_staging.oBHaXg/foo\_extracted/Payload/IndiqueumHeroi.app Aug 25 15:39:22 Renatos-iPhone installd[3802] \<Error\>: 0x283000 install\_application: Could not preflight application install
Now everything works fine after deleting that invisible Icon file.
Any thing that changes the OS’s Icon (color it, add a graphic to it, etc.) will create an invisible Icon file that may hose your build.
Rob
I just noticed that when you start using CoronaViewer, Dropbox creates the Dropbox/Apps/CoronaViewer and inside the directory it automatically creates 2 invisible files: .dropbox & Icon. So, since I was also using CoronaViewer, I think it was Dropbox that added that invisible Icon file to my project.
Just registering here for future developers that see that problem.
You can exclude the .dropbox file for certain. The Icon file has a couple of non-printable characters and it’s probably guilty for breaking builds. You might be able to exclude it as well. I’ve been copying the files to a non-dropbox folder to build that doesn’t have an Icon on the folder.
Rob
Yes… I thought that it was a LuaGlider file but it is really Dropbox fault.
Do you think that adding these 2 files (.dropbox and Icon) to the excludeFiles list on my build.settings would be sufficient ?(I will try that anyway and post here the results)
I already developed a tool here to be able to use the CoronaViewer with any project without having to copy/move files around, so if the excludeFiles table works, I would use it as default for all of my projects.
I think the Icon file has some hidden characters. You could try excluding “Icon” and see what happens.
Rob
Rob, the file name is “Icon\r”. How can we escape this character so that Corona will ignore it (can’t put the actual return character in of course)? You guys should really consider making this default behavior.
My Mac identifies the file as “Icon?” (on the terminal. Didn’t try using that on the excludeFiles)
The ? is a placeholder for any character not supported in output. The actual file is explained here: http://superuser.com/questions/298785/icon-file-on-os-x-desktop
I thought I tried ignoring with the ?, but I must have inadvertently reinstalled an old build instead. Tried again and it looks to be working!