My ios application was rejected automatically by the app loader and itunes connect.
I sent an email to chartboost, it says some of their partners experience this issue.
and send me a link to follow the steps.
uniqueIdentifier is called in chartboost
Upon trying out the command within the project, only chartboost sdk is detected with the function name.
I have follow the steps in the link, but the application is still rejected.
The charboost sdk in question is 3.2.1, the latest as if 2nd of Oct 2013.
Any idea what other issues can it be?
I'm having the same issue now as well. Email sent to Chartboost too hopefully they fix it soon http://thechocolatelabapps.com/
Related
I have an app up on the apple store written with Ionic v1, Cordova, and AngularJS. It's been up there for a few years now. We are planning a few more releases in the upcoming months. I got this email from the Ionic Team:
Hi Aubrey,
In just over one week’s time, Apple will begin rejecting new apps using UIWebView. We wanted to reach out with details on how to update your Ionic apps.
If you receive an email from Apple after uploading an app binary to the App Store, you’ll need to update the app. The email reads something like this:
We identified one or more issues with a recent delivery for your app, [App Name & version number]. Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage – Apple will stop accepting submissions of apps that use UIWebView APIs. See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.
You can find complete details including upgrade instructions on the Ionic blog, but here’s the summary:
Using Cordova? Update to cordova-ios 5.1.0 and above, install the WKWebView plugin, and update each Cordova plugin to the latest version.
Using Capacitor? Update to the latest version then sync the project.
Submit a new version of your app before the deadline to ensure that it has been updated correctly.
If you're an Ionic Enterprise customer, your Customer Success Manager should already be in touch. If you're not a customer and would like to learn more about Enterprise Support options, please reach out here for extra assistance. Our Enterprise Support team is available and able to help. We've already helped a number of our customers navigate this change quickly & easily.
Cheers,
The Ionic Team
The email says that they will reject new apps of they are using UIWebView.
Does this also mean that my future releases will be impacted? Will my next release of an existing app be rejected for using UIWebView?
This link provides the answer to both of your questions.
The bottom line: It’s time to update your apps! Apple will only accept submissions of Ionic-based iOS apps that contain references to UIWebView until April 2020 (new apps) and December 2020 (existing apps). To meet the new requirement, simply update to the latest version of Capacitor. If you’re using Cordova, see below.
- From link provided!
I have installed ordova-ios#5.1.1 and using plugins which may have some UIWebView references such as google-plus, facebook4 and social sharing.
Also I've added the right configuration to config.xml but still failed to successfully upload to App Store. They keep rejecting my first app and now my build number is 1.0.21 !!! 21 Tries I've made but still failing.
I've been using GoogleMaps iOS SDK in my app for a while, everything goes fine when I submit to App Store.
But this time I got rejected by Apple, and they say I'm using non-public selector in my app.
The selector is called imageWithName
First, I use Xcode to search if there is any class using this method, result shows nothing.
Then, I use grep -r imageWithName, the result shows GoogleMaps is using the selector
I'm using CocoaPods to install GoogleMaps, and the version is 1.13.0
Previous successful submission is using 1.13.0, too.
So I'm wondering if this is a bug caused by Apple or Google Maps.
I've filed a issue to Google's forum, and accepted by Google staff.
(https://code.google.com/p/gmaps-api-issues/issues/detail?id=9704)
Wondering if anyone facing same issue with me?
Screen shot of App Store reject
Finally solved the problem, reported this issue to Google Maps API Forum,
They've released a new version v1.13.2, this version works and approved by Apple app review team.
https://code.google.com/p/gmaps-api-issues/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal&groupby=&sort=&id=9704
I'm having issues with Facebook review. I'm currently using Unity building an Android and iOS game. Android apk wasn't too hard to upload, but the iOS build is much more.
I can't download the app from App Store because the app isn't reviewed by the Apple Team, and when i try to "use an uploaded build", following instructions here : https://developers.facebook.com/docs/ios/creating-ios-simulator-build-for-review/
My build fail. I found some informations, it seems to be an issue caused by Unity, i changed SDK Version to SDK Simulator, and now i don't know what to do.
Can someone find a way to build this simulator version, can I get reviewed by Facebook without any build ? (As long as i already uploaded and Android build)
I have also had this issue. Facebook are fairly quick with their reviews so for me, the answer was to send the app to the app store and allow Facebook's Review team to download it from there to review it.
I get the following error message when I try to upload the archived app to the App Store:
I tried removing AdColony I was able to upload. Any ideas on how to get this error fixed?
We have throughly tested the app submission process and have found that apps submitted containing our SDK are being processed successfully through Apple’s iTunes Connect site. Our SDK is fully compliant with Apple’s stated intended usage and collection requirements for IDFA.
When you are submitting your app, that contains our SDK, through iTunes Connect you MUST check all 4 of the boxes asking about IDFA. Please see our support documentation on this issue here: http://support.adcolony.com/customer/portal/articles/1516610-device-identifiers-user-privacy.
We did have some reports from developers who were using other monetization partner's SDKs finding that one of these additional SDKs was causing the rejection. You should check with any other monetization partners that you are working with to ensure that their SDKs are up to date and not the cause of what you are seeing.
I have checked the iTC settings
I have uploaded the same app 2 days ago and it works fine but when today I uploaded the same app with a minor bug fix it's now showing this error.
I'm using Admob, Revmob and Applovin. But I know admob is the culprit.
The only solution for me was to trash the Admob-SDK and integrate the Startapp-SDK, It is compliant with the apple's new IDFA policies, you can read their documentation here.
I will let you know if Admob guys fix this issue.
From Applovin Folks
I wanted to update you on an IDFA change Apple made on Saturday. Apple's systems are automatically rejecting apps that are uploaded if the app has SDKs in it that access IDFA and still support pre-iOS 6 (where IDFA wasn't present). Our new SDK 2.3.6 (and in Unity, 3.0.9) will now pass Apple's screen since we have deprecated support for iOS 4 and 5 (only 1.5% of traffic); and note that many popular SDKs in the market act similarly so you may need to work with your other vendors on updating their software for compatibility.
Edit
I uploaded an update today(5th May, 2014) with admob 6.8.0 and it was uploaded sucessfully
It validated for me also. Initially I thought admob was the issue and might have been but after removing TapJoy and all references the app validated.
I had to remove both InMobi and Conversant (aka ValueClick/Greystripe). Then it stopped being an "Invalid Binary" and went into "Waiting for Review". I can confirm that AdColony, Chartboost and TapJoy all definitely pass Apple's check with latest SDKs. InMobi issued an SDK update on 29/4 (v4.3.0) but it does NOT pass this test.
I used Google AdMob and Flurry. With AdSupport framework removed, shows it's AdMob that's the culprit.
I can't find any recently released SDK for AdMob and Flurry, so I just change the status back to ready for binary upload again, select the answer as shown above in the screen dump, and it works for me, some screen dumps on my blog below. Hope this helps. Thanks!
http://new2objectivec.blogspot.com.au/2014/05/app-store-invalid-binary-error-due-to.html
I've submitted an app with AdMob today with the same settings.
It's now in Waiting for Review state.
I've used Xcode Organizer to submit the app. Maybe Apple have re-adjusted the validation.
I uploaded an app with admob sdk 6.8.0 successfully today (after removed mmedia sdk 5.2.0). I think you need to check other ad network sdk.
It appears your issue is actually coming from Applovin, not AdMob. Others seem to have succeeded with AdMob in some way, so it would make sense. These guys have come to the conclusion that it is Applovin -> Source
I've finally got mine to validate! If you remove AdSupport.framework, any culprits causing this failed validation will NOT cause a linker error. So the SDK's that are showing errors are the ones using the framework correctly, remove any others and try again. In my case Millennial was the problem.
I had an app that was at state "waiting for upload" before 12th April. After which the itunes guidelines were updated to contain section of IDFA usage when the app state is "Prepare for upload". So, because of this situation every time I turned in the binary I would get an error of "Improper IDFA usage".
For me the solution was
1.upload a binary without IDFA sdks.
2.make it "developer rejected".
3.Update the settings of IDFA after choosing "ready to upload binary" option from itunes connect.
4.Upload a new binary with IDFA sdks.