Search results for

5.1.1

400 results found

Post

Replies

Boosts

Views

Activity

Reply to How do I see which devices my app supports?
armv7 minimum iOS is 3.1https://developer.apple.com/library/ios/documentation/DeviceInformation/Reference/iOSDeviceCompatibility/DeviceCompatibilityMatrix/DeviceCompatibilityMatrix.htmlSee Table 1-1I think what you saw when uploading was the admonition note Apps and app updates submitted to the App Store must be built with Xcode 5.1.1 or later, and iOS 7 SDK. That means you need to support iOS 7 capable devices (not minimum iOS 7)...screens, etc. Base SDK is 8.x and deployment can be 6.1, as an example...iOS 5 users are in single digits now, so I'd not put too much effort into that level to make it work.But if you're sure you set deployment to iOS 5.1.1, and it makes it into the store, then by default any iPod Touch 4 users at 5.1.1 or higher should be able to install. And pls. move to Xcode 😉
Aug ’15
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage(purchase in-app)
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Next Steps To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their iOS devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Please note that although App Store Review Guideline 3.1.2 requires an app to make subscription content available to all the iOS devices owned by a
0
0
850
Jun ’23
Reply to 5GB limit for all Hosted Content? (ERROR ITMS-4162)
I'm having the same problem. I filed a DTS incident, and Apple confirmed that there is no limit to the total size of the hosted content. Unfortunately, we are still unable to upload. Please let me know if you find a solution.I did find a stackoverflow thread that suggested that this was an old Application Loader bug from years ago that has never been fixed, and recommended using xcode 5.1.1 to upload. Unfortunately, that didn't work for me either; xcode 5.1.1 comes up with an error Apple ID is not an integer.
Topic: App & System Services SubTopic: StoreKit Tags:
Mar ’16
Reply to X Code 5.1.1 Signing Identities Revoked
>and don’t have to rely on XCode 5.1.1.Point is, it's not your call. Xcode 6.x is the minimum allowed when doing store submittals now, so if that's your goal, you don't have a choice but to walk away from Xcode 5.x. >And, also how do I transfer the signing identities if they are revoked?Revoked/expired/invalids aren't transferrred, they are renewed.Many things have changed for codesigning since 5.1.1 was originally used, including the recommended preference of automatic provisioning. I suggest you get busy w/Xcode 7.3.1, and deal with details as they arise.
Jul ’16
App Store Review Guideline 5.1.1(v): What is understood as OFFERING the account deletion WITHIN the app
The newly updated App Store Review Guideline 5.1.1(v) states that: ... If your app supports account creation, you must also offer account deletion within the app. ... The guideline leaves two important questions open: What does it mean to offer the account deletion? Is it enough to point the user to the website, email, ... or does the deletion need to be completed within the app? Does Apple expect a simple account deletion (in the sense of inactivation) or a full delete-all-my-data request? Is there a statement from Apple which specifies these details or has someone already receive an app rejection for it?
15
0
13k
Jun ’21
App Store Review Guideline 5.1.1(v): What is understood as OFFERING the account deletion within the app
The newly updated App Store Review Guideline 5.1.1(v) states that: If your app supports account creation, you must also offer account deletion within the app. The guideline leaves two important questions open: What does it mean to offer the account deletion? Is it enough to point the user to the website, email, or does the deletion need to be completed within the app? Does Apple expect a simple account deletion (in the sense of inactivation) or a full delete-all-my-data request? Is there a statement from Apple which specifies these details or has someone already receive an app rejection for it?
2
0
967
Oct ’21
Reply to Application Crashing on ggl_gtzuompo
What other library could it be? I'll post all the pods used in my app here:Using Alamofire (4.4.0)Using AppsFlyerFramework (4.8.10)Using Bolts (1.9.0)Using Cartography (3.1.0)Using Crashlytics (3.10.2)Using FBAudienceNetwork (4.99.3)Using FBSDKCoreKit (4.33.0)Using FBSDKLoginKit (4.33.0)Using FBSDKShareKit (4.33.0)Using Fabric (1.7.7)Using FacebookCore (0.3.1)Using FacebookLogin (0.3.1)Using Firebase (5.6.0)Using FirebaseAnalytics (5.1.1)Using FirebaseCore (5.1.1)Using FirebaseInstanceID (3.2.1)Using Google-Mobile-Ads-SDK (7.36.0)Using GoogleAppMeasurement (5.1.1)Using GoogleUtilities (5.2.2)Using IQKeyboardManagerSwift (6.1.1)Using KeychainAccess (3.1.2)Using LUKeychainAccess (1.2.5)Using MBProgressHUD (1.1.0)Using Quick (1.3.1)Using ReachabilitySwift (4.3.0)Using Reveal-SDK (11)Using nanopb (0.3.8)
Nov ’18
App (using MusicKit) rejected - Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
App Rejected stating Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage Issue Description One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used. My App is simple using MusicKit. My app has only two buttons and the user just taps them. ・search button : Search for Apple Music with auto-generated text and play previews. ・listen button : Listen to searched songs on Apple Music. NSAppleMusicUsageDescription key is the app requires Apple Music access to search for songs and to play the searched songs. I don't know how to fix it. Please let me know some advice.
1
0
302
Mar ’25
Submission Rejected: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
Hello Experts, I am in need of your help with this feedback from the App Reviewer. Issue Description: One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used. Next Steps: Update the location purpose string to explain how the app will use the requested information and provide a specific example of how the data will be used. See the attached screenshot. Resources: Purpose strings must clearly describe how an app uses the ability, data, or resource. The following are hypothetical examples of unclear purpose strings that would not pass review: App would like to access your Contacts App needs microphone access Feedback #2 Regarding 5.1.1, we understand why your app needs access to location. However, the permission request alert does not sufficiently explain this to your users before accessing the location. To resolve this
1
0
242
Jun ’25
Reply to Submitting iOS app for iPad-1 (iOS5.1)
Hi ishahak2If I include the standard architectures (both 32 and 64 bits), I'm getting an error saying that apps with 64-bits can't set their target to iOS 5.1. (see below)iOS 5.1 did not properly handle fat binaries with a 64-bit slice. iOS 5.1.1 was released to address this issue and it is the lowest iOS version you can deploy back to when distributing via the App Store. Set your deployment target to iOS 5.1.1. You can then continue to build a fat binary, with 64-bit and 32-bit slices.
Sep ’15