The file "Demo" Couldn't be opened because you don't have permission to view it - xcode10.1

This question was asked several times in StackOverflow.
The file couldn’t be opened because you don’t have permission to view it
The file “ ” couldn’t be opened because you don’t have permission to view it
File couldn't be opened because you don't have permission,
The file “***.app” couldn’t be opened because you don’t have permission to view it,
and etc
It seems like the problems everyone faced is the same Xcode error,
like below, but totally different causes.
For me, the error will appear when I use the wrong Building Setting.
So Why Xcode gave the same error to the specific problems. Or In the
eyes of Xcode, these problems belong to the same type of error, so how
does Xcode classify these errors?

Related

Anylogic - unable to open model

Yesterday I was working on a file model in Anylogic.
Today I tried to open it and I get the error "Unable to open the model. Invalid project file format".
I'm able to open any other models. I tried to delete the .metadata folder but didn't solve the problem.
If anyone knows how to solve it, it will save me!
Thank you very much.
I encountered this problem recently.
In my case, the problem was caused because I copied and pasted Parameter descriptions into the Parameter Description text box from Adobe. Once I typed them in instead, no more problem.
The solution, as always, is to "Save As" frequently during model development.

App Store Connect Operation Error Transporter Issue

I am trying to upload my app however I keep having this error pop up. I'm not sure what caused it as I didn't really change anything but I can't seem to fix it. It looks like a file is missing. I've tried reinstalling Xcode but that did not resolve anything. Any help is appreciated.
Okay, I found a fix. It was actually really simple. I just deleted the file /Library/Caches/com.apple.amp.itmstransporter and the files and all of its components were regenerated correctly when uploading to App Store Connect.

Not able to archive Swift app and upload to the app store without "Your app can't contain standalone executables or libraries" error

After trying to investigate this, I've seen this in a few other places, namely the Flurry Analytics framework, but their solutions don't seem to apply to my issue.
The error is referencing a file with my app's name and a .o extension
My build log shows it twice under two "CompileSwift normal arm64" sections:
"/Users/Admin/Library/Developer/Xcode/DerivedData/App_Name-fglhmhjmskcjuedbcbpinrnjxaey/Build/Intermediates.noindex/ArchiveIntermediates/App
Name/IntermediateBuildFilesPath/App Name.build/Release-iphoneos/App
Name.build/Objects-normal/arm64/AppNamePrefs.o" -o
Searching for anything .o in Xcode turns up nothing, but maybe I could navigate to what it shows in the build log, but I don't know how that would solve my issue, aside from attempting to delete it, but I'm not sure if it's the right approach because I have no idea what this file is for.

Strange situation give error: "The application bundle does not contain a valid identifier."

Today I experienced a very strange behavior with my XCode (using Version 4.2, iOS 5.0).
I read some another questions, but my problem is diferent and I never before had this issue.
So, XCode gives me the error "The application bundle does not contain a valid identifier." when I'm trying to run my app on a device (in the simulator just simply does nothing).
I'm sure that the project is correctly set, the bundle ID is correct, my certified is also correct..
I already try a lot of different approaches to solution the problem. Then I realized that it just gives the error when I add a folder to the project with the options "Create folder References for any folder added" selected (like the picture).
I have another apps with folders with folder references, and don't get any error..
Resuming: If I add the folder I get the error, If I don't add a folder, the app runs without any problem..
Could someone help me here trying to figure out whats happens (it's driving me mad).
Thanks!
EDIT:
I managed to mend the problem. I was adding a folder called "Resources", changing the folder name stops giving me the error.
But I would like to know/understand why was I getting the error..
Thanks
I managed to mend the problem. I was adding a folder called "Resources", changing the folder name stops giving me the error. But I would like to know/understand why was I getting the error..
Anyway, not a problem anymore..
I'm missing the target name after the icon at the Add to targets. Got lost somewhere?

Couldn't install Ad-Hoc in iPhone 3.0 OS?

I've created an Ad-Hoc of my iphone app, but i couldnt install it on my iPhone (upgraded to iPhone OS 3.0). And also i created new provisioning file and plist file but it still shows error:
The application was not installed on th iPhone "Unknown" because an unknown error occured (0xE8008017)
Please send me a solution..........
I saw the 0xE8008017 when dragging a .ipa file that I created into iTunes, but NOT when dragging the .app folder directly into iTunes.
Update: There seem to be lots of reasons why this can occur:
1) You should use "ditto" instead of "zip" to create the .ipa file, as that is what gets used if you use Finder and choose "Compress":
ditto -c -k --sequesterRsrc Folder OutputFile.ipa
2) This link has a comment explaining the error is due to stale resources, i.e. you have a file in the .app bundle that has not been code signed. Check that all the files in your binary have a corresponding entry in the CodeResources file (except those explicitly excluded in ResourceRules.plist).
If you are trying to debug this problem you should check if dragging the .app folder into iTunes directly works. If it does, look for a problem with your creation of the .ipa file.
On another occasion when I changed my Info.plist 'Bundle identifier' from com.domain.appname to appid.com.domain.appname it made iTunes report a 0xE8008019 error instead of the 0xE8008017 one (importing the .app still worked directly). I think using appid.com.domain.appname in the Info.plist is wrong, but I mention it here in case somebody is searching for that error code!
I solved one 0xE8008017 error by renaming one of my resources. It was a PNG file with the danish letter 'ø' in it.
I've seen one other report about 0xE8008017 where the fix was about a colon in one of the resource filenames.
I am getting the same error.
I looked for the names of the files in the resources.
But the names have only alphabets a-z and digits 1-9.
Only at couple of places, hyphen - and underscore _ have been used.
I don't think that can cause the issue.
What else can be the reason?
This is a generic error, and often the real error will be reported to the OS X console.
Fire up the Console app (should be in Applications, or use Spotlight to find it automatically), and scroll to the bottom. Look at the timestamps, and see if there's a detailed message.
I've several times used this to fix completely different bugs which use the same error message.
(sadly, Apple is very bad at writing error messages - you often find they didn't bother to write new text for the popup error, and re-use old text, so that you have to read the Console to find out the "real" error)
Alternative answer (I had this problem recently):
"Upgrade to iTunes 9"
A bunch of these "missing" error messages appear to have been added in iTunes v9, including some of the most common ones. I guess Apple just forgot to include them first time around...