we have a XPage project in the Domino Designer. The project contains a file [database.nsf]/Code/Java/META-INF/services/com.ibm.xsp.core.events.ApplicationListener, which configures an com.ibm.xsp.application.events.ApplicationListener2 (same with com.ibm.xsp.application.events.ApplicationListener) to be executed when the application is created, refreshed and destroyed.
When I clean and rebuild the project I often get the following error in the problem section:
The project was not built due to "Resource already exists on disk: '[database.nsf]/WebContent/WEB-INF/classes/META-INF/services/com.ibm.xsp.core.events.ApplicationListener'." Fix the problem, then try refreshing this project and building it since it may be inconsistent.
This message is correct: the file is than available at that location. (You have to use the Eclipse view "Navigator" to see it, because the directory /WebContent/WEB-INF/classes is hidden in the project explorer.). When I open the file, it is empty. When I open the properties of the file, the size is "-1 bytes" (yes, minus). When I delete the file and refresh the folder in the Navigator, sometimes the file come directly back again with size -1 bytes, sometimes not. Sometimes the bug is solved after next clean project, but sometimes it reoccurs.
When the Designer compiles the project without error, the file has the correct content. At runtime this file is read and the ApplicationListener is executed, all events are fired as expected.
When the error occurs I could copy the content by hand into the problematic file and save it, delete the error task in the Domino Designer. Than the application also works fine (?).
I tried to create a minimal example, with a new project (nsf database) with only the configuration file (/Code/Java/META-INF/services/com.ibm.xsp.core.events.ApplicationListener) and the application listener implementation. Unfortunately the error does not occur.
The reason may be, that our project has a lot of files. We had this problem only with the services definition file. The problem also occurs when I rename the file (I appended two underscores as test).
The problem occurs with Domino Designer 9.0.1 and Notes 9.0.1 FP3.
Our project has an associated on disk project. But I had the same problem after removing the association. After associate again the problem was there again.
Is there a solution, except removing the file? (Whithout the file our application will not work correctly.)
Thanks in advance
Stephan Koops
I have had the same issue. In the 'Problems' view it lists 'The project was not built due to "Resource already exists on disk .../WebContent/WEB-INF/Classes/... then a file with a long hex name ending in .js.
Even simple Xpage changes would not appear on the browser no matter what I did with clean/build etc
What I find works is:
Open the 'Package Explorer' view, and in the first Folder called Local you will see a series of *.js files as mentioned above.
Delete them all.
Clean and build.
Bingo, my xpage is now working again.
Related
for my xamarin forms ios project I am getting an error when uploading an ipa file via the application uploader to apple.
missing required icon file ipad of exactly 167x167 for ipad pro.
The weird thing is I have actually included this file already in the media.xcassets.
any idea how to fix this?
So here is what I have found regarding this:
First, I would check that all the information found in this article is done (it talks about making sure your .csproj file has the needed references to the files):
https://alexdunn.org/2020/01/06/xamarin-tip-fixing-missing-ios-app-icons/
Second, I would check for miss-match of the case of letters in the file name between the json file in the Assets.xcassets/AppIcons.appiconset folder and your ios csproj file. For example ipad176.png is not the same as iPad176.png. This article explains it well.
https://blog.mzikmund.com/2020/05/the-mystery-of-the-missing-ios-app-icon/
Finally, neither of these resolved my problem. For me it seemed that one of the entries in my json file had something weird about it (event though visually it looked fine). I noticed that every icon entry in the json file AFTER the one that had something weird about it, showed as missing when I attempt to publish the archive. For me the easiest way to find the offending entry was to look for the first (i.e. earliest in the json list) icon entry that generated a missing icon error message when I published. Then, I unloaded my iOS project, opened the .csproj file for the iOS project in Visual Studio, and found the entry for that first app icon. I then copied the file name from the .csproj file and replace the file name in the json with the copied name, saved the json file and magically, I could publish my archive to the App Store.
We've recently created a second Company (id=3) based on a snapshot of our original company (id=2). I am attempting to publish a change to one of the Customization Projects in the new company. The file upload/save worked fine, but publishing leads to this error:
Publish Customization
Compiled projects: AA, BB, CC, DD
Validation has been started.
PX.Data.PXException: Cannot access the uploaded file. Failed to get the
latest revision of the file 9a65331c-ad34-477c-9759-2c414dead49f
at Customization.CstBinFile.GetFileFromDb()
at Customization.CstBinFile.SaveFiles(FilesCollection context)
at Customization.CstDocument.GetFiles(FilesCollection context)
at Customization.CstManager.ValidateDocument(CstDocument doc, Action`1
logMessageDelegate, Boolean patchLibInDB)
at PX.Customization.CstValidationProcess.ValidateCurrentDocument(Action`1
logMessage)
at PX.Customization.CstValidationProcess.CompileInternal()
at PX.Customization.CstValidationProcess.<>c__DisplayClass6_0.
<ProcessRequest>b__0()
This attempt represents the first publish within this Company.
I retried the upload/save, but still no luck.
Our version is: 6.10.0010.
How do I overcome this error?
Any help would be great. Thanks.
This can happen when the customization projects reference a file that has been removed from the database. Customization project still has the file reference ID but the database doesn't contain a file associated with that ID anymore.
If this is the cause of your error, you can correct it by removing and adding back missing files. To do this, go to the Files section of your customization project. Click on each file link.
If the file is missing in database, an error message popup will appear. For these, remove the file link reference and add it back again. When files are not missing, they will appear like in the screenshots below.
A weird one here. I've noticed that the 'Team Development - Sync with On-Disk Project' is not deleting files on my ODP. I'm not using automatic updating.
I've looked at the permissions on the odp/nsf folder, and I've noticed a little grey out checkbox which I can remove, but it pops back up immediately.
I've also tried opening up the security on the folder (right-click/properties/Security) and giving most groups superpowers, but no bananas.
Any help or hint would be appreciated.
Update: the deletions happen, but not immediately. I'm confused.
We have had issues not just with deletion but newly added files received via git, the only solution is to refresh both projects a few times and sync them both.
Another issue: I often lose some project settings, i.e. an additional source folder and a .jar file. It probably has something to do with replication, but it's impossible for me to find out exactly why this is happening.
I am hoping someone has had this issue before and can help me resolve. I was working on a company project. I had just finished up and needed to publish my project to the server. When trying to publish, I got the error "This file is currently not available for use on this computer."
So then I tried to open one of the .cs files of the solution, and the error occurred again from trying to open the file. So I tried to grab the latest version from TFS thinking it would give me whichever file is missing, but when I click "Get Latest Version" on the project, the error message pops up there too.
I thought surely I will be able to delete the project locally and then remap it, but I can't even delete the project off my computer, as the error message pops up halfway through deletion. When it occurs there, however, I do get "Error 0x800710FE: This file is currently not available for use on this computer."
Also have tried deleting offline cached files through Control Panel > Sync Center > Manage Offline Files > Disk Usage > Delete temp files
I got this error for a small, test solution that was not using TFS. The default file location is the documents folder, which in my environment is synced using the Sync Center. I moved all of the solution files to a new local folder that was not included in Sync operations and the error went away.
Conclusion: storing VS files in a folder managed by Sync Center is likely a bad idea.
I got this error when trying to save an excel file served from a webpage.
The solution for me was to save it under a different filename. Possibly because I previously had a file with the same name open in excel.
Using Xcode 4.0 sometimes when I remove resources from the project they still appear in the app when I run it, both in simulator and device. I remove the resource from the Resources group by removing reference only, but afterwards also remove the actual file in Finder, and yet the resource magically appears in the app.
Doing a project clean did not help.
Xcode 4.0 has a lot of problems managing its projects' "derived data". Try opening the Organizer (Cmd-Shift-2) and clicking the Projects tab. Select your problem project in the source list, then find Delete button next to the Derived Data section near the top. Go ahead and confirm deleting the derived data, then build again (this will take longer as Xcode re-indexes your project).
Does that fix it?
A bundle (and hence also an app) is just a directory, as seen from Unix and Unix-derived tools' point of view.
My guess is that they are still in the bundle because Xcode left a copy there once, and removing the originals in the source directory does not remove the copies in the built app bundle.
If you delete the app from the build directory (or the build directory altogether), you shouldn't see them any more inside a freshly built app.