ConfigData framework not compiling on upload to Apple Store - ios

I having some problem while uploading file to Apple Store.
After i generate the file (archive) i try to upload to Apple Store.
But i got a message:
This only happens when i upload to Apple Store.
I already try to generate file with AD Hoc, to upload to HockeyApp. This way, i don't have this problem.
An interest thing: When i remove this ConfigData.framework from Embedded Binaries, now i have another error during prepare to upload: "Code signing OmiseSDK.framework failed." Even remove those frameworks, when i compile project, any error appear. But after archive and prepare to upload file to Apple Store, i have those strange errors.
Could someone help?

Related

Unable to upload app to App Store connect

I am trying to upload my app to the App Store connect but I'm not able to.
I was testing my app using Xcode 12 and without realising it was beta software, I archived my app and uploaded it. Now when I click on submit for review it says Binary Invalid. Then, I realized that I wasn't supposed to upload it using Xcode beta. Now, when I try uploading it with Xcode 11.5, It isn't letting me sign the app as I get an error saying Profile doesn’t include the com.apple.application-identifier entitlement .
I have tried the following Methods and none seem to work.
Close Xcode and Delete all provisional Files from ~/Library/ApplicationSupport/MobileProvisions/
2.Change the Bundle ID and also tried repeating (1.)
Create new certificates and profiles from the developer website(Both original and new bundle IDs)
Delete Xcode and reinstall it.
But in the end it only uploads it with Xcode 12 beta. (And throws an error saying Binary Invalid)
Please help me rectify this issue.
I struggled with this problem for two days, simple fix is to;
Build with 11.5
Archive / Upload with 12 beta
Here is the answer. Create your archive. In the organizer, select your archive. Choose distribute app. Then instead of upload, choose export. Export the archive to a folder on your hard drive. Now download transporter from the App Store. Transporter replaced "Application Loader" or whatever it used to be called in the developer tools menu of Xcode.
Now sign into Transporter with your dev account and upload the .ipa found in your exported archive folder using Transporter.
It will work under Big Sur!

How to deploy Xamarin iOS App with .dSYM file

I've been looking at Microsoft's docs for deploying Xamarin iOS apps to the app store:
https://learn.microsoft.com/en-us/xamarin/ios/deploy-test/app-distribution/app-store-distribution/index?tabs=windows
https://learn.microsoft.com/en-us/xamarin/ios/deploy-test/app-distribution/ipa-support?tabs=windows
We are currently building in Ad-Hoc and generating an .ipa file which we then upload to the app store via Application Loader. I managed to get the .dSYM folder to generate if I set the Project Properties -> Build -> Advanced -> Debugging Information to "Full" in Visual Studio.
Is there a better way to upload the .ipa, or a way to upload the .dSYM to iTunes Connect? As I read that Apple will automatically symbolicate any crash logs for you if the symbols were uploaded with the app?
Also, does setting the Debugging Information to "Full" change the actual .ipa in any way, or does it just generate the extra .dSYM file? Since setting it to "Full" I manually deployed the .ipa to our test device and one the libraries we use is now throwing an Object Reference exception.
Any help is greatly appreciated, thanks.
Is there a better way to upload the .ipa?
In my knowledge, there are two ways to upload .ipa file to iTunes Connect. One is XCode and the other is Application Loader.
or a way to upload the .dSYM to iTunes Connect? As I read that Apple
will automatically symbolicate any crash logs for you if the symbols
were uploaded with the app?
"you will be given the option of including the dSYM file when uploading your archive to iTunes Connect. In the submission dialog, check “Include app symbols for your application… DSYM files store the debug symbols for your app, it should exist at the machine that compiled the app binary. Read the answer in this thread would help you understand what is a DSYM file better.
Here is the document about Understanding and Analyzing Application Crash Reports.
or does it just generate the extra .dSYM file?
I don't think so, there is only a DSYM file after you compiled the app binary.
Since setting it to "Full" I manually deployed the .ipa to our test
device and one the libraries we use is now throwing an Object
Reference exception.
What is the Object Reference exception? Any stackTrace?

iOS - Error: This action could not be completed. Try Again (-22421)

I am trying to upload an iOS App to the App Store, using Xcode >> Organizer, but I got the issue This Action could not be completed. Try Again (-22421) as in the below image.
I tried to re-upload app many times but same error occurred
Here is snaps for an issue I'm getting :
What to do next? How can I upload my app successfully on store?
Tried using Application Loader app and now getting another error
Error ITMS-90168: "The binary you uploaded was invalid.
Use Application Loader to upload your app, as Xcode organizer can't upload file (rejects IPA) sometimes, without genuine reason and it's frequently occurring issue, with Xcode Organizer, that apple could not resolve permanently.
There are few other reasons also for such kind of error, like
Apple app upload server is not working properly (not in
connection or lost connection during file upload). Just wait and try
again later (may be after a day).
Fluctuation in your network
connection, during file upload.
You may not have added privacy
statements in your info.plist file.
Cocoa Keys: Here, is list of keys that you should consider to add in your info.plist file, if you have used that service in your application.
Solution for error code: 90186
Outdated application loader can be reason of this error. Use latest Xcode tool and use application loader from Xcode Tool.
Incorrect/invalid provisioning profile, associated with your build. Ensure, your have used correct provisioning profile (A provisioning
profile with Distribution/Production mode is require. A Development mode provisioning profile won't allow your to upload app on store.)
You can find latest Application Loader Tool from latest Xcode Tool: Xcode (Menu) ► Open Developer Tool ► Application Loader
This works fine with application loader. You will have to create ur ipa from the Xcode organizer and use application loader.
I am facing this issue for the last week. finally uploaded using application loader.

App ID not available while upload iOS archive file through Xcode 7.3

I'm getting following error while uploading archive file to the iTunes connect. I've already uploaded the same app's archive to iTunes twice, second time with different bundle version. And my internal test users were able to download and run the app just fine. But now I'm getting this error and I can't put my finger on something I'm doing wrong. Please do help me identify. Thanks.

Bundling app for app store distribution in Xcode 4.3

I can't believe how difficult it is to figure out the final process for building an app and getting it into the app store.
I've already prepped iTunes Connect with my app and it shows up in Application Loader.
I finally figured out how to "archive" the app, although none of the guides I found, including Apple's, seemed to really describe this process in complete detail.
Now I've got a .xcarchive package. For some reason, Application Loader will not let me select that kind of file. I read somewhere about needing to archive as a .zip file, so I tried that. Now Application Loader allows me to select the file, but after I click Send, it gives me this error:
"The application wrapper must end in .app."
What exactly is the process of archiving from Xcode 4.3 and getting the application uploaded into the app store?
In the XCode Organizer, does the 'Archives' tab allow ou to 'Distribute'? You should then have the option to 'Submit to the iOS App Store'.
This is described in more detail in Distributing Your iOS App.
The submission process doesn't get a lot of description because, when it works, it's quite simple. You never need to manually locate the '.xcarchive' package or '.ipa' file for your app store submission, only for testing or backups outside the app store. (You do need the archive package, but it's just quietly created and then uploaded by XCode.)

Resources