.app file not get install using package installer - xcode

I have created a package installer using Xcode's PackageMaker. I want to install a .app file into the applications folder, but when i am running installer package, it's showing that the software is installed succesfully. When i checked the applications folder, the application i m installing is not there. Can anybody help me to solve this?

While the Installer is still running you can select the Window menu and choose the Installer Log option. In the Installer Log dialog select the 'Show All Logs' from the drop down control. This might help you determine where the Installer put your .app or what happened.
BTW I'm seeing the same thing with a .pkg I have written and would love to hear if you find a solution.

I ended up getting things working with my .pkg by making it install into /Applications/ with the trailing slash. I had previously been just using /Applications. Maybe that works for your package?

The issue is that the installer can upgrade packages even if their not located in /Applications. So if there is an application with the same name or it already exists on your hard drive it will try and install over that. To fix it click on the item your trying to install in the content pane then click on the components tab and make sure the "allow relocation" check box is unchecked. Should work perfect after that

Related

IntelliJ IDEA can't open projects or add SDK on macOS Catalina

If I open IntelliJ IDEA and try and import any project or open any folder containing a project, nothing happens, I'm just returned to this screen.
Earlier on, before I moved my project files around, I tried to set a new JDK for a project and i clicked add SDK and then selected Java 12 home and again it returned to the screen without adding anything.
Is there some permission I need to grant to IntelliJ Idea?
Seems to have started since installing MacOS Catalina.
It's a known issue specific to the recent macOS Catalina update. Please follow YouTrack ticket for updates.
You can also help by providing the following information in YouTrack:
Open the file chooser, select a directory (but don't open it yet), take a screenshot, then open a directory; then attach idea.log and the screenshot (a path to a project and a time of the operation are needed, too, but they should be guessable from the screenshot).
As a workaround until this issue is resolved you can add -Dide.mac.file.chooser.native=false in Help | Edit Custom VM Options and restart the IDE.
Mac OS, Mojave or Catalina,
Exit intellij first,
Apple menu  > System Preferences, click Security & Privacy, then click Privacy.
Click the lock , then enter your administrator password.
From the list of items on the left, select Full Disk Access.
Add Intellij(or other whatever app having this problem) to the apps allowed full-disk access by using the add button.
Lock and try again.
Hope this will help.
Ref from apple support of other things, but I tried, it works!
I can temporarily open things by dragging a folder to that window it seems, but its' not ideal.
Faced the same problem after the (PyCharm) update. Workaround: Go back to the old version.
https://stackoverflow.com/a/59858297/7024760

Removing plugins from a .pkg file

I am using an user registration plugin that is included in iceberg installer. Registration dialog is appeared and everything works fine in the installer.
But the problem here is when i right click the .pkg file and go to "Show Package contents" there is the plugin folder which i included in the package and i can delete this simply.
Is there a way to prevent this by disabling "Show Packages Contents" or any other ways available to prevent this ?
Also there is "Flat Package Editor" in which we can remove the files within the package created using "Package Maker".
Is there a way to prevent this also ?
Thanks in advance,
Regards,
Balaji
No, you can not restrict a user to delete any content inside your application bundle.
However, you can use digital signatures to mitigate the problem.
Make sure that the installer is signed before you ship it. In that case, if a user deletes any content from inside the bundle, OSX will complain that the app is broken.
But, be aware that a person having decent knowledge about .pkg files can still bypass your registration.
For example, if I do a silent installation of your pkg, it will not show me the registration dialog.
You should probably look at implementing this registration inside your application as well. So, if a user bypasses the registration in your installer, your application must be able to detect that and show the popup again.

ClickOnce Applications Won't Install on Windows 7, Application Cannot Be Started, Contact the Application Vendor

I am trying to install Github for Windows which is a ClickOnce application, however I am unable to start any ClickOnce application. I receive a pop up error saying "Application cannot be started, contact the application vendor".
I have seen that other users with this error have solved it by deleting the '2.0' folder in there 'users/USERNAME/AppData/Local/Apps/2.0' location. However, I do not have an 'Apps' folder in my 'AppData/Local' location and therefore unable to delete anything from it. I have tried creating an 'Apps' folder there and then trying to install the application but I receive the same error. When I run the following: '%UserProfile%\AppData\Local\Apps\2.0' it says that it refers to a location that is unavailable.
I have contacted Github support and they told me the same thing about deleting the '2.0' folder but alas I do not have the 'AppData/Local/Apps' location. They also told me to clear the cache by running this: rundll32 %SystemRoot%\system32\dfshim.dll CleanOnlineAppCache but that did not solve the problem either.
I do not have any anti-virus or firewall turned on either. I have also tried installing a different ClickOnce application and I received the same error. Is there some other folder I need to delete or some setting I need to change to get ClickOnce applications to start?
By Changing to Net Framework 4.0 got me working, changing and delete 2.0 made no difference but deleted the other apps.
The other apps were reinstalled automatically so no biggy, will try install latest 4.51 later.
I know this is a really old question. You should have a Apps folder at '%UserProfile%\AppData\Local\Apps\2.0'. You are probably unable to see the folder because you haven't enabled viewing of hidden folders in windows explorer. To resole this, launch windows explorer "windows key + e", hold down Alt and hit T (tools menu) then click folder options, click the "view" tab and then select:
"show hidden files, folders, and drives"
Uncheck:
"Hide empty drives in the Computer folder"
"Hide extensions for known file types"
"Hide protected operating system files (recommended)"
Note, not all of these are required to see the hidden folder "apps", this is how I always configure my setup though.
After this you should be able to see the folder at :
'%UserProfile%\AppData\Local\Apps\2.0'
Deleting the 2.0 folder usually works but you are also deleting any other click once applications that have been installed.

MonoMac Package Does NOT Include Images

I have several images and one application icon in my MonoMac application, all with build action set to "content", but when I build the installer (.pkg) file and install it on another machine, none of the images are available! Is this because I'm using the free version of MonoDevelop instead of Xamarin Studio? Any help would be greatly appreciated!
EDIT 1: On the test machine, I went into "Show Package Contents/Resources" and manually changed the permissions on the images from "Everyone - No Access" to "Everyone - Read/Write", and now the images are available in the application! The obvious problem is: how do I build the package so the images are installed with these rights? Thoughts?
I was finally able to get my images to show up by moving them into the resources folder and changing some path information. I still can't get my application icon to work correctly, but I'll post that question separately. Thanks.
Try setting the build action to BundleResource

How do I Create a link to an executable Installed by Visual Studio Setup Project

I am working on a visual studio setup project. I want the setup project to install the executable for a windows forms project, and then put a link to that executable in the Programs Menu on the target machine. In the Setup Project I clicked 'Add'-> Project Output... and selected the Primary Output from my WindowsForms App. So that should install the program right? Ok, so next I went to the File System on the Target Machine, right clicked on the Primary output from WindowsForms App and said Create Shortcut. I then moved that shortcut into the User's Programs Menu folder.
I tried running the installer and it works ok but for some reason whenever I click shortcut that is in the Programs Menu It actually installs the program before running it every time. Why does it do this? Did I add a shortcut to the wrong thing? If I navigate to the directory application directory and click the .exe file it just opens the program without doing any install. Does anyone know what is going on?
I read somewhere that I could actually make a shortcut in windows explorer that targets my output .exe and then add that file to the installer project but I can't see how that would work on every machine it gets installed on.
I think this is how I did it... been a while tho.
Application Folder
Primary Output From MyProjectName (Active)
Right-Click => Create Shortcut
Then
Users Program Menu
Right Click => Add Folder
Go back to "Application Folder"
Move the shortcut over to the program menu
Rename it to whatever you need. The "Type" should say "shortcut"
Is that kinda what it looks like for you right now? Something in
* User's Program Files
* My App Folder
* Start My Application (shortcut)
And need I say, MS's install projects are a nightmare :) Just open the .VDproj and look. I never thought i'd say I like the csproj xml format, but in comparison...
The problem was not actually in how I was creating my shortcut but rather what the shortcut was pointing too. The executable that the shortcut was targeting was not in the main installation folder and for some reason it didn't like that. Restructuring the install directories a bit fixed it.

Resources