I have a Xamarin Forms App running on Android and iOS. Everything works fine on a Simulator and on lokal devices.
When I push the Buid to AppCenter, the Android Version gets build without a problem, but the iOS Build alsways fails with the following error:
(_CoreCompileImageAssets target) -> /Users/runner/runners/2.165.1/work/1/s/O365Info/O365Info.iOS/Assets.xcassets/AppIcon.appiconset/Icon1024.png : error : File not found: /Users/runner/runners/2.165.1/work/1/s/O365Info/O365Info.iOS/Assets.xcassets/AppIcon.appiconset/Icon1024.png [/Users/runner/runners/2.165.1/work/1/s/O365Info/O365Info.iOS/O365Info.iOS.csproj]
24 Warning(s)
1 Error(s)
Time Elapsed 00:01:01.73
[error]Xamarin.iOS task failed with error Error: /Library/Frameworks/Mono.framework/Versions/6_6_1/bin/msbuild failed with return code: 1. For guidance on setting up the build definition, see https://go.microsoft.com/fwlink/?LinkId=760847.
[section]Finishing: Build Xamarin.iOS solution.
In the first builds I didn't even had a Iconset called AppIcon.appiconset (my Iconset was named appiconset1) and the whole project didn't include a file named "Icon1024.png".
I then renamed my Iconset to appioconset and included a file named "Icon1024.png", but I'm still getting the same error.
No ideas, where this error might come from. Any suggestions?
Copied From ColeX at:
https://forums.xamarin.com/discussion/179775/build-error-with-missing-file-icon1024-png
Edit csproj file to remove the bogus entries (just delete them)
Ensure that a 1024*21024 png icon (file does not have Alpha or transparent) add into Assets.xcassets
Ensure the 1024 file information included in csproj file
Refer
Where to find 'Missing Marketing Icon'
https://forums.xamarin.com/discussion/129252/problems-with-missing-appicons-files
Related
This message just appeared out of nowhere even though I made absolutely no changes to the project. I have an Ionic cordova project that has been working for Android and iOS. The project builds fine in Visual Studio code for ios but when I open the project in xCode then I try to run the emulator in xCode I get the following error message:
Showing All Messages
unable to read input file '/Users/anonymous/Downloads/GoogleService-Info.plist': fopen(/Users/anonymous/Downloads/GoogleService-Info.plist, rb): Operation not permitted (1)
This is really weird because I haven't changed anything in the project so I'm not sure why it's trying to copy the .plist file from the downloads folder even though I've added it to the root project and the project\platforms\ios directory.
I found one solution that suggested adding the following to my config.xml:
That did not work. It actually caused build failures within Visual Studio Code.
Any help would be greatly appreciate. I'm not sure why this would issue would appear all of a sudden and the solutions I've seen online haven't been helpful.
I can see the .plist file in xCode
I’ve hit a problem working on iOS app development using Xcode outside Australia. Yesterday I was using Xcode inflight to compile and build the app and again for a short time upon arriving in Mumbai. The moment I removed an obsolete source file that was no longer needed in the app - i.e. just removing the reference and not deleting the file - I started getting compiler and linker problems.
The first message said my developer’s license had expired on March 27. But as I had used Xcode successfully on a daily basis since that date I assumed the problem might be related to Xcode being licensed only for use within Australia.
I logged onto the Apple Developers site where I agreed to accept terms and conditions and found no indication that my license had expired. So I restored the obsolete file and deep cleaned (command+option+shift+K) and rebuilt the project and now have multiple Dependency Analysis Warnings
Showing All Issues
error: failed to remove /Users/gs/Library/Developer/Xcode/DerivedData/xxx-ehpokmdvcmvspodonmckmjkbbfzj/Build/Products/Release-iphonesimulator/xxx.app/Info.plist: “Info.plist” couldn’t be removed.
Showing All Issues
: error: couldn't remove '/Users/gs/Library/Developer/Xcode/DerivedData/xxx-ehpokmdvcmvspodonmckmjkbbfzj/Build/Products/Release-iphonesimulator/xxx.app/Info.plist' after command failed: No such file or directory
Warning: The Copy Bundle Resources build phase contains this target's Info.plist file 'Info.plist'.
and multiple of the next warning
Warning: Multiple build commands for output file /Users/gs/Library/Developer/Xcode/DerivedData/SatGam-ehpokmdvcmvspodonmckmjkbbfzj/Build/Products/Debug-iphonesimulator/xxx.app/xxx.ipa
with the following files
xxx.app/xxx.mobileprovision
xxx.app/HelpText.xcf
xxx.app/ios_distribution.cer
xxx.app/PhoneDeviceID.txt
xxx.app/iOS Human Interface Guidelines: Icon and Image Sizes.pdf
xxx.app/AppleWWDRCA.cer
and two that I wouldn't expect to be part of an Xcode project
xxx.app/ios_development.cer
xxx.app/HelpText.xcf
(I attended AppleWWD in 2009. The GIMP project file was used to create .PNG assets in 2013)
I’ve repeated the deep clean procedure, closed Xcode, rebooted the simulator (hoping to erase any old versions from the simulator) but I can’t get rid of the problem. The multiple build commands suggest that Xcode is getting confused keeping track of old versions of the app.
Does anyone have any suggestions how I can restore Xcode to good health ?
My problem was solved once I understood and trusted what Xcode was saying. By selecting the target in the navigation window, I found many Info.plist files from earlier versions of my project. I carefully removed all but the latest version but still the project would not compile.
Then in the navigation window I discovered groups containing every file from earlier versions of my project. While I had made backups of my project I most certainly had not created groups within the project so I can only assume Xcode did this as it tried to make sense of backup copies I had made. There was even a project file in each group that allowed me to build and run earlier versions of the project successfully. Once I removed all references to these file groups from the navigation window, I was able to compile the latest version of the project successfully.
When I try to build an iOS application the XCode gives me the error which says
error: can't exec 'copypng' (No such file or directory)
Command copypng failed with exit code 71
So the problem isn't in missing PNG files or something like this, the problem is in the file that should does copy. I met this error for the first time and google says nothing.
How do I fix it?
I guess you stated, that you want to copy file, while there is no such file. Go to Project->Target->Build Phases->Copy Bundle Resources and find 'copypng' file (should be highlighted in red), and delete it (as it doesn't exist anymore).
On image attached to your question I see info that system couldn't copy files LaunchScreen-iPhoneLandscape.png and LaunchScreen-iPhonePortrait.png.
Normally, if you have Images.xcassets in project there should be "LaunchImage" image set. But it is alsoo possible that these .png files are placed directly in resources. Name for launch image used by target is set in "Asset Catalog Launch Image Set Name" in target's Build Settings. Make sure name for Launch image in xcassets (or in .png file in targets sources) matches.
If they are, check if target membership is correct (otherwise they won't be seen by compiler). Last thing to check - check potential problems with LaunchImage files according to the instructions in link from Adamsor comment.
For example - check if all necessary file sizes are in place, try opening and re-saving these images in editor. Maybe format is not right and that will be enough to fix it.
I've reinstalled XCODE and now all is ok.
I am going through the process of updating my swift project to Swift 2.0 on Xcode 7. The following error is being reported by xcode on building the project:
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1
This happens on either SwiftyJSON or SwiftSpinner frameworks (the compiler seems to pick one first at random and fail, so the error gets reported intermittently on either or the other). I have updated these frameworks to their xcode7/swift2 compatible branches but the project still fails to compile.
Just wondering if this is a situation other people are seeing when upgrading their project with cocoa pods framework dependencies, or if this is a compiler bug
For others with a similar problem try this:
Open Console (not terminal) and choose All Messages. Then try to build your Xcode project and when it fails take a look in the list there with any message that could be related to Xcode.
I found a message like this:
01/10/15 10.24.17,808 Xcode[53145]: DVTAssertions: Warning in
/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-8228/IDEFoundation/Playgrounds/IDEPlaygroundAuxiliarySourceCompilerOperation.m:311
Details: Unable to read diagnostics from file
"/Users/username/Library/Developer/Xcode/DerivedData/OurProject-diexylwajzhwgtfqdwiphjgzdwcy/Build/Intermediates/OurProject.build/Debug-iphoneos/OurProject.build/Objects-normal/armv7/CheckoutUserDataAdapter.dia"
(Invalid File): Invalid diagnostics signature Function: void
XCGenerateDiagnosticsFromFile(NSString *__strong, NSString *__strong,
NSDictionary *__strong, NSDictionary *__strong,
IDEActivityLogSectionRecorder *__strong, BOOL
(^__strong)(IDEActivityLogMessage *__strong)) Thread: {number = 250, name = (null)} Please file a bug at
http://bugreport.apple.com with this warning message and any useful
information you can provide.
This gave us info that the error was in CheckoutUserDataAdapter.swift.
After trial and error we found that the problem was it was calling a method from its super class that it overrides from its super class. Somehow it could not find the correct method. We fixed it by adding super.methodCall() in CheckoutUserDataAdapter.swift - but that of cause should not be needed. I have filed a bug report.
Check Build Phases - Compile Sources for deleted files, or files with a blank icon, once this file was removed the error was gone
Thanks #Dug for the Build Phase tip. I ended up going a different direction than the deletion...
After checking Build Phases - Compile Sources, find the files that are grayed out (don't currently have a link to an actual file) to identify the files in question.
If the files are still being used, then find them in the Project Navigator (left hand column) and you'll see that they're colored red because Xcode only has a reference and not a location for the actual file.
Select each red file and then head to the File Inspector (right hand column). You'll see "Location". Locate your files by clicking the gray folder and finding them in the file structure outside of Xcode.
If you're working with a repo, you may find it easier to simply remove the red files, choose File > Add Files to... and simply re-add them so the link is more generic rather than pointing directly to your machine's file location.
This happened to me after a project file merge in which I'd been branched from the main repo for quite a while so a handful of file locations were lost in the merge.
I'm playing with IwUI RSS sdk sample. I made a change of adding a link label to feed page (2nd page). I made this change by copying the description CIwUILabel block and renaming it to say 'linkLabel' and accordingly added that as an element to the CIwUIElement 'Lables' just below Title element. This works fine in x86 marmalade emulator, GCC ARM Debug emulator.
But when I take this to BlackBerry device, it breaks with the error - "Element '' does not have child with name 'linkLabel'. Why it is saying element ''?
Does it mean that my edits in IwUIItems.ui are not getting into device build?
I guess your changes didn't get included in the .bin file. The .group file or .ui file doesn't get included in the GCC build, you need the corresponding .bin file, which you'll get after loading the .group file in x86 simulator.
Just delete the data-ram folder, clean your project, re-run the x86 simulator, make sure UI.group gets loaded before you quit.
optionally you can even delete the VS project folder to get a perfectly clean build. Double clicking on mkb will recreate the project again.
If anybody stumbles on this, please find the details below -
As #Creator said, my changes did not get into the deployment package but the reason it was running fine in the Marmalade simulator does not allow to believe this. The reason was that the changes were getting in the .bin file correctly. But the deploy tool was looking for that file in data folder. There was an old file available and that was getting into my deployment package.
So I have to copy .group.bin file from data-ram\data-gles1 to data folder after running the application in x86 debug mode. Then build the deployment package for BlackBerry 10
For WP8, we have to copy .group.bin file form data-ram\gles2-dx11 to data folder.