how did you resolve this? What settings needs to be done on the server? We are having the same issue.
Buju77
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Ok, we have finally managed to verify our domain. Our issue was, that we had a general redirect rule on our server. This one had to be disabled for a short time for Apple to verify our domain.How we fixed it:1. Entered our domain "example.com" on Apple deveveloper portal2. Downloaded the "apple-developer-domain-association.txt" file3. Uploaded that .txt file to our server4. Disabled our "www." redirect rule "example.com" --> "www.example.com"5. Clicked on "Verify" domain button in Apple developer portal6. Apple website now shows a green checkmark --> woohoo domain verified ✅7. Now enabled our redirect rule again8. Done! Profit! 😁More Info:Apparently Apple will not follow the HTTP 301 redirect responses from your server. Your server needs to delivier the .txt directly under the url "https://example.com/.well-known/apple-developer-domain-association.txt" without any directs.How to check if redirect is the issue:1. Open termial and enter "$ curl https://example.com/.well-known/apple-developer-domain-association.txt"2. It will probably respond with something like the following:```<html><head><title>301 Moved Permanently</title></head><body bgcolor="white"><center><h1>301 Moved Permanently</h1></center><hr><center>nginx</center></body></html>```3. Now try "$ curl https://www.example.com/.well-known/apple-developer-domain-association.txt" (with www.)4. If it responds with the content of the .txt file, then you have the redirect issue.--> to fix it: disable your "www." redirect url for a short time
thanks for you reply!
Thanks for the reply. I'll try to file a bug then. But an example project would be difficult. Because this is not really easy to reproduce. Even locally I may only get it once in a week maybe when compiling our app project. This is only happening in our big main app project. I've never seen this in our smaller projects.
So some pointers (maybe a log file somewhere?) where to look closer when we do finally get this error again to immediately investigate.
I checked and there aren't any crash logs remotely related to assets catalog in ~/Library/Logs/DiagnosticReports/. So I can't attach anything in this regard.
But I've just created a new feedback with bunch of screenshots and logs from derived data, since I just got this error now on my machine:
FB8081594 (Command CompileAssetCatalog failed with a nonzero exit code)
EDIT: Xcode 12 GM is now online for download
This looks very much like a Xcode 12 bug. Did anybody already filed a bug in feedback assistant?
unfortunately we have the same issue. This fails randomly for us on CI and is not reproducible and haven't found a workaround yet :(