The title error is what gets emailed after uploading the ipa via the application loader and below is the error that occurs in debug mode:
ERROR: "The framework
APPNAME.app/Frameworks/PersonalizedAdConsent.framework does not
contain a binary named PersonalizedAdConsent"
I've been getting this error in debug mode when trying to build the project. However, when I build it in Ad-Hoc mode, it builds fine and uploads on the application loader without any issues but then I get the following mail
"This bundle is invalid - The Info.plist file for
PersonalizedAdConsent.framework is missing or could not be read."
I've looked in the Info.plist file as well as .csproj file for this reference and I cannot find it anywhere.
Also searched online, can't find much about the PersonalizedAdConsent.
Any ideas?
So it seems like the issue was because of the following packages:
Xamarin.Google.iOS.MobileAds
&
Xamarin.Firebase.Ads
As far as I can tell, the app needs permissions to request consent to display ads or personalized ads (not too sure exactly) and it build correctly after removing these packages.
These were in a build that I've done on Windows for a different app which did not actually use them but VS for MAC gave me the issues and it turned out to be these packages that were causing it.
Hope it helps!
Related
yesterday I wanted to deploy some bugfixes for my app with Xcode 8.3, and ran while uploading into the error ITMS-90167: "No .app bundles found in the package".
This error is also shown already when trying to validate.
I did not change any code signing or mobile prov. files. Everything worked a month before.
I tested my code with ios 11 device support copied over from xcode-beta.
I read through all stackoverflow questions like this one, but I am not using Xcode 7 nor the application loader.
So I updated to Xcode 9.0, fixed some stuff due to the changes for swift 3.2, cleaned derived data etc., and tried again but still the same error.
Inside the ipa I can see the folder Payload/appname.app with its contents.
I am trying to deploy with fastlane, but also tried with Xcode, same results.
I have double checked code signing and recreated mobile provisioning profiles, revoked expired certificates and deleted duplicate/expired certs and keys in my keychain.
Xcode shows the profiles as eligible.
I also tried Automatically manage signing.
But nothing helped.
What does this strange error message really mean? And how can one debug/resolve this?
For me, the cause was a lack of space on my internal hard drive.
As far as I can gather, you need to have the same amount of space free that the unarchived xCode project takes up in order for the .ipa to be verified and uploaded to iTunes Connect - and that's through either xCode or ApplicationLoader.
After moving as much as possible over to a USB drive, the .ipa uploaded without issue.
I finally resolved the issue (after 2 days hard work),
it seems that it was a problem with a framework which I copied (with all sources) completely into my app-project and within this framework there was a info.plist (of that framework) which seems to confuse the validation step of the itsm transporter. Although the app was built and worked in simulator and on the device correctly.
The error message
ITMS-90167: "No .app bundles found in the package"
is very misleading - because there was an .app directory in the ipa and I first thought about signing issues. On the internet I didn’t find anything helpful with this error.
After I build the framework as separate project and included it correctly as a framework the validation was successful and I was able to upload my app.
If anyone knows more about this itms transporter and where to find some more documentation about possible errors, please leave a comment...
I have a iOS project, which link a binding library and correctly works without issues.
But when I send xarchive to my customer (so xarchive is signed from him), his app crashes at launch
It seem I miss something during the xarchive build?
Using an external library maybe I have to check additional options in xamarin studio build tab?
UPDATE:
pluggin iPad and launching Xcode devices windows, error is:
Runtime error: The assembly mscorlib.dll was not found or could not be
loaded
Searching I found this:
https://developer.xamarin.com/guides/ios/troubleshooting/questions/error-mscorlib-not-found/
This issue occurs when the hidden .monotouch-32 and .monotouch-64
folders are missing from the .xcarchive for signing / IPA creation,
triggering the runtime error.
How can I fix it?
I confirm issue was related to https://developer.xamarin.com/guides/ios/troubleshooting/questions/error-mscorlib-not-found/
My archive was uploaded to my owncloud company. Owncloud client doesn't upload hidden files/folders (as .monotouch-32 and .monotouch-64), so xarchive received by customer was different and smaller and did not contain all references.
I hope this help other people will have this issue.
I am following the Google Developer's guide for building a virtual reality application for the iPhone. I followed the initial steps and believe I have everything that is necessary installed. When I try to build the app from Xcode on my iPhone, I receive the file not found error on the "#import "GCSCardboardView.h"" statement in the TreasureHuntRenderer.h file. Am I missing a file or has the name of this library changed since the guide was published?
Thanks.
Just created an .apk with the Publish Android Application option, created a keystore with key and uploaded to the Google Play app store. Everything worked, but when I tried to download the app from the app store i got an error message resembling "The application has an incorrect signature". I thought the "Publish Android Application" part of Xamarin.Studio was supposed to fix everything?
I ran the following command on the .apk afterwards: jarsigner -verify -verbose -certs app.apk At the bottom it said the following: This jar contains entries whose certificate chain is not validated.
Please help, would love to have the app out today :)
My problem was simple. XamarinStudio was setup to use Java1.7, setting it to use Java1.6 fixed it :)
Recently I created an application for iPad. I created the binary(something.zip) and uploaded that via Application Loader, but the result of uploading was 'Invalid Binary' always.
and I received this email from apple when my app was denied from them due to the issue 'Invalid Binary' :
"Invalid Signature - Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target."
I searched the web from around the world to solve this annoying problem, but I cannot see the good answer. Here's the data of my application's info.plist :
Localization native development region : English
Bundle Display name : $(PRODUCT_NAME)
Executable fike : $(EXECUTABLE_NAME)
CFBunldleIconFiles :Icon-Small.png(29x29), Icon.png(57x57), Icon-Small-50.png(50x50)
(all files were created as 72ppi, RGB, flattened, No transparency)
InfoDictionary version : 6.0
Bundle name : $(PRODUCT_NAME)
Bundle OS Type Code : APPL
Bundle creator OS Type Code : ????
Bundle Version : 1.0
LSRequiresiPhoneOS : Enabled
UIPrerenderedIcon : Enabled
UIApplicationExitsOnSuspend : Disabled
UIStatusBarHidden : Disabled**
and I created this application with these tools -
cocos2d Ver0.99.4-rc3 /
xcode Ver3.2.5 64-bit /
iOS SDK 4.2
I tried to solve this problem for 3 days, but I couldn't.
Is there anybody who can solve my application's problem, It's an emergency issue of our company.
Thanks everyone
It seems like there are a LOT of causes for receiving this cryptic and mostly unhelpful email. Even after verifying the use of distribution certificates, cleaning & rebuilding my project, and checking with codesign from the command line (and following instructions from the email), no errors showed up—-but I'd get the "invalid signature" email right after uploading. All the solutions seem anecdotal and obviously depend on what secret error is causing the problem. I've spent the last week pulling my hair out, trying to figure it out for my app—-and finally got it successfully submitted today—so let me share my story and see if it's relevant to your situation.
In my case, I seemed to have a complex cause of having my Entitlement.plist set with an incorrect variable along with the holdover of an old provisioning profile (from a previous Xcode version?) buried deep in the project.pbxproj component of my Xcode project file.
The "aps-environment" variable in my Entitlements.plist was set to "distribution" instead of "production" (I swear I read somewhere in the developer docs that it was supposed to be "distribution"!) But fixing that alone wasn't enough to get my app through. (I must have submitted 100 different combinations of app configurations trying different variables!) Starting with the helpful suggestions from this post on another forum, I dug through the distribution profile and found duplicate entries for some variables. The duplicates had empty quotation marks (i.e. nothing set for the variable) or strange variables or old provisioning profiles which seemed to be causing problems (somehow). Cleaning this up and removing the duplicate lines with bad variables worked in my case. YMMV. But carefully examining the project files ("show contents" on the Xcode project file in finder) seems like a good idea for diagnosing. Good luck!
This is a very annoying issue, I spend a lot of hours in trying to find a solution but at the end this was corrected for me by removing the Entitlements.plist (as I understood it is only needed when deploying for ad hoc), removing any duplicate field in the Info.plist, setting the target to "Distribution" with the correct configuration of the certificates and using the method of "Archive" then "Validate" and at last "Submmit" in XCode