I get following warning while validating archive
Undeclared Use of Advertising Identifier [IDFA].
You app contains the Advertising Identifier [IDFA]
API but you have not indicated its usage on the Prepare for Submission
page in iTunes Connect. Click Submit for Review to access the
Prepare for Submission page and indicate IDFA usage.
Google returns only 2 pages in some asian language when I search for that text.
I do not know where is Prepare for Submission page? I searched it in iTunes Connect.
It's only a warning, you will get it validating the build or submitting it from XCode.
When you prepare the build in the new iTunesConnect, you have to select the build you want to submit for review (it will appear there a few minutes after you submit it with Xcode, even with the IDFA warning), after you click Submit for Review you will get the three questions with a warning saying:
Ensure that you select the correct answer for Advertising Identifier
(IDFA) usage. If your app does contain the IDFA and you select No, the
binary will be permanently rejected and you will have to submit a
different binary.
Select the appropriate answers and your build should change the state to Waiting For Review.
In iTunesConnect, click on submit for Review. Then you're asked three questions on IDFA, encryption usage and usability changes.
Related
I'm trying to upload a new android apk in the google play console. It has a couple of additional permissions like READ_SMS which is triggering a permissions form that I have filled too. I am however unable to save the data. Error code in logs: 858285013
Error snapshot
I had the same issue in one of my apps. I followed the below steps to resolve the issue.
Upload the new apk with only required permissions in the track which you want
Now you can see the Old apk with retain option
If you click on retain button, you will see permission declaration form
Select No, this release does not meet the SMS and Call Log permission policy option and click on save in bottom right of the page
Now click on discard button
Now create new release and upload the latest APK and fill the declaration form
Save the new changes and now you will able to save the changes
Before that if your app is using RECEIVE_SMS & SEND_SMS to verify the mobile number, then you need to change the implementation of mobile verification. For that you need to use Google's SMS retriver API. If your app comply with the Google developer policy, then you can keep the READ_SMS permission and for that you need to mention the valid reason in the permission declaration form in play console. Or you can remove the READ_SMS permission, and proceed with the flow as mentioned above.
You must Use SMS intent or you need to send a declaration Form... SMS, CALL LOG.. not allowed from 2019 Jan 9th.. Plesse Check this link android SMS Permissions
SMS Permission Declaration Form
I'm trying to get an Android Wear watchface set up that gets the number of steps the user has taken. To do that, apparently I have to get the data from Google Fit. Step 3 of that process is getting an OAuth 2.0 client id. I'm following the steps in the link below.
Request an OAuth 2.0 client ID in the Google API Console
The first step is clicking the blue GET A CLIENT ID button. In there I select my project and click Continue. That enables the Fitness API. Then I click on the blue Go to credentials button. There I choose Android for where I'm calling the API from and User data for the type of data that I will be requesting. Then I click the blue What credentials do I need? button.
This page is where the problem lies. I am supposed to enter a name, SHA-1 fingerprint and package name. However, all three fields are disabled so I can't type in them. If I go ahead and click on the blue Create OAuth client ID button, it marks those three fields in red with some verbiage about being required. I still cannot type in the fields.
How is this supposed to work?
I was facing the same issue today. In case you haven't found a solution to your problem, you can try creating a project with a different Google account. I think it happens because of the conflict with your previous projects.
We have an iOS app that is fully managed in Xcode by the Agent setup in iTunes Connect.
Now, as our team grows, we tried to add a new member who would be responsible for uploading new versions. But we cant succeed in doing this.
In iTunes Connect, this new member is listed under 'Pending Invitations'. The email was sent out and user has accepted the invitation, but status didn't change.
When doing a re-send invitation, the second mail is well received, but clicking on the 'Accept' brings message 'Already a Member'. Status in Itunes Connect stoically stays with listing user under 'Pending Invitations'.
Xcode allows signing in with the new user, but doesnt see it as being a member of the team.
Although having checked the docs carefully, we must have missed something in this process.
If the member don't have a apple id account on his email he should create it before when he accept the invitation, if it's the case you should wait the itunes validation and it's ok.
check the apple documentation for more details.
On iOS8, in my app (which is working fine), if the user is not logged in with their Apple Id, and they attempt an in-app purchase, they get the following Apple alert:
Now, if the user presses "Cancel",in the code, we get an error code 2 with the SKPaymentTransaction. This has the enum code SKErrorPaymentCancelled
On iOS9, in the same situation, we now get error code 0,
Error Domain=SKErrorDomain Code=0 "Cannot connect to iTunes Store"
UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store}
This has enum code SKErrorUnknown, which doesn't seem useful.
Anyone else run into this? The difficult here is in my app UI. If I get an error code, SKErrorPaymentCancelled, I don't present any info to the user as it is clear that the user has explicitly done a cancellation.
With SKErrorUnknown, I can't tell what has gone on, so I present an error alert to the user. Which, if they have explicitly cancelled, is just annoying. Thoughts?
May be :
Your app is enabled only for other location, test user was localized for other - and with this setup does not work. You should enabled the app for USA and created a test user localized in USA and it seems to work (no code change at all). And I think that proves that the code is ok, just the apple sandbox has some problems with non USA test users.
And don't login from settings. When this login form comes from your app, try it.
Okay I register my application to Itunes connect. I make sure that the correct application name and bundle is available.
Then I archieve my project and then I want to validate.
Then I got this message.
What is exactly wrong?
Is apple cannot figure out any application with the same bundle id and the same application name? Which one mismatch?
This is a common error. Just make sure that you set your app's state to waiting for upload
From Apple's documentation:
Troubleshooting: If Xcode doesn’t find an iTunes Connect application
record for your application, the “No suitable application records were
found” dialog appears. This dialog also appears when the application
record state is not at least Waiting for Upload.
When you register your app, it becomes 'Ready For Upload' first. You have to put it to 'Waiting For Upload' manually, by clicking the bottom-right button in iTunes Connect.
I'll add another answer because I just spent the last 30 minutes trying to figure out why I could not get validation to work...
If you have multiple iTunes Connect accounts, make sure you are logging in with the correct account that you created the app in iTunesConnect with.
It sounds like a no-brainer but the Organizer remembers the credentials that you last validated with for deployment. The last app I shipped was several months ago under my contractor credentials. My new app is under my own credentials but I was trying to authenticate with the saved contractor credentials. ugh.