I'm trying to validate my project in xcode to prep it for upload to the store and I've run into this error:
"iTunes Store operation failed.
Invalid Bundle Structure - The binary file [bundleidentifier]/GooglePlus.framework/GooglePlus' is not permitted. Your app can't contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles...etc"
and
"iTunes Store operation failed.
Invalid Bundle Structure - The binary file [bundleidentifier]/gpg.framework/Versions/A/gpg' is not permitted. Your app can't contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles...etc"
Anyone have any idea how to solve it? Your help is appreciated.
Remove GooglePlus.bundle from your project.
Related
I am new in Cmake thats why I will write story detailed.
I trying to build one lib under windows and that lib depends on other lib. (libmatroska depends on libebml) source libmatroska and source libebml
Fortunately both libs can be build with cmake.
I built libebml successfuly with cmake. And also built binaries using VS studio.
Then I tried to deal with libmatroska:
During first try I got:
Could not find a package configuration file provided by "Ebml" (requested
version 1.3.5) with any of the following names:
EbmlConfig.cmake
ebml-config.cmake
at libebml sources I found EbmlConfig.cmake.
I Type export Ebml_DIR=D:/work/mkv/libebml and try again.
On second run I got:
Could not find a configuration file for package "Ebml" that is compatible
with requested version "1.3.5".
The following configuration files were considered but not accepted:
D:/work/mkv/libebml/EbmlConfig.cmake, version: unknown
And after few hours I am still stuck on it.
I can't understand root of this error.
Is it something wrong with EbmlConfig.cmake?
... or maybe I specified path to wrong *.cmake file?
... or I need to install libebml some how before handling libmatroska?
I will be happy for any clue.
UPDATE:
Here EbmlConfig.cmake context:
include(${CMAKE_CURRENT_LIST_DIR}/EbmlTargets.cmake)
Where EbmlTargets.cmake is file generated while Ebml compilation.
I tried to change path inside EbmlConfig.cmake to global path. But got same error.
Also when I delete context of EbmlConfig.cmake I still have same error.
It looks like "default error when something goes wrong"
I was trying to run the video-demo sample application in the Affdex SDK, but ran into a linker error. In the in instruction page (http://developer.affectiva.com/v3/windows/) there is a point where it states:
"A dynamic library, opencv_ffmpeg.dll is required by VideoDetector". However, I could not find this .dll as part of either the SDK package or the github example code.
I downloaded the openCV version 3.1 which was mentioned as required dependency, but it did not have opencv_ffmpeg.dll either. It did have two files that seemed relevant : opencv_ffmpeg310.dll and opencv_ffmpeg310_64.dll. However, when I try to link the project with either of these files, I get the error:
Error LNK1107 invalid or corrupt file
So, I was just wondering what I'm doing wrong, and where could I find the correct opencv_ffmpeg.dll.
kind regards
A dynamic library, opencv_ffmpeg.dll is required by VideoDetector [c++] in runtime for the video decoding.
You can download the Affdex SDK 3.0 for Windows from the downloads page. Based on the architecture for which you downloaded the SDK for you can locate either opencv_ffmpeg248_64.dll at C:\Program Files\Affectiva\Affdex SDK\binor opencv_ffmpeg248.dll at C:\Program Files (x86)\Affectiva\Affdex SDK\bin.
I am getting a strange error on the build server, this does NOT happen locally.
Error during file generation. The target file 'C:...\AcceptanceTest\Features\HelloWorld.feature.cs'
is read-only, but different from the transformation result. This
problem can be a sign of an inconsistent source code package. Compile
and check-in the current version of the file from the development
environment or remove the read-only flag from the generation result.
To compile a solution that contains messaging project on a build
server, you can also exclude the messaging project from the
build-server solution or set the msbuild
project parameter to 'true' in the messaging project file.
I'm not sure what to do to fix this, I don't have a "messaging" project (or know what is being referred too). And the code is the latest
This is the full message (some folder names have been obfuscated):
13>C:\Builds\2\Services\PService\src\packages\SpecRun.Excel.1.1.0\tools\TechTalk.SpecFlow-buildfix.targets(47,5):
error : Error during file generation. The target file
'C:\Builds\2\Services\PService\src\PService\Test\PService.AcceptanceTest\Features\HelloWorld.feature.cs'
is read-only, but different from the transformation result. This
problem can be a sign of an inconsistent source code package. Compile
and check-in the current version of the file from the development
environment or remove the read-only flag from the generation result.
To compile a solution that contains messaging project on a build
server, you can also exclude the messaging project from the
build-server solution or set the msbuild
project parameter to 'true' in the messaging project file.
[C:\Builds\2\Services\PService\src\PService\Test\PService.AcceptanceTest\PService.AcceptanceTest.csproj]
13>C:\Builds\2\Services\PService\src\packages\SpecRun.Excel.1.1.0\tools\TechTalk.SpecFlow-buildfix.targets(47,5):
error : Could not find file
'C:\Users\tfsbuild\AppData\Local\Temp\tmpPWithData.feature.xlsx.cs'.
[C:\Builds\2\Services\PService\src\PService\Test\PService.AcceptanceTest\PService.AcceptanceTest.csproj]
13>C:\Builds\2\Services\PService\src\PService\Test\PService.AcceptanceTest\Features\PWithData.feature.xlsx
: error : Generation error: Could not find file
'C:\Users\tfsbuild\AppData\Local\Temp\tmpPWithData.feature.xlsx.cs'.
[C:\Builds\2\Services\PService\src\PService\Test\PService.AcceptanceTest\PService.AcceptanceTest.csproj]
Delete HelloWorld.feature.cs from source control.
TFS will checkout files as read-only during a build and so SpecFlow fails to re-generate the file because it already exists and SpecFlow doesn't overwrite read-only files.
I created a new request for SpecFlow to not automatically add the file to source control here: https://github.com/techtalk/SpecFlow/issues/592
I'm not sure what the messaging project refers to, that's something I haven't seen before.
However the error reads as if the problem is due to an issue with the generation of the *.feature.cs from the *.feature file, but I am confused as to why this should be happening on the build server. Normally the generation of *.feature.cs occurs in the IDE when you save the *.feature file. This gets checked in and with some version control systems (VCS) you may end up with a read-only file status.
Your error reads as the build server is trying to re-generate the *.feature.cs file and cannot overwrite it.
Some things to check;
What VCS are you running? Does it leave checked-in files as read-only?
How are you building the files on the build server? Is there a custom step involved, or is it just a simple compile?
Can you replicate this error on your machine by setting the *.feature.cs to read-only and running the same build script on your local machine?
Good luck.
I have a WIX package - created using Wix Toolset 3.7, which is strangely failing on a specific environment with the following message,
ExecXmlFile: Error 0x80070005: failed to load XML file:
\sharep001\share\IIS\pre\EAT\Website\CalculationService\Web.config
MSI (s) (70!FC) [11:15:37:491]: Product: EAT 1.0.0.0 -- Error 25531.
Failed to open XML file
\sharep001\share\IIS\pre\EAT\Website\CalculationService\Web.config,
system error: -2147024891
Error 25531. Failed to open XML file
\sharep001\share\IIS\pre\EAT\Website\CalculationService\Web.config,
system error: -2147024891
CustomAction ExecXmlFile returned actual error code 1603 (note this
may not be 100% accurate if translation happened inside sandbox)
Why I say the behavior is strange is because,
The same package I can install on the local directory on the webserver, no errors reported.
The same package I can install on another UNC directory, no errors reported.
Why is it failing?
- The XML transform step only gets called after the directory is created, files are dropped, iis website is created, etc. So, hard to explain why, does not seem like a permission issue.
Any idea how I can debug this?
It is strange that the path does not contain a root drive specification. Is it possible that this file is on a different drive than where the custom action is executing and thus the relative path is not being found? I would first try to provide a full path to the file and see if that addresses the issue.
To debug, you could go hardcore and grab the sources and pdbs .zip files for the WiX toolset build you are using then use MsiBreak environment variable to get attached to the custom action .dll. From there, you can debug through the ExecXmlFile() function to see the actual return result. You could also inspect the machine just before/after the error occurs to see if the file is locked or otherwise inaccessible.
Good luck!
Check if file has correct UTF-8 encoding, my fault was a missing BOM
Failed to open XML file , system error: -2147024786
I just addred Growl integration to an Xcode application. The source compiles and runs correctly under the Debug target while testing.
When I try to build the Release target however, I get the following error and I'm not sure why, or whoe to resolve it.
Building target “EchowavesNotifier” of project “EchowavesNotifier” with configuration “Release” — (1 error)
cd /src/echowaves-notifier-osx
/Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -strip-debug-symbols -resolve-src-symlinks /src/echowaves-notifier-osx/Growl.framework /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks
strip: for architecture x86_64 object: /src/echowaves-notifier-osx/Growl.framework/Versions/A/Growl malformed object (unknown load command 5)
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
pbxcp: warning: couldn't strip: /src/echowaves-notifier-osx/build/Release/EchowavesNotifier.app/Contents/Frameworks/Growl.framework/Versions/A/Growl: No such file or directory
Build failed (1 error)
Is it some kind of 64-bit (x86_64) related issue?
I ran into this recently when upgrading Growl, and several other groups have noted it (I found some traffic on the Unison.app list). What seems to be happening is some kind of mismatch at the link step, though I haven't been able to isolate it.
The solution I've found so far is to delete the entire build/ directory and rebuild (which is much more than just doing a "clean" in xcode). So far I have not seen the problem recur for any developer after performing that. Please let me know if this does or doesn't fix your problem, since I want to know whether I need to continue hunting solutions for this problem should it come back.