Build After Update To Release 3

  1. ‹ Older
  2. 5 months ago

    Scott C

    Dec 5 Pre-Release Testers, Xojo Pro Nova Scotia, Canada
    Edited 5 months ago

    I ran across the #105 error recently myself, using 2017 R2.1 on macOS 10.12.6.

    #105 error in iOS

    I wasn't able to reproduce it reliably, so I didn't file a Feedback report. But after my little fix, it went away (including the temp folder).

    I hope that helps. Good luck.

    Edited: typo on the error number.

  3. I have discovered that release 2.1 also has this problem on my machine. I am suspicious that this problem may be due to the update to to High Sierra 10.13. I had not done any builds for some time, but I think everything worked OK on 10.12.

  4. Richard W

    Dec 6 Pre-Release Testers, Xojo Pro

    Same problem here using 10.13.2 beta 6. I would tend to agree that 10.13.x is still not ready for prime time.
    I finally added a build script that removes the previous build.

  5. Greg O

    Dec 6 Xojo Inc Somewhere near Raleigh, NC

    I think what we discovered is that the OS is holding onto the icon file and marks the bundle as “in-use” which caused this behavior. Also thought we’d fixed it in r3 but apparently not for everyone. :(

  6. Sascha S

    Dec 6 Pre-Release Testers, Xojo Pro Germany/W'haven

    Does it help to add the Folder in which you create the Build/Debug App, to the Folders ignored by Spotlight?

    I think it's in: System Settings > Spotlight > Privacy

  7. 4 months ago

    I have found that if I delete the Build file before entering a project (with the exception of one project), I can build multiple times with no error and subsequent opening of these projects (without deleting the Build file) also build with no error. There is one project that I have to delete the existing build before I can build without error and then subsequent Build attempts all have the Build error. There must be something about this project that produces the error but I can’t find what it is. if I find the problem I will post it here.

  8. Greg O

    Dec 8 Xojo Inc Somewhere near Raleigh, NC

    Check and see if they all have icons.

  9. Greg, I think you have hit on something here. If I delete the icon for the troublesome app, I can build successfully without having to delete the previous build file. The question now is how do I build apps with an icon? Thanks so much for this info, I was trying many things without success until your suggestion.

  10. Beatrix W

    Dec 9 Pre-Release Testers Europe (Germany)

    That the icon is the problem isn't exactly new. I think someone either on the forum or in the Feedback case tried to add the icon after building and ran into different problems.

  11. Greg, I am sorry I missed your earlier post about the icon problem. Also, I updated my Mac to 10.13.2 this morning and it did not solve the build problem. I don't see others complaining about the icon problem - does this mean that it is something unique to my Mac.

    Beatrix, I did not do any builds for quite some time so I just noticed the problem after the Release 3 update.

  12. Norman P

    Dec 9 Xojo Inc

    when you see this occur run

    lsof +D <drag the troublesome debug build into terminal so you get the right path>

    I'm VERY curious about the output as we do a very low level unlink to remove these files
    Unlink is what RM calls to remove files
    That they persist is VERY surprising

    I've seen Quicklook and LaunchServices holding onto fileslong enough that we do not successfully remove the entire debug build

  13. Norman, thanks for your input, but I am not comfortable doing Terminal stuff. I would prefer to wait for a XOJO fix if one can be found.

  14. I am wondering if XOJO could simply delete any existing Build file before a new build is performed, since you are going to overwrite it anyway?

  15. Tim J

    Dec 9 Pre-Release Testers, Xojo Pro Back in Phoenix, AZ USA (desic...

    @James H I am wondering if XOJO could simply delete any existing Build file before a new build is performed, since you are going to overwrite it anyway?

    They do remove the built app, but the system is holding on to the icon resource in some instances under 10.13.

    Also, if you're going to create software for a Mac (or Windows or Linux), you really should take the time to become "comfortable" with the terminal. For the Mac space, I recommend this book (and provide it for my tech team):
    Learning Unix for OS X - Dave Taylor

  16. Beatrix W

    Dec 9 Pre-Release Testers Europe (Germany)

    You can't make anything kaputt with the Terminal command. Quite a few tested this during the development phase of 2017r3 and it's really interesting to see that the fix still doesn't work fully.

    Have a look at the Feedback case at Feedback Case #49147 for details.

  17. Norman P

    Dec 9 Xojo Inc

    @James H Norman, thanks for your input, but I am not comfortable doing Terminal stuff. I would prefer to wait for a XOJO fix if one can be found.

    The reason I asked you to do that is so I can fix the issue

  18. James H

    Jan 5 Answer

    Have been away from xojo for a while, but can now report that my original build problem in early December has been solved. I can now build repeatedly without having to delete the previous build file. I assume this is due to the update to Mac OS 10.13.2 as nothing else has changed. Thanks to all who made suggestions to solve this problem.

  19. I must correct my previous post. I forgot that I had deleted the icons from the offending projects so they did multiple builds without the problem. When I put the icons back into these projects, the problem persists - File error 105 unless the previous build file is deleted. Other users don't seem to be seeing this problem so perhaps it is something unique to my Mac. For now, I just delete the previous build if I need to do a new build. Sorry for confusion.

  20. Richard D

    Jan 6 Pre-Release Testers Europe (UK, London)

    @James H I must correct my previous post. I forgot that I had deleted the icons from the offending projects so they did multiple builds without the problem. When I put the icons back into these projects, the problem persists - File error 105 unless the previous build file is deleted. Other users don't seem to be seeing this problem so perhaps it is something unique to my Mac. For now, I just delete the previous build if I need to do a new build. Sorry for confusion.

    what is the name of the icon that is causing the problem?

  21. 3 months ago

    Richard, the icon is a png file named football_ball.png. As far a I can remember, there was no problem with this icon until OS 10.13. I was using this icon for a long time without any problem, but at some point, it started giving the Build error. Looking over the history of this post, it seems to me that the problem is running OS 10.13 and doing more than one build (without deleting the previous build file) with a project containing an icon. Other users do not seem to be seeing this issue, but I can't explain why.

or Sign Up to reply!