No. Information in Membership details are some another. If I want to edit bank account holder apple offers checkbox "Use the same as Legal Entity" and when I check it, it fill-in address with typos errors. In membership details address is correct. So question is that where else have Apple stored "Legal Entity" information to edit it?
Post not yet marked as solved
Terrible problem. We can add as many APP ids as we want but grouping supports just 5. We successfully configured Facebook and also Google sign-in for in about 10 app variants but it is not possible for Apple. Apple should increase this useless low limit.
Post not yet marked as solved
This is typical Apple. Iphone 6 with iOS 12 is nowadays still supported by Apple (only iPhone 5* does not have support) but you do not have any way how to test it! Simulators support only newer devices! Thank you great Apple!
Post not yet marked as solved
Exactly. In my bug report via black hole Apple Feedback Assistant I exchanged in about 20 messages with Apple support. They wrote just excuses etc. Later wrote that they have some problem with Lets Encrypt cert. Strange because of certs are world-wide accepted, most popular certs, every browser accept it including Safari but Apple engineers have problem with validating our websites with Lets Encrypt certs. Thanks for all. We annoyed them for so long that they admitted that the problem is on their side and they are preparing an improvement. Question is how many years it will take.
Post not yet marked as solved
After tens of messages with apple support and many irrelevant answers and many excuses I finally got this answer...
> Our engineering teams have found that the validation job is seeing closed connections while trying to fetch the SSL certs.
>
> To provide more context, when the validation job tries reaching the client host at the verification file URL path and encounters an HTTP 200 response, it will re-use the open connection and acquire the SSL cert information (to check for expiration as well as to ensure no changes to the Subject and Issuer in the SSL cert chain have been made from the previous domain registration). This is where the issue for automated validation is occurring for your domains.
>
> They recommend for you to further review the timeout settings and adjust if needed.
>
> We appreciate the feedback you have provided to the verification process. Our teams are exploring ways to enhance and improve the domain validation process.
Interesting is that any browser including Safari can access SSL cert info, also https://www.ssllabs.com/ssltest have no problem to validate cert, just nobody has problem except Apple. Also interesting is when I click "Verify manually" Apple succeed verification? Just then there is no connection close problem? But when Apple should do it automatically suddenly there is a some problem with closing connections? Im really loosing any hope that Apple will sometime fix this annoying bug.
Post not yet marked as solved
Be careful because of this invalid_client error could be misleading (as always Apple's error messages)
$postParams = array(
'code' => ...,
'client_id' => ...,
'client_secret' => ...,
'grant_type' => 'authorization_code',
'redirect_uri' => ...,
);
$curl = curl_init('https://appleid.apple.com/auth/token');
// never pass params as just array for apple without stringifying via http_build_query()
curl_setopt($curl, CURLOPT_POSTFIELDS, http_build_query($postParams));
When you will use just curl_setopt($curl, CURLOPT_POSTFIELDS, $postParams); it is valid POST request but another type than Apple expects but lazy apple developers are not able to provide error that this type of POST request is unsupported.
In accepted response is To request user information in the id_token... But it is not true, user info is never in id_token but just after first sign-in (Ok, Apple decided just one time and makes developer life complicated as Apple always does) after redirection from https://appleid.apple.com/auth/authorize to redirect_uri When authorizing we set also 'response_type' => 'code id_token' + 'scope' => 'name email' but user info is not included in decoded id_token but just as separate parameter "user"...
What about security dear Apple? How we can trust fields in user param? Email, OK, it is included also in id_token which can we verify by signature and Appples public key.
@ppinkney are you sure user info is included in id_token?
Post not yet marked as solved
I have sent mail via https://developer.apple.com/contact/#!/topic/SC1109/subtopic/30064/solution/CONTACT.EML.GEN/details why bug reported via Feedback Assistant is not solved for many months (status is OPEN with no answer from Apple employees). But answer to email is terrible and useless - copied texts from https://developer.apple.com/bug-reporting/#after-submission Response was from eurodev(at)apple.com So Feedback Assistant is ignored, Apple Developer Forum too, mail support too. What Apple developer should do when there is a real bug? Apple has worst developer support ever. Each developer must pay 99 USD/yearly but bug reports are ignored. Google developers program is for free and each bug report is transparently solved at Google Issue Tracker: https://issuetracker.google.com
Post not yet marked as solved
@meaton could you check this thread please?
Post not yet marked as solved
I do not understand why Apple optionally does not provide way to users (or to developers in console) to see some error details? You can google https://www.google.com/search?q=apple+pay+%22payment+not+completed%22 that there are thousands topics about it over the internet. And solution easy - add some way to show more error details what is the problem. The status how it is now with just simple "payment not completed" it is just lottery. Apple developers works like ... someone on the street ask you what time is it and you answer find out! So dear users/developers guess why apple pay is not working and we do not know if it is developer error or user error - answer is the same "just error".
Post not yet marked as solved
Im sure that this is apple bug because of they do not do what is stated here:
https://developer.apple.com/documentation/apple_pay_on_the_web/maintaining_your_environment
Renew Your Domain Verification
Domain verification expires on the same date that your domain’s SSL certificate expires. Apple servers check if SSL certificates have been renewed at 30, 15, and 7 days before expiration.
If you update the SSL certificate before it expires, Apple detects the renewed certificate and the domain remains verified. No further action is required on your part.
If the SSL certificate expires and is not replaced before expiring, you must redo domain verification in your Apple Developer Account. See Verify a Merchant Domain for additional information.
Im wondered that Apple have global bug affecting each merchant and does not solve it for more than 1 year and also does not answer at all. We and many others are receiving from Apple tons of incorrect email notifications which mention incorrect (old) certificate expiration however it was renewed.
Post not yet marked as solved
Dear Apple, could you please answer? It seems that automatic verification does not work at all. Just manual. It is big problem when using short lived certs such as Lets Encrypt. But also problem for long lived certs if you have many many domains. I already reported this bug via Feedback Assistant but this tool is terrible. In the past we have reported many other issues with no answers after months/years. So no hope Apple to do something with it. Apple Feedback Assistant is private so nobody sees how apple ignores developers reports. Google bug tracker is public and before adding new bug/ticket you can search if it is already reported and employees from Google response there. This apple developer forum is the worst support all over the world such as their Feedback Assistant. No answers from Apple just developer complaints. For anyone please fill in bug here https://feedbackassistant.apple.com/ Maybe it will help when many identical issues will be reported by more developers.
One of reason (from many other possible as googled) why archive is added to "Other items" is that Xcode does not know CFBundleVersion/CURRENT_PROJECT_VERSION. But it is not easy as always in Apple world. Anyway I had CFBundleVersion in Info.plist Xcode did not see/used it. See details below.
After upgrade from Xcode 13.2.x to 13.4.x my app archive started to show in organizer in section "Other items" not in "iOS apps". Also in organizer app has empty version. Build to iPhone was working, build on simulator failed due to error, that I do not have CFBundleVersion in Info.plist - but I had it there. I had fixed number (not variable) and it is root of problem. I had to change static values to variables....
File Info.plist
// OLD incorrect
<key>CFBundleVersion</key>
<string>345</string>
<key>CFBundleShortVersionString</key>
<string>1.2.3</string>
// NEW correct
<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>
<key>CFBundleShortVersionString</key>
<string>$(MARKETING_VERSION)</string>
File project.pbxproj
...
CURRENT_PROJECT_VERSION = 345;
MARKETING_VERSION = 1.2.3;
...
And additionally I had to add variables to file project.pbxproj to Release and Debug sections because I did not have it there. So with older Xcode it was working this way and versions was taken from Info.plist. Now it seems that source of true are variables from project.pbxproj but Apple have incorrect error messages because it is fail to say in error that CFBundleVersion is missing in Info.plist when it is there. Finally Xcode automatically deleted CFBundleVersion and CFBundleShortVersionString from Info.plist.
I have spent many many hours of finding out what is problem. I hate upgrading Xcode - nightmare, many hours always lost.
Post not yet marked as solved
The best solution to this stupid Apple situation is to install app "DevCleaner" which offers to delete many GB of Xcode (probably files and caches from simulators - I got 4-6 GB more space; builded archives I did not want to delete but app offers it too). It is really shame on Apple that I can not upgrade 12 GB app with 40 GB free disk space (maybe it time to offer external disk to store new installation files of xcode to save space). Soon I will have to throw my MacBook with 120GB disk to trash because of hungry Xcode upgrades. I just have in macbook Xcode and Chrome. I had to remove anything else bigger than 100MB due to hungry and nasty xcode. Many pre-installed bloatware apps like Music, TV, Mail, Maps, Books and many other can not be removed to free space.
Post not yet marked as solved
macOS Big Sur 11.6.7 20G630 released in June 9, 2022 is incompatible with iOS 15.5 released May 16, 2022. Apple platform for developer is nightmare it is worst platform all over the world. I hate this. Apple is not able to support compatibility between own softwares for more then several weeks.
