Apple Developer Program

RSS for tag

Create and deliver software for users around the world on Apple platforms using the the tools, resources, and support included with Apple Developer Program membership.

Apple Developer Program Documentation

Post

Replies

Boosts

Views

Activity

Account blocked
Hi, ok everyone. I need help please. My developer account was suddenly blocked without any reason and any notice. What I should do now? On regular support I didn't get any useful information, they said that this is probably permanent. WTH?? Can I even know what I have done wrong???Any help please! I cant beleive it. I have building app for years to get some subscribers and now the block me without ANY info !!!!??? I pay for developer account for some year I was at wwdc etc. and now I get blocked. WTF PLEASE HELP! the account Im writing from is not the account that was blocked! I would write with my main developer account but I cant login.
1
1
119
1w
pod file error
require File.join(File.dirname(node --print "require.resolve('expo/package.json')"), "scripts/autolinking") require File.join(File.dirname(node -e "console.log(require.resolve('react-native/package.json'))"), "scripts/react_native_pods") require 'json' podfile_properties = JSON.parse(File.read(File.join(dir, 'Podfile.properties.json'))) rescue {} ENV['RCT_NEW_ARCH_ENABLED'] = podfile_properties['newArchEnabled'] == 'true' ? '1' : '0' ENV['EX_DEV_CLIENT_NETWORK_INSPECTOR'] = podfile_properties['EX_DEV_CLIENT_NETWORK_INSPECTOR'] use_modular_headers! # Enable modular headers globally use_autolinking_method_symbol = ('use' + '_native' + '_modules!').to_sym origin_autolinking_method = self.method(use_autolinking_method_symbol) self.define_singleton_method(use_autolinking_method_symbol) do |*args| if ENV['EXPO_UNSTABLE_CORE_AUTOLINKING'] == '1' Pod::UI.puts('Using expo-modules-autolinking as core autolinking source'.green) config_command = [ 'node', '--no-warnings', '--eval', 'require(require.resolve('expo-modules-autolinking', { paths: [require.resolve('expo/package.json')] }))(process.argv.slice(1))', 'react-native-config', '--json', '--platform', 'ios' ] origin_autolinking_method.call(config_command) else origin_autolinking_method.call() end end platform :ios, podfile_properties['ios.deploymentTarget'] || '13.4' install! 'cocoapods', :deterministic_uuids => false prepare_react_native_project! target 'StayRealtor' do use_expo_modules! config = use_native_modules! use_frameworks! :linkage => :dynamic # Enable dynamic frameworks globally use_react_native!( :path => config[:reactNativePath], :hermes_enabled => podfile_properties['expo.jsEngine'] == nil || podfile_properties['expo.jsEngine'] == 'hermes', :app_path => "#{Pod::Config.instance.installation_root}/..", :privacy_file_aggregation_enabled => podfile_properties['apple.privacyManifestAggregationEnabled'] != 'false', ) Adding Firebase dependencies with modular headers pod 'Firebase', :modular_headers => true pod 'FirebaseCoreInternal', :modular_headers => true pod 'FirebaseCore', :modular_headers => true pod 'Firebase/Auth', :modular_headers => true pod 'Firebase/Firestore', :modular_headers => true pod 'Firebase/InAppMessaging', :modular_headers => true pod 'Firebase/RemoteConfig', :modular_headers => true pod 'Firebase/Storage', :modular_headers => true pod 'FirebaseAuthInterop', :modular_headers => true pod 'FirebaseAppCheckInterop', :modular_headers => true pod 'FirebaseCoreExtension', :modular_headers => true pod 'RecaptchaInterop', :modular_headers => true pod 'FirebaseFirestoreInternal', :modular_headers => true pod 'FirebaseInstallations', :modular_headers => true pod 'FirebaseABTesting', :modular_headers => true pod 'nanopb', :modular_headers => true pod 'GoogleDataTransport', :modular_headers => true pod 'GoogleUtilities', :modular_headers => true; post_install do |installer| react_native_post_install( installer, config[:reactNativePath], :mac_catalyst_enabled => false, :ccache_enabled => podfile_properties['apple.ccacheEnabled'] == 'true', ) # Fix for Xcode 14 signing resource bundles installer.target_installation_results.pod_target_installation_results .each do |pod_name, target_installation_result| target_installation_result.resource_bundle_targets.each do |resource_bundle_target| resource_bundle_target.build_configurations.each do |config| config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO' end end end end post_integrate do |installer| begin expo_patch_react_imports!(installer) rescue => e Pod::UI.warn e end end end error:[!] The following Swift pods cannot yet be integrated as static libraries: The Swift pod FirebaseAuth depends upon FirebaseAuthInterop, FirebaseAppCheckInterop, FirebaseCoreExtension, and RecaptchaInterop, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. The Swift pod FirebaseFirestore depends upon FirebaseCoreExtension and FirebaseFirestoreInternal, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. The Swift pod FirebaseInAppMessaging depends upon FirebaseInstallations, FirebaseABTesting, and nanopb, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. The Swift pod FirebaseRemoteConfig depends upon FirebaseABTesting and FirebaseInstallations, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. The Swift pod FirebaseSessions depends upon FirebaseCoreExtension, FirebaseInstallations, GoogleDataTransport, and nanopb, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies. The Swift pod FirebaseStorage depends upon FirebaseAppCheckInterop, FirebaseAuthInterop, and FirebaseCoreExtension, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.
0
0
181
2w
How I successfully enrolled for the Apple Developer Program!
Hey guys! I believe I've found the solution to successfully enrol for the Apple Developer Program. This is for all of us who have tried enrolling and waiting in vain for the confirmation email from Apple after the acknowledgement email. First, you should know that the whole time I was attempting to enrol I was using my iCloud account and I was trying to do so via my MacBook with the browser. I tried both Firefox and Safari just to be sure it wasn't a browser thing. Then a thought came to me... since I knew Apple also had an Apple Developer app on its store that according to its articles it claims can be used to enrol... I chose to go for it, and this time I opted to enrol with my iPhone for good measure... I downloaded the Apple Developer app... logged into my iCloud account and attempted to enrol. However, this still didn't work. The message said that I couldn't use that email to enrol... And so I signed out and opted to use my Gmail account and voila! I was able to enrol!! The payment went through successfully! I received the SMS notification from my bank and I also got the subscription confirmation from Apple. That's how I did it. I really hope this helps someone 🙏.
0
0
108
2w
Issue with Renewal of Apple Developer Membership
I am reaching out regarding an issue with renewing my Apple Developer membership. For the past two days, I have been in contact with support but am still unable to view the renewal options under my Apple Developer account. Additionally, I am not seeing an option to initiate a call when selecting "Program Purchase and Renewal" as the category for support assistance. Could you please assist in resolving this issue? Access to the renewal option is critical for maintaining our development processes, and I would appreciate any guidance or escalation that might expedite a resolution. Thank you for your attention to this matter.
0
0
83
2w
ios 18,xcode 16,RadStudio 11.3
Hello; I am using Rad Studio 11.3 software development language. When distributing the application, it works fine with iOS 16.7 iPhone X. I am getting "DeveloperDiskImage.dmg" error on iPhone 14 Pro iOS 18.1 device. The application crashes on the opening screen. At the same time, my HospiTools application in Appstore is distributed and installed with iPhone X 16.7. When we download the application from Appstore, it works fine with iOS 18.1. Thank you.
0
0
77
2w
Unable to Complete Apple Developer Program Purchase After Multiple Attempts
Hello, I’m experiencing issues completing my Apple Developer Program membership purchase. I’ve attempted the process three times, received an order acknowledgment email each time, and was informed that the request would be processed within 2 business days. Despite this, my payment does not go through, and I’m repeatedly prompted to make the purchase again. Here are the details: Enrollment ID: 2D8KS5FGH4 Cost: US$99 Attempts: 3 separate purchase attempts Acknowledgment Email Received: Yes (Order Acknowledgement email from Apple Developer, confirming my order request) I’ve verified my payment method, billing details, and even tried different browsers and devices. Each time, the process completes up to the acknowledgment, but the payment is not finalized, and my membership remains inactive. Could you please help resolve this issue? I need assistance in activating my membership so I can begin development. Thank you,
0
0
123
2w
Team requires more devices than that of the Device limit
Hi Hypothetically, my company has 300 mobile engineers and we're building an iPhone app. Optimally I'd like each mobile engineer to have a physical device which they can do their day to day development, testing etc on. What options do I have to enable this given that there is a 100 device limit for iPhones on the Apple Developer Program used by my company. (https://developer.apple.com/help/account/register-devices/devices-overview/) Thanks
1
0
173
2w
Issue Accessing Apple Developer Program – Payment Confirmation Received, No Further Action
Hello, I’m encountering a problem while trying to join the Apple Developer Program from Argentina. Each time I submit a payment, I receive a confirmation email stating: Dear Agustin Oberg, Thank you for your order. Here's a summary of your order request, which will be processed within 2 business days. We'll notify you when your items are ready. Order Details: Apple Developer Program US$ 99 Best regards, Apple Developer Relations However, despite this message, no further actions are taken, and I am still unable to access the program. I’ve tried multiple credit cards and submitted payments on several occasions, but the issue persists. Is there anyone who has faced a similar problem or can offer advice on how to resolve this? I would appreciate any assistance or guidance to complete my registration successfully. Thank you!
0
0
111
2w
I want to pay
I have tried to mail the Apple Developer Team so many times now. In desperation, I was even prepared to pay twice should another $99 go through if I didn't hear anything back from Apple on my first payment. I would like to pay my $99 so that I can get registered and start launching my app. Please help? Where can I go to get someone to attend to my repeated communication.
1
1
95
2w
macOS App Archive Validation Failed mdimporter Info.plist
…How do I figure out what is wrong to be able to upload the app to the store with its signed mdimporter embedded? mdimporter in macOS project, compiled separately, signed and bundle dropped into Xcode app project. Runs fine but trying to upload to Apple App Store for macOS one runs an Xcode > Product > Archive command and I get this error… Xcode > Organizer > Products > Archives … Validation Failed Asset validation failed This bundle is invalid. Unable to load ‘Info.plist’ for bundle at path: ‘MyApp.app/Contents/Library/Spotlight/MyApp-SpotlightIndex.mdimporter’.. (UUID-shown-here) The Info.plist of the mdimporter is in the separate mdimporter Xcode project, the bundle is compiled as Build for Running and was dropped and copied into the Xcode app project. Runs fine. Any ideas on how to get that to NOT FAIL so I can succeed with my app Archive to upload to the Apple App Store? How to find out what is wrong? How to fix? I'm at a loss here.
1
0
117
2w