Post

Replies

Boosts

Views

Activity

Xcode Cloud Developer Account Not Eligible
I'm having issue using Xcode Cloud with my developer account. I have active Apple Developer Program membership (Individual) associated with my Apple ID: Same Apple ID is the only Apple ID added in Preferences > Accounts in Xcode 13.4.1 (13F100). But with that setup, for any project I can try, Report Navigator > Cloud tab shows this error: Your developer account is not a member of a team that is eligible to use Xcode Cloud And Product > Xcode Cloud > Create Workflow... shows error This operation could not be completed. If I switch to a different developer account that I have (associated with a team, not individual membership) – the issue is resolved and I can start creating first Xcode Cloud workflow in same projects. Can Xcode Cloud be used with individual ADP memberships? If so, why my account is not eligible? How can I further diagnose the problem?
15
4
3.7k
Aug ’22
How does the system resolve App Clips links?
How does iOS know that given URL is an App Clip URL? Developing a Great App Clip - https://developer.apple.com/documentation/app_clips/developing_a_great_app_clip lists a number of ways app clip can be launched: Scanning an NFC tag or visual code at a physical location Tapping a location-based suggestion from Siri Suggestions Tapping a link in the Maps app Tapping a Smart App Banner on a website Tapping a link that someone has shared in the Messages app Some of these – like scanning a QR code – are interactive. Which means there is no way to pre-process the URL to understand if it is an App Clip URL (which can be done for links in Maps for example). Does this mean that for each QR code scanned the system will first need to make a request to the App Store to understand if the link should be presented as App Clip?
1
0
518
Jul ’20
App Attest Security Model
From Establishing Your App’s Integrity - https://developer.apple.com/documentation/devicecheck/establishing_your_app_s_integrity: Not all devices can use the App Attest service, so it’s important to have your app run a compatibility check before accessing the service. If the user’s app doesn’t pass the compatibility check, gracefully bypass the service. You check for availability by reading the isSupportedproperty: let service = DCAppAttestService.shared if service.isSupported { 		// Perform key generation and attestation. } // Continue with server access. You change the behavior of both your app, as shown above, and your server — which can no longer require assertions — when you find that the service isn’t supported. What stops a compromised/fake app instance to pretend to run on 'not supported' device, report that to the app server and that way circumvent App Attest completely? Is there any way for the app server to verify this 'not supported' claim received from the app instance?
1
0
1.2k
Jul ’20