My app is using IDFV (id for vendor) and a third party analytics framework is using IDFA (id for advertising).
I'm not planning to upgrade my app using XCode 12 right now, but in the next few months.
What will happen for both identifiers if an user is using iOS 14 on my app built with XCode 11 and ios 13 SDK? permission will be granted by default or asked?
From what I understand:
On iOS 14 the IDFA is nullified until you get the user's authorization to use it, which means that you get zeroes if you don't ask, and you also get zeroes if you ask and the user refuses.
If collecting the IDFA is really important to you you will have to use Xcode 12 to provide a version compiled with the iOS 14 SDK, ask for the authorization, and hope some people give you the authorization (but don't count on it).
IDFV will still works as of now.
edit: Apple just announced that they will delay the necessity to ask for the permission to use the IDFA. So you are saved for now.
Related
This question already has an answer here:
Generate ipa without paid apple developer account
(1 answer)
Closed 8 months ago.
I have built webview IOS app yet I want to built ipa so that iphone users can install it without apple developer account however I am facing this on Product>Archive are disabled.
enter image description here
Short answer: You can't. In order to upload apps to the app store you need a paid developer account.
With a free developer account you can install your test apps on a small number of devices who's UUIDs you register to your account. (I haven't done this, so I'm a bit vague on the details, but that's my understanding.)
I'm trying to understand, what will happen if one remains to use older Xcode version for developing, building and deploying.
I understand that each new Xcode version (...10,11,12) comes with new SDK support, improvements and features. I also have a great example of, we'll need the latest Xcode 12 to deploy our app to iOS 14 and above, since it won't work for Xcode 11 and below.
[Scenario ques]
However, what are the possible issues if one decided to continue in building and deploying their app with Xcode 11(SDK iOS13)?
Aside from not being able to test the app in a proper iOS 14 environment and risking of having bugs. Could the SDK version in Xcode11 and Xcode12 make any difference to the app?
You can certainly go on playing with Xcode 11 if that is what you feel like doing. But that's all you will be doing - playing. You won't be able to do anything with an app that you create that way. In particular, without Xcode 12, you cannot run the app on a device with iOS 14 on it, and you cannot submit the app to the App Store.
So when you say
use older Xcode version for developing, building and deploying
...you can just delete the word "deploying"; you won't be doing that (if the word "deploying" means what it usually means).
(And you cannot easily develop an app partly with Xcode 12 and partly with Xcode 11, as some of the things you do in Xcode 12 can make the project incompatible with Xcode 11.)
I have an UI issue in my Swift 1 (Xcode 6, iOS 7.1) app on devices running iOS9. I've tried to convert my app to Xcode 7 and Swift 2.0 but I'm running in a lot of issues here.
To give my customers a quick fix until I've figured out whats wrong I was wondering if I can download and install Xcode 6 (the version I build and uploaded the app last time) correct the UI issue (I know what to do) and upload the app again.
In a nutshell: Will Apple deny an app update with an old Xcode/Swift version?
The “Submit Your Apps” page currently (as of 2015-09-23) says
If your app still depends on Xcode 6, you'll need to keep a partition or external hard drive with OS X Yosemite installed in order to submit from Xcode 6.
This clearly implies that you can still submit apps with Xcode 6 (and therefore with the iOS 8 SDK).
It seems that new ios 8 APIs such as Local Authentication run on ios 7 without crashing. Of course, the actual policy validation fails (gracefully without a crash), but given that the API is brand new in ios 8, how is it that the app does not crash upon calling this new API?
In the previous versions we had to do a check before calling a new API.
This is just speculation, but sometimes a "new" API was already available in the older versions of the OS, but has not been made available for developers outside of Apple. However, if you submit such an application to Apple there is a good chance that it will be rejected.
When I try to distribute an app I get this error:
Xcode attempted to locate or generate matching signing assets and
failed to do so because of the following issues.
No matching provisioning profiles found for "Application/TheApp.app"
None of the valid provisioning profiles allowed the specified
entitlements: application-identifier, beta-reports-active,
keychain-access-groups.
I don't really understand what that error means. Any help?
You can't submit an app to App Store with beta software, you have to wait GM release.
From Apple
New apps and app updates submitted to the App Store must be built with
release versions of Xcode 5. Do not submit apps built with beta
software, as beta versions are for development and testing only.
Xcode 6 beta, iOS 8 beta, and OS X Yosemite Developer Preview are
pre-release software. Your use is subject to and licensed only under
the terms and conditions of the iOS Developer Program License
Agreement ("iOS PLA"), including any applicable consent to collect
diagnostic data set forth therein. If you have not agreed to the iOS
PLA, you are not permitted to use this software.
9 Sep. 2014
You may now use Xcode 6 GM seed to submit apps to the App Store and Mac App Store.
I have the same error till I revoke and request new iPhone Distribution certificate from Apple.
Go to developer.apple.com, open Certificates.
If you have 2 or less certificates for Distribution you can create new one. But if you have 3 you need to revoke one and then create new one.
Go to Provision Profiles and select your profile. Change old certificate to just created certificate. Download provision profile.
Now build your app.
Obviously I think you can, starting now ;)
I just received the mail from :
To prepare your apps for the App Store, download and build with the iOS 8 and Xcode 6 GM seeds from the iOS Dev Center. With these latest seeds, Swift is now final and you can submit your iOS apps written with Swift to the App Store.
If you are not using a beta version of Xcode, and you have regenerated all your certificates, and you are doing everything you should and it is still not happening; this is what worked for me:
1. Backup your code, 2. delete your project, 3. recreate the project anew, 4. add your code back in and voila successful build for validation and submission to the App Store.
I found a hack, you can replace the build version number in the system to cheat to the system.
System/Library/CoreServices/SystemVersion.plist
Replace the build version of the beta for the last release version, in my case for 10.15.5 is 19G73